The new Larky v4 nudge® library is compatible with apps that utilize location-based messaging as well as those that do not. Previously, we had two separate libraries, nudgeBase and nudgeGeo, to address these two designs. This new library architecture simplifies managing app builds when both options are offered.

Additionally, the new library design allows simpler control over your app user experience. Our previous libraries had a single initialization call that performed multiple operations, including prompting the app user for notification permission and location permission, as well as communicating the "Federation ID" value back to us after authentication. 

The new design offers a much lighter initialization call that only establishes communication with our backend code and handles any analytics events we track when messages are received and tapped. We've pulled out the permission prompting as well as the Federation ID handling into their own discreet calls. This allows you to place them appropriately (or ignore them entirely, if not required) within your preferred flow.

Overall, this new architecture will be simpler for our partners to implement and maintain over the long term.

This is the only version of our libraries to which new functionality, including the ability to add images in push notifications, will be added.

We will support our legacy libraries with security and OS compatibility patches through the end of the year. But they will be deprecated early in 2026.

Full details

See our integration guide here for full technical details on how to include the new library in your app.

We're here to help!

Have questions? Just reach out to us through the Submit a request link above, or email us at support@larky.com.