What Will Change in Location Marketing with iOS 11 Update

Location-based technologies and location services are widely used today for daily activities from social networking to finding a nearby restaurant or picking someone up from the airport. Knowing where their customers are located can help businesses identify where they need to provide service. As the smartphone user base grows, companies need to expand their audience through mobile apps. One problem is that not all developers ask for mobile permissions properly.

“Too often apps ask for location consent on first open without explaining clearly what it will be used for,” said mobile strategy adviser Steve Ricketts. This can hurt multiple businesses as users begin to turn down location permission prompts almost habitually.  This year, Apple announced some significant changes in iOS 11 that can increase user opt-in; namely, iPhone users are granted more selections and transparency in giving away their location, thus reinforcing their confidence in location services.

Location services

Bringing iBeacon support to Android

Beacons weren't born with Apple iBeacon

All the Beacon BLE phenomenon exploted since Apple introduced the iBeacon support on iOS 7. However, all the Bluetooth Low Energy technology and the possibility of creating stand-alone devices emmiting its own ID 24/7, were available before the iBeacon support on iOS. Most modern Android Phones have the necessary hardware and software to detect BLE Beacons, however Android does not provide developers the tools to facilitate the work in order to create an App that does not drain the battery (except in the not-yet-released Android L), like iOS does.

The Google solution

Google is aware of the need to provide a native support for Beacon scanning and discovery, so they have dramatically improved Bluetooth Low Energy beacon detection on the latest iteration of the Android Operating System (Android L). This version of the OS will allow developers to rely on the OS the beacon detection , like iOS does. However, Android will provide more flexibility to developers regarding the kind of beacons detected. The main problem about going with Google solution is that it will be available only for the L version of Android. A version that has not been released yet and due to the nature of this operating system, its market share will not be relevant until a year from now, taking into account the adoption rate of the latest released version (KitKat).

MOCA iOS SDK 1.2 Released

MOCA iOS SDK v.1.2

We are pleased to announce that we have just published the latest version of the MOCA iOS SDK.

Here is the Change-log:

Features:

  • SDK now supports iOS 6 (Analytics only) and iOS 7+ (Analytics and Proximity)
  • Weak binding for iOS 6 is now supported
  • You may know determine if proximity service is available by calling [MOCAProximityService isProximitySupported]
  • Proximity actions are now delivered in foreground mode and converted to local push notifications in background mode.

Bug fixes and improvements:

  • Various proximity engine fixes.
  • Zone/Place enter range bug fix.
  • Re-execute open url action bug fix.
  • Number of performance optimizations
  • CLBeacon CLProximity state change bug fix
  • AFNetworking symbol conflicts removed. You may now use AFNetworking module in your app.

SDK is available on GitHub.