Overview
The Stay22 Mobile SDK turns travel intent in your app into well-timed accommodation offers.
Your users already tell your app where they're going — they book a flight, save an event, search a destination. The Stay22 Mobile SDK turns that travel intent into a new revenue stream: a single, well-timed local notification that opens a curated accommodation booking experience, with every booking attributed to you.
How it works
A traveler drops signals in your app — they search a destination, pick travel dates, save a place
You send those signals to the SDK — destination, dates, places, whatever you have — with a single call: Stay22.setTravelContext(...)
The SDK watches for exactly the right moment, then shows one local notification for that trip
One tap drops the traveler into a curated Stay22 booking experience for their destination and dates
Every booking is attributed to your partner ID (aid) and earns you affiliate revenue
There's no backend work on your side: you install the SDK, tell it about the trip, and Stay22 handles timing, relevance, and the booking experience.
One notification, well timed
The SDK is deliberately conservative — a spammy notification costs you user trust, so it only shows one when it's worth showing:
- One notification per trip. Setting a new travel context replaces any pending notification; it never stacks.
- Timed for relevance. Delivery waits until the user has left your app, after a delay tuned by Stay22.
- Local suppression. If the destination looks like home — the user's own city, or anywhere within a configurable suppression range — no notification is shown.
- Frequency capping. A cooldown prevents users from being notified too often, even across multiple trips.
- Fully configurable. Everything the user sees is yours to shape — title, message, grouping, badges, action buttons — with
{destination}and date placeholders filled in per trip. See Notifications & Events.
Notification timing, delays, frequency caps, and the local suppression range are managed by Stay22 per partner — you don't configure them in code. Reach out to your Stay22 account manager or support@stay22.com to tune them for your account.
Built around user consent
- Opt-in by design. Nothing happens until your app sets
Stay22.isEnabled = true— gate it behind your own consent flow, and users can opt out at any time. - No GPS. The SDK never requests location permission and doesn't track users; it only acts on the travel context your app explicitly provides.
- Standard notification permission. Notifications go through the OS permission prompt like any other — the SDK helps you request it and respects a denial.
- Privacy-manifest ready. The iOS SDK ships an Apple privacy manifest and has no third-party dependencies.
Requirements
| Platform | Minimum version | Language | Distribution |
|---|---|---|---|
| Android | Android 8.0 (API 26) | Kotlin | Maven — com.stay22:sdk |
| iOS | iOS 15.0 | Swift 5.9+ | Swift Package Manager |
Both SDKs are distributed as prebuilt binaries through public GitHub repositories:
stay22-android-sdk
Android SDK on GitHub — README, releases, and integration guide.
stay22-ios-sdk
iOS SDK on GitHub — README, releases, and integration guide.
Next steps
- Quick Start — install, initialize, and send your first travel context
- Notifications & Events — customize the notification and observe the SDK's decisions
- Testing & Troubleshooting — verify your integration in minutes