phoenix
phoenixPhoenix - Your AI Assistant
Inactive session will be ended in 24 hours
End Session

React Native / Expo developer to support app ownership migration

  • Posted:
  • Proposals: 45
  • Remote
  • #4525918
  • OPPORTUNITY
  • Paused
Thompson J.Cornelius O.David O.Peter F.Amaneet B. + 40 others have already sent a proposal.
  • 2

Description

Experience Level: Entry
React Native / Expo developer to support app ownership migration (iOS + Android, Supabase, RevenueCat)

About the project
We are acquiring a live AI calorie-tracking app on the App Store and Google Play. The seller is transferring the app, code and accounts to us over the next few weeks. We need an experienced developer on our side to set up our accounts, receive and check every transfer, and make sure we can build, run and release the app independently.

Tech stack
- Expo SDK 54, React Native, TypeScript, expo-router
- EAS Build and EAS-managed signing (no CI/CD yet)
- Supabase: Postgres, Auth (email, Apple, Google), Storage, 16 Edge Functions, scheduled jobs
- OpenAI GPT-4o, called through Supabase Edge Functions
- RevenueCat subscriptions (iOS and Android)
- Firebase (FCM push, Google Sign-In), Sentry, PostHog, Vercel website

Scope of work
1. Help set up our accounts so they are ready to receive transfers: Apple Developer, Google Play Console, GitHub, Expo, Supabase, RevenueCat, Firebase, OpenAI, Sentry and PostHog.
2. Check each transfer against our handover checklist as it arrives, and tell us about anything missing or incomplete.
3. Build and run both apps from a clean checkout of the transferred repository using EAS.
4. Check the Supabase project: migrations, row-level security, edge functions, scheduled jobs and secrets. Switch to our own OpenAI key and turn on backups.
5. Rotate all credentials and API keys after handover. Create a new APNs key, and confirm Sign in with Apple, Google Sign-In and push notifications still work.
6. Confirm RevenueCat is set up correctly (store notifications, webhook to Supabase), and run sandbox test purchases on iOS and Android.
7. Release a new build to both stores from our own accounts.
8. Confirm the seller's access has been removed from all accounts.
9. Write a short handover report: how to build and release the app, where everything lives, and any risks or issues you found.

You will work alongside the seller's developer, who provides support until 31 December 2026. You may also be asked to review two new features the seller is building and confirm they work as described.

What we're looking for
- Proven experience shipping Expo / React Native apps to both stores with EAS
- Hands-on Supabase and RevenueCat experience
- Experience with App Store Connect and Google Play app transfers is a strong plus
- Clear written English and regular progress updates
- Available from mid October to December 2026
- Willing to sign an NDA


Ongoing work
If this goes well, there is potential for recurring monthly work from January 2027 to manage and maintain the app. This would include monitoring crashes and performance, dependency and Expo SDK updates, store releases, Supabase maintenance, small fixes and improvements, and new features quoted separately.

To apply, please include:
1. Two or three Expo / React Native apps you have shipped, with store links
2. Your experience with Supabase and RevenueCat
3. Whether you have handled an App Store or Google Play app transfer before
4. Your availability over the next 6 to 8 weeks

New Proposal

Create an account now and send a proposal now to get this project.

Sign up

Clarification Board Ask a Question

  • Asad C.

    Is the existing GitHub repository already complete, including Supabase migrations, Edge Functions, configuration files, and EAS build settings, or are some components maintained separately by the seller?

    Are the Apple Developer and Google Play Console accounts already created and verified under your ownership, or will account setup and app transfer coordination need to happen first?

    Do you have a formal handover checklist and access to the seller's developer for resolving missing credentials, configuration gaps, or failed builds during the transition?

  • CYTNHIA W.

    One important question before we begin: Will the seller transfer the existing Supabase and RevenueCat projects directly, or are you planning to migrate them into newly created accounts and projects? This distinction determines how we preserve existing user identities, subscription entitlements, webhook configurations and production continuity during the handover.