Skip to main content

​
Overview

Reelevant brings the same personalisation engine that powers web experiences to your native mobile apps. Since mobile apps render their own UI with native components, the integration model is headless — Reelevant provides the personalised data, and your app handles the rendering.

Reelevant Mobile SDK

Native SDKs for Android, iOS, and Flutter with unified analytics and personalization. Typed responses, auto-identity, click tracking.

Reelevant as API (JSON)

Call the Reelevant runner from your mobile app and receive structured JSON data. Render it with your native iOS, Android, or cross-platform components.

​
Why personalise mobile?

​
How it works

Your mobile app integrates with Reelevant the same way a headless web frontend does:
1

Create a JSON Template

Define the schema and variables in the Reelevant platform. The schema describes the fields your app expects (product names, prices, image URLs, etc.).
2

Build a workflow

Connect datasources, add conditions and splits, and use a JSON Template output node. Bind each variable to a datasource field.
3

Call the runner from your app

Make a simple HTTP GET request from your iOS/Android/Flutter app. Pass the user identity for personalisation.
4

Render natively

Parse the JSON response and render it with your native UI components — SwiftUI views, Jetpack Compose composables, Flutter widgets, or React Native components.

​
Push and in-app surfaces

Push notifications and in-app surfaces are served by your push provider, not by Reelevant. Two integration modes exist, and they can be combined in the same app. Image-URL mode resolves the Workflow at display time, so content stays fresh after the send. JSON mode resolves it at send time, which is required when the notification copy itself must be personalised — the trade-off is one Runner call per recipient inside the sending window.
Some push providers only render plain text on the lock screen. In that case, deliver the personalised visual on the notification centre card or an in-app scene, and keep the lock screen copy generic.
Product-side setup for each surface is documented in the push and in-app integration guide.

​
Next steps

Technical Integration

API endpoints, response format, and mobile-specific code examples (Swift, Kotlin, Flutter, React Native).