Marketers may have heard about some of the well-publicized features in iOS 8 such as Interactive Notifications and widgets, but there are lesser-known behavioral changes in the new operating system that could have a profound effect on the end-user?s experience.

Many of these changes represent new opportunities to delight and engage your users, but others, if ignored, could disrupt a marketer?s ability to deliver pushes or power application features based on location.

Whether you are planning an app update for iOS 8 soon or not, take a moment to think through this watch list of new app, location and push-related behavior, along with our tips for how to think about and best handle these changes:

? When iOS assigns a device token

? When a device can receive a ?silent? push

? When a device can display a local notification

? New location opt-in behavior and options

Apple has changed the way it assigns device tokens, creating a pathway for app developers to dramatically improve user experiences.

Before iOS 7, iOS assigned a device token, or a push address, whether the user opted in to push or not. Starting in iOS 7, the OS only assigned a device token if the user opted in to push. 

Now, once again, iOS 8 assigns a device token to users who opt out of push if the app developer has enabled the remote-notification background mode.

This means that Apple now allows you to deliver pushes in the background, even if the user has opted out of notifications to pre-load content in the background to create fresher and faster app experiences. 

Instead of pulling the latest content from servers after the app opens, forcing the user to wait, the user can view it immediately.

This change also has implications for companies that track device tokens in their backend systems or map them to corporate logins. 

If you are doing any device token tracking in your backend systems, you will want to take note of this change, since the presence of a device token no longer necessarily implies that the user has opted in to push.

Apple describes a ?silent push? as a notification that will wake up your app in the background to load content or perform some other processing by adding the ?content-available? flag. 

The ?silent? part refers to the ability to wake up the app in the background. However, it is also possible to send a silent push with notification text that opted-in users will see.

In the past, silent pushes were used for Newsstand apps. The silent push would trigger the download of new articles/issues in the background. When a user opted out of push, they would no longer receive these pushes.

The exciting new opportunity for marketers in iOS 8 is that Apple will now deliver ?silent? pushes even if the user has opted out of notifications. 

Also, ?silent push? is no longer just for Newsstand apps. Every app can take advantage of this ability to refresh content in the background, creating the most up-to-date, responsive experience possible the moment the user opens the app.

Users can still switch off your app?s ability to process a ?silent push? by means of the ?Background App Refresh? control. 

Even though Apple Push Notification service (APNs) will deliver a push marked ?content-available? to your phone, the OS will not wake up your app to receive it, effectively dropping it on the floor. 

However, opting out of ?Background App Refresh? is a lesser-known capability not directly associated with Notifications. You don?t access this preference in your Notifications Settings. It is located under General > Background App Refresh screen.

Though some users may go in and disable background refresh for an app believing it will conserve their battery life, they should know that Apple has designed this functionality from the ground-up to improve their overall user experience. 

Not only will apps have fresh content that is instantly available on open, these changes improve battery life and network usage as well.

Background refresh means that content gets delivered as soon as it is available, including overnight, when devices are more likely to be plugged in and connected to Wi-Fi. This makes for more even network usage and reduces direct battery usage during the day. 

This is also a much more efficient way to update content than waking up the app to poll for content. With a push, the app only wakes up or makes requests for new content when it knows for sure that new content is available. 

Apple does other things to preserve battery life. For example, APNs has built in rate limiting that prevents customers from sending too many silent pushes within a short period of time, and in the course of a day.

Background App Refresh is not enabled for apps by default: to take advantage of any background processing including ?silent push,? the app developer has to enable this at build time by including the 'remote-notification? background mode in the app's capabilities. You can also use background push to trigger a content refresh of widgets.

Local notifications look just like push notifications to the end user, but are triggered programmatically, either directly, at a scheduled time, or triggered by crossing a geographical boundary. 

Prior to iOS 8, users had no control over the display of local notifications. Some apps even took advantage of this feature to get around opt-in user preferences. 

Because there is no way to visually distinguish a local notification from a push-based notification, this frustrated users who thought they had opted out of push but continued to see local notifications.

With iOS 8, Apple has linked display of both push and local notifications in the same opt-in choice. Opting out of notifications now blocks both local and push notifications.

IOS 8 created the new Location Services opt-in option, ?While Using the App,? to offer a more limited level of access than the ?Always? option, which allows the app to react to location changes at all times in the background. 

The user can enable or disable these under Settings > Privacy > Location Services.

Many leading brands are already taking advantage of the new ?While Using? setting, including Twitter, Zillow, United, Instagram and Evernote. These companies believe they can see higher opt-in rates by asking for less location information. 

A good rule of thumb is to only ask for what you need and if you do need to ask for more, make the strongest possible case before asking for it.  

Apple is enforcing this behavior by requiring brands to provide explanatory text when they prompt the user to opt-in to location services. This will help users make more informed decisions about sharing their location data.

IOS 8 also makes it easier to link users directly to their push and location settings screen to change their opt-in settings. Now if you can give users a compelling reason to opt-in, you can link them directly to opt-in settings to take action immediately.

Finally, users who select the Always option will receive an occasional re-prompt asking them to re-confirm their consent to allow the app to continue to always track their location.

This new OS behavior in particular is surprising, and will likely reduce the percentage of users opted-in to always share their location. 

App publishers planning location-enabled features for iOS 8 should take steps to confirm the value and necessity of this level of tracking, while also educating users on the unique value it offers.

IOS 8 offers many exciting capabilities to reduce friction for bidirectional communication between users and the apps they trust with space on their phones and in their lives. 

To take advantage of this opportunity, marketers must plan ahead and maximize value for their consumers.