As detailed in our latest Product Bulletin, we’ve been working on updates to our libraries to accommodate the latest mobile OS releases from Google and Apple.

Android 13 update

We are pleased to announce an update to our Android libraries for compatibility with Android 13. This update is recommended for Android mobile apps targeting API level 33. With this update (v3.2.0), the nudge library will conditionally prompt the app user for permission to receive push notifications - a newly-added runtime permission in Android 13. If the app already prompts for the new permission before the library is initialized, then the nudge library will respect the choice already made and not prompt again.

In addition to the notification permission prompt, the new version of the library also includes enhanced analytics that will improve the ability for our FI clients to measure and improve the effectiveness of their messaging campaigns.

We’ve also mitigated a few issues that were resulting in some apps crashing while in the background. These weren’t impacting users who were actively using the mobile banking app itself, and we only had reports of this from a few partners. Obviously this update is recommended for anyone experiencing those issues.

Full integration documentation is available here. For existing integrations, the only update required to utilize this new library is a change in the build.gradle file to reference `3.2.0` for the version number of the library itself. There are no changes to any code-related calls or parameters.

iOS 16 update

After thorough analysis and testing we’ve determined that the current version of our iOS library (v2.0.4) is fully-compatible with apps running on the newest iOS 16 release. No further update is required at this time.

On the roadmap - a new library architecture for the future

As detailed in an earlier Product Bulletin, we have previously released the nudge® Base library to allow partners to integrate a version of our platform that doesn’t utilize location-based triggers for messaging. This can smooth the overall development, UAT and app submission processes in instances where a client doesn’t need to utilize location in their overall messaging strategy.

Building on this, we are in the process of developing a nudge® Geo add-on library that, when paired with nudge® Base, will effectively replace the current “full service” library. There is no date yet on when we will end-of-life the current library. You will have plenty of notice and support in migrating to the new Base + Geo architecture - a process we intend to be as minimal as possible. 

Implementing Federation - a key to adding value and speeding the sales cycle

A final reminder that whenever you are considering the topic of a Larky nudge® library integration, we strongly recommend including Federation as part of that. We have a short article that discusses some of the details, and we’re happy to have both a technical and business strategy discussion around this topic. Essentially, our mutual clients — and our mutual prospects — want the functionality that Federation delivers: the ability to create highly targeted messaging to their account holders. Implementing Federation is not difficult, and having it removes a possible objection in the sales cycle, shortening your time to revenue. Please reach out directly to kurt@larky.com for more details.