# Mobile app analytics (https://talivia.com/docs/mobile-analytics)



Talivia mobile SDKs send app activity to the same collector used by your website. Use the same **Website ID** and **hostname** as your web tracker to see web and app activity in one workspace. A mobile app does **not** use the browser `script.js` tracker; Expo Web still does.

| App framework           | SDK                     | Status                              | Guide                                               |
| ----------------------- | ----------------------- | ----------------------------------- | --------------------------------------------------- |
| React Native / Expo     | `@talivia/react-native` | Published on npm                    | [React Native](https://talivia.com/docs/mobile-analytics/react-native) |
| Flutter                 | `talivia_flutter`       | Published on pub.dev                | [Flutter](https://talivia.com/docs/mobile-analytics/flutter)           |
| Native iOS / Swift      | Talivia Swift package   | Public Swift Package Manager source | [Swift](https://talivia.com/docs/mobile-analytics/swift)               |
| Native Android / Kotlin | Talivia Android module  | Maven Central release pending       | [Android](https://talivia.com/docs/mobile-analytics/android)           |

## What to record [#what-to-record]

1. Call `screen()` when navigation changes. No SDK observes your router automatically.
2. Call `track()` after a meaningful product action, such as completed onboarding or feature use.
3. Call `identify()` after login with your stable account ID. Call `reset()` on logout.

Initialize only when your consent and privacy settings permit analytics collection. Do not put a private server API key in the mobile app.

## Measurement boundaries [#measurement-boundaries]

* The same Website ID puts web and app events in one workspace. Matching stable user IDs link known customer identity records, but current funnels still group by visitor token; they do not merge cross-device journeys.
* SDK queues hold at most 100 events **in memory**. App exit clears pending retries. Do not use them as durable offline storage.
* SDKs do not automatically track installs, deep-link campaign attribution, app-store purchases, or verified revenue. Send authoritative purchase data from a trusted backend or payment integration.
* If your app also has a website, keep the website tracker on web pages and the mobile SDK in native app code.

Explore the [mobile app analytics overview](https://talivia.com/mobile-app-analytics) for platform links and product context.