How to get app icon badge numbers in iOS7 without push notifications
Refresh your app in the background with a new iOS7 feature
ITworld | February 5, 2014
Using the badge number on your app icon for iOS is a great way to let the user know that there is something new to interact with in your app. Here’s a quick way to achieve this without using push notifications.
The badge number is the little red circle you see on your app icons from time to time, most often mail and the app store notifying you of new items. Before iOS7, the only way to use this feature was to leverage it via Apple Push Notifications. While the push notification service is great, it takes a fair bit of configuration to enable. You need to initiate the notifications from the server side not the mobile device for starters, and the app needs to be provisioned properly to enable them.
Starting in iOS7 however, you can use a new feature called Background App Refresh to periodically poll for new data and update the app icon badge indicator based on that data. This can be done with just a small amount of code, especially in comparison to full blown push notifications.
It works like this, you register your app into a new app registration category called “fetch”. You then implement an event handler in your AppDelegate which will fire when iOS decides it’s going to allow your app to update. The interval in which this happens is unknown because iOS determines it dynamically based on your usage patterns with the app. If you use it a ton, it will fire more frequently, if you hardly use it at all, less so.
To get started, you first need to register your app into the “fetch” category. You do this by editing your app’s Info.plist file, add the key “Required background modes” and set a value of “App downloads content from the network”. If you’re using Xcode 5 you can simply click on your project target, go to the Capabilities tab, expand the Background Modes section, and check the box for “Background fetch".
Next, you need to add a little code to your AppDelegate.m file.
The first bit in the application didFinishLaunchingWithOptions: method lets you polietly suggest to iOS how frequently you’d like your app to be refreshed. It’s good to be responsible with this as it could affect battery life if abused. In this case, I set it to the minimum fetch interval.
The next method application performFetchWithCompletionHandler is the event handler that you need to add in order to perform the data call. In this method you can do whatever logic you need to execute in order to update your app or it’s badge number. Once you have that number, updating the icon is as simple as calling:
[UIApplication sharedApplication].applicationIconBadgeNumber = newItemCount;
Finally, you need to end your performFetchWithCompletionHandler by responding back that you're finished and provide a status such as
completionHandler(UIBackgroundFetchResultNewData);
iOS expects you to return this promptly, within about 30 seconds, otherwise it will start to penalize your app’s background execution to preserve battery life.
As you can see, with just a few lines of code and some minor setup, you can add this welcomed feature into your iOS7 app. Users today expect to be notified when their apps have actionable items, and doing so with just an e-mail or with a barrage of push notifications can become a nuisance. This represents a great, lightweight alternative to keep the user informed and their apps synchronized.
Matthew Mombrea is a software engineer, founder ofCypress North, and a technology enthusiast.
The opinions expressed in this blog are those of the author and do not necessarily represent those of ITworld, its parent, subsidiary or affiliated companies.