We are pleased to announce the release of our latest update: v2.0!
|
The main focus for this release are updates to the mobile code library, with the most significant updates relating to how we prompt for location sharing permissions. Specifically, we can now display a “prominent disclosure” dialog, with customizable text, informing the user why the app is requesting access to location information. An example of such a dialog is shown here. This addresses requirements from Google for such a disclosure on all Android apps that access location in the background, and also conforms to best-practices in end-user privacy for all platforms. It is also an important element in driving user adoption and ultimately stronger engagement and overall client satisfaction. Please see this guide for additional details related to this important feature. |
![]() |
Additionally, work has been done to increase flexibility for mobile app developers integrating the mobile library, and to lay the foundation at the mobile library layer for upcoming functionality enhancements around enhancing nudge delivery precision.
Larky strongly recommends upgrading to this version to take full advantage of these critical updates required for compliance with Google Play policies, as well as overall enhancements to resilience and performance. Please note that apps submitted to Google Play which do not comply with the requirement of displaying a prominent disclosure around location sharing may be rejected. As a trusted partner, Larky is committed to helping you comply with these requirements with minimal effort on your part.
Mobile Code Library
Updating to this version will require a small change to the line of code where you initialize the nudge® library. Please see this guide for complete instructions.
- New location permission prominent disclosure dialog
Displays a dialog with customizable text educating the user on the benefits and security of granting location permission. Required for all Android apps in the Google Play store, but also implemented as a privacy best-practice for iOS apps as well. - Dynamic configuration architecture
Enables numerous configuration items to be set and updated after the app has been built and submitted to the app store. Allows more flexibility during and after the implementation process. - Foundational updates for increased nudge® message delivery precision
Capture additional operational device details (unrelated to identity) that will enable greater control over delivery of appropriate messages. Examples include velocity, to allow selected messages to be delivered only when the user is traveling at a walking pace. - Security, performance and stability updates
Note: For Android implementations, nudge currently requires that you target Android 10 (SDK 29) for proper behavior around location permissions. If your app requires functionality provided in Android 11, please contact us.
Update (March, 2021): We have released an updated v2.0.1 library specifically for Android apps that target SDK 30. See this announcement for details.
Portal / Other
- Improved analytics export file formatting
Revised format for better consistency and usability, especially when performing further analysis in external tools like Microsoft Excel. - Enhanced message handling
Increased throughput, resilience and performance of push notification management framework - Foundational updates completed for upcoming feature enhancements
Includes framework updates required for improved campaign management and deep-linking to mobile app from taps on nudge® messages - Security, performance and stability updates

Comments
0 comments
Article is closed for comments.