For Developers

Learn how Nami helps mobile app developers.

In-app purchases and subscriptions are notorious for being a hassle to implement, let alone test and maintain. We want to help developers stay focused on building a great app experience.

To start, Nami eliminates all of the platform-specific client-side and server-side purchase integration points.

For instance, if you're building an iOS app this means we simplify your use of StoreKit, handle receipt validation, and stand-up the backend to consume Apple's Server-to-Server notifications.

For Android apps, Nami takes care of the complexity of working with the Google Play Billing library, validating purchase tokens, and consuming the real-time developer notifications to make sure your app users' purchase state is up to date.

That's just the beginning! In this article, learn more about how Nami helps developers.

Adopting In-App Purchases on Apple Platforms

Nami helps make it easier to adopt in-app purchases (including subscriptions) on Apple's App Store platform.

Apple's StoreKit is well-known to be one of the more complex developer frameworks to incorporate into your app. Additionally, new App Store Connect server-side APIs are both necessary and complex to integrate for subscription apps.

Both can be quite frustrating to implement and test, leading to App Review pitfalls.

Nami solves this, by simplifying the integration points to one (the Nami SDK) allowing you to follow Apple requirements and best practices without the pain.

Specifically, Nami automatically handles three key integration points:

StoreKit Purchase Flow
The Nami SDK abstracts away much of the complexity required to utilize StoreKit. For example, the Restore Purchase flow or getting In-App Purchase SKProduct details are handled for you automatically.

Receipt Validation
Nami interfaces with the App Store's receipt validation APIs so you don’t have to do any client or server-side receipt validation.

Server-to-Server Notifications
Nami listens for Apple's Server-to-Server notification events on your behalf so you don't need to stand up a server. This provides on-going monitoring of key lifecycle changes so your app can adapt accordingly.

To have Nami listen to Server-to-Server notifications on your behalf, see Apple Setup .

Easier Purchase Testing
Besides implementation details, the Nami SDK helps simplify your purchase testing so you can test purchase flows without managing test users or running up against tedious system prompts just to see how your app reacts to purchase state changes.

Adopting In-App Purchases on Android

Nami helps make it easier to adopt in-app purchases (including subscriptions) on Google's Play Store platform.

Working with the Google Play Billing library can be tricky. Google releases major updates to the library every year and staying on top of all the latest changes and requirements can take a lot of effort.

Additionally, an implementation of IAPs that meets all of Google's recommendations includes having a server for both purchase token validation and processing of real-time developer notifications.

Nami solves this, by simplifying the integration points to one (the Nami SDK) allowing you to follow Google's requirements and best practices without the pain.

Specifically, Nami automatically handles three key integration points:

Google Play Billing Purchase Flow
The Nami SDK abstracts away much of the complexity required to utilize the Play Billing Library, including dealing with acknowledging purchases, pending purchases, and other complex cases.

Purchase Token Validation
Nami interfaces with Google's APIs to validate the purchase token so you don't have to write any client or server-side code. Nami validates purchase tokens server-side to help reduce fraud in your app.

Real-Time Developer Notifications
Nami listens for Google's Real-Time Developer Notifications (RTDN) events on your behalf so you don't need to stand up a server. This provides on-going monitoring of key lifecycle changes so your app can adapt accordingly.

To have Nami listen to RTDN events on your behalf, see our RTDN setup guide .

Easier Purchase Testing
Besides implementation details, the Nami SDK helps simplify your purchase testing so you can test purchase flows without managing test users or running up against tedious system prompts just to see how your app reacts to purchase state changes.

Cloud-Based Paywall Screens

Nami moves app paywalls to the cloud.

From a developer perspective, this means you can shift day-to-day management to the non-developers on your team, freeing your time to work on other critical work.

There are two supported use cases to use Nami as your PaywallPaywall - A paywall is a specific type of Call-To-Action (CTA) that is asking your users to make a purchase in your app. It is the visual presentation of your paid products to your users. solution:

Linked Paywall
Connect your paywall code to the Nami SDK's paywall object, so you bring the user interface but can still shift some management responsibility to our web-based Control CenterControl Center - The Nami Control Center is our web platform that allows you to control the Nami experience in your app from the cloud..

Use our Paywall Creator
We provide a native user interface implementation that you can use to fully create and manage from the cloud. This allows you to save a ton of time by turning over complete control of the paywall to non-technical product and marketing members on your team.

Additionally, instead of hard coding business logic related to when and how your paywall is displayed, you can also shift management of this to the cloud and the non-developers on your team.

Eliminate Hard-Coded Rules
Many apps depend on hard-coded rules to govern when a user is presented your sales sheet. Nami allows you to shift these rules to the cloud, so they can be easily managed and updated in real-time. Read more about managing business rules by creating a campaign.

How to Evaluate the Nami Solution

We have tried to make it straightforward to evaluate Nami through the following resources:

Documentation
You're already here on our documentation portal. Here you'll find Guides and our SDK Reference documentation as well as links to our GitHub repository where you can find the Nami SDK.

Sample Apps
In addition to code snippets you'll find throughout our documentation, we provide sample app projects that you can compile and run.

📘

Sample apps for other platforms are coming soon.

Request a Demo
If you or someone on your team would like to see Nami in action, send us a demo request.

Create a Free Account
Get access to all of Nami’s core features without setting up billing or committing to a paid plan. Create your account in moments to start your evaluation.

Minimal Code to Get Started
If you're ready to try Nami in your own project, you can get started with just a few lines of code. Our Add the SDK article will guide you through the steps.

Designing the Nami SDK
We know it's an honor to be included in your app, and we take our responsibility seriously. To get more insight into how we think about SDK design, review blog post on SDK Design Goals.

App Standards
In order to maintain high standards, our customers need to adhere to application standards.

Developer Support
We're also available to provide developer support if you have a question or want to walk through implementation details specific to your app. Please let us know, we'd be happy to help!


Did this page help you?