Platform support

The @akin-travel/partner-sdk is a React convenience layer — providers, hooks, and headless components. It targets:

Every other browser stack — Vue, Angular, Svelte, plain HTML, or a server-rendered site — uses the framework-agnostic Embed widget: a <script> tag plus Web Components (<akin-login>, <akin-loyalty-card>, <akin-tier-progress>) built on the same core, with Shadow-DOM style isolation and partner-token theming. Native mobile and back-end services talk to the GraphQL API directly. None of these is a separate product: anything the SDKs do, you can do against the API.

React Native

There is no React Native package today, and we haven’t committed to a timeline. A dedicated RN SDK is under evaluation; this page will be updated if that changes — we won’t promise a date we can’t keep.

That’s rarely blocking, because the recommended mobile pattern doesn’t need a client SDK at all:

Backend-mediated (recommended)

If your backend already authenticates your users, read their loyalty standing server-to-server and serve it to the mobile client as cached state:

1. Your React Native app talks only to your backend, as it already does.
2. Your backend reads the member’s tier and points from AKIN server-to-server — keyed by email, authorized on your partner API key, no member sign-in or token exchange. From Node, the typed Server SDK wraps these calls for you.
3. Your backend caches that standing and returns it to the client however it serves the rest of its data.

The member never touches AKIN auth, the mobile client never holds a partner API key, and you control caching and refresh. See Server-to-server reads for the request shape, or the Server SDK (Node) for a typed client.

If you instead need members to sign in to AKIN from the mobile client, the GraphQL API and its auth exchange work from any HTTP client — see Using the API and Authentication — there’s simply no React-Native-specific wrapper to lean on yet.