Mobile Developer — React Native / Expo

About the role

We build a consumer wellbeing app for iOS and Android. It is already live in both stores, has paying subscribers, and is under active development. We are a small team, and we are hiring the person who will own the mobile app.

This is not a greenfield project and it is not a role on a large mobile team. The codebase exists — React Native and Expo, TypeScript, Supabase on the backend, RevenueCat for subscriptions — and it was built quickly. Your job is to take it over, make it solid, and keep shipping. You will be the only mobile developer, which means the app is yours: the architecture, the release pipeline, the store listings, the crash reports, and the decisions about what to fix versus what to live with.

You will work directly with the founder and a designer. There are no layers between an idea and a release, which is the appeal of the job and also the demand of it. We need someone who is comfortable being the person who knows how the app works.

Fully remote, with a few hours of daily overlap for calls and reviews.

What you will own

The product roadmap

• Build features end to end — from a design in Figma and a conversation with the founder, through implementation in TypeScript and expo-router, to a release in the App Store and Google Play.

• Break down loosely specified ideas into shippable increments and tell us honestly what each one costs.

• Work on core experience features: audio recording and playback, animated screens, journaling with offline-tolerant sync, daily progress and streak state, and push notifications.

Subscriptions and revenue

• Own the paid side of the app end to end: paywalls, free trials, entitlement checks, renewal and cancellation states, restore purchases, and the platform deep links for managing a subscription.

• Build and iterate on retention flows — cancellation off-ramps, discount offers, and win-back prompts — keyed off subscription state from RevenueCat and our own backend.

• Handle the unglamorous parts properly: receipt and entitlement edge cases, users whose store state and backend state disagree, and refunds. Billing bugs cost real money and real trust.

A consistent experience on every device

• Extend and enforce our shared responsive layout system — breakpoints, spacing scale, and typography scale — instead of hard-coding values per screen.





• Make every screen render correctly from a 360 × 640dp Android phone up to a tablet, in dark theme, including non-Latin script typography.

• Keep our device test matrix green and stop layout regressions before they ship. We have a real backlog here and you would be the person to close it.

• Take accessibility seriously — VoiceOver and TalkBack, dynamic type, contrast, and touch target sizes.

Release engineering and quality

• Run EAS Build and EAS Submit, manage release channels, and use EAS Update to ship fixes over the air without waiting on store review.

• Own both store listings: submissions, review responses, privacy disclosures, and staged rollouts.

• Maintain the test suite — unit tests, component tests, and snapshot tests across device profiles — and keep CI meaningful rather than decorative.

• Monitor crash reporting and analytics, triage what comes in, and close the loop with fixes and regression tests.

• Keep upgrade debt low by moving the app forward across Expo SDK versions on a deliberate schedule, not in a panic.

What we are looking for

Required

• 3–5 years of professional software development, including at least 2 years building production React Native apps.

• Expo in production, not just in a tutorial. You have used EAS Build, worked with development builds rather than staying inside Expo Go, shipped to both stores, and pushed an over-the-air update to real users.

• In-app subscriptions on both platforms. RevenueCat ideally, or direct StoreKit and Play Billing — you understand entitlements, trials, renewal, grace periods, and restore, and you have debugged a subscription that was in the wrong state.

• Strong TypeScript and contemporary React: hooks, composition, and a clear sense of when state belongs local, in a store, or on the server.

• Experience with a backend-as-a-service such as Supabase or Firebase — auth, a relational or document store, row-level security, and realtime subscriptions.

• Client state management with Zustand,



Redux Toolkit, or similar, and comfort with offline behaviour and cache invalidation.

• Comfort taking over code you did not write. Much of the first months is reading, understanding, and improving an existing codebase. Tell us about a time you inherited one.

• Native-layer literacy: what app.json and config plugins actually generate, how to read an Xcode or Gradle build failure, and how to approach a native crash.

• Familiarity with App Store and Google Play submission requirements, review guidelines, and privacy disclosures.

• Genuine self-direction. As the only mobile developer, no one will unblock you day to day. We need someone who makes reasonable calls alone, communicates clearly in writing, and flags problems early.

• Professional working proficiency in English.

Nice to have

• Audio recording and playback on mobile (expo-audio / expo-av), including background and interruption handling.

• Reanimated and Gesture Handler for non-trivial animation and interaction work.

• NativeWind, Tailwind, or another token-driven styling system.

• Migrating an app to the React Native New Architecture (Fabric, TurboModules).

• End-to-end testing with Maestro or Detox, and CI/CD for mobile.

• Internationalisation, right-to-left layout, or typesetting non-Latin scripts.

• Writing custom Expo modules or config plugins in Swift and Kotlin.

• Paywall experimentation, subscription analytics, or app store optimisation.

• Having been the sole developer on a shipped consumer app before.

Our stack

This is what the app is actually built on today. You do not need every line of it on day one.

• Framework — React Native with Expo, TypeScript, expo-router (file-based routing)

• Backend — Supabase: Postgres, auth, row-level security, realtime channels

• Payments — RevenueCat (react-native-purchases): entitlements, trials, offers, App Store & Play Billing

• State — Zustand stores, custom hooks, AsyncStorage for local persistence

• UI — Shared responsive primitives and design tokens, dark theme, animated and audio-driven screens

• Quality — Jest + React Native Testing Library, snapshot tests across five device profiles, CI audit scripts

• Release — EAS Build, EAS Submit, EAS Update (OTA), App Store Connect, Google Play Console

Skills:- Expo and EAS

📌 Expo experience Mobile developper (India)
🏢 Zan - Zari Group
📍 India