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

Finish & ship existing React Native app to iOS and Android

  • Posted:
  • Proposals: 29
  • Remote
  • #4505797
  • OPPORTUNITY
  • Paused
Mohammed A.Williams O.Amir S.Johven M.Ankur M. + 24 others have already sent a proposal.
  • 1

Description

Experience Level: Expert
We have a near-complete React Native (Expo) app with a Supabase backend, a health and wellness tracker. The core is built and has passing unit tests. We need an experienced Expo developer to complete the remaining work and ship it to both the App Store and Google Play.
Scope:
Set up the EAS build and submit pipeline for iOS and Android
Implement in-app purchases on both stores (RevenueCat is integrated but on a test key)
Complete features currently stubbed: charts, push notifications, and Apple HealthKit / Android Health Connect
Produce store assets (icon, splash, screenshots, listings) and complete the App Store privacy and Google Play data-safety forms
QA on real iOS and Android devices and fix issues
Submit and shepherd both apps through review
Requirements:
Demonstrable Expo apps live in both stores (please share links)
One contactable client reference
Comfortable working in an existing codebase to a defined brief, not building from scratch
Terms: Fixed price per milestone. A mutual NDA is required before any repository access. Please quote per milestone against the scope above.

New Proposal

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

Sign up

Clarification Board Ask a Question

  • VCONN P.

    Hi Olga,

    Could you please answer the following for scope clarity:

    1. Which Expo SDK version is the project currently using?

    2. Have the Apple Developer and Google Play Console accounts already been created and verified?

    3. Is RevenueCat already configured with the production products, or is only the sandbox environment available?

    4. Are the chart designs already finalized, or do they still need implementation decisions?

    5. Are HealthKit and Health Connect limited to reading health data, or will the app also write data?

    Looking forward to your response.

    Best,
    VConn Pvt Ltd

  • CYTNHIA W.

    One question: is the HealthKit/Health Connect integration currently stubbed at the permissions layer only, or has any of the data-read/write logic been scaffolded? That will determine the effort for that milestone specifically.

    Olga M.5 hours ago

    Good question. It's stubbed at the surface only. The HealthKit / Health Connect entry points and permission prompts exist in the UI, but no data-read logic has been scaffolded behind them. The app currently runs on manual input; these integrations are the planned auto-source, not yet wired.
    So scope that milestone as building the read pipeline end to end: request authorisation, query the relevant types (sleep duration and quality, steps / active energy, HRV, and the cycle category on HealthKit, with Health Connect equivalents on Android), normalise them, and feed them into the same fields the manual entry already populates. The manual path stays as the fallback when permission is denied or data is missing.
    It's read-only. Nothing needs to be written back to HealthKit / Health Connect, which should keep the effort down. Happy to confirm the exact Expo SDK and RN versions and walk you through the relevant module under NDA before you finalise the number.

    CYTNHIA W.5 hours ago

    Thanks, Olga and that's very helpful and exactly the clarification I needed.

    Having the UI entry points and manual data model already in place makes the scope much clearer. I would approach this milestone by implementing the full read pipeline for both HealthKit and Health Connect: handling permissions, retrieving the supported health metrics, normalising the data into a common model, and feeding it into the existing manual-entry workflow while gracefully falling back to manual input whenever permissions are declined or data isn't available.

    The fact that it's read-only simplifies the integration considerably and reduces both implementation complexity and testing effort.

    One final question: are there any target OS version requirements (minimum iOS/Android versions) or specific Expo SDK / React Native version constraints I should factor into the estimate? Once I have that, I should be able to provide a realistic timeline and fixed-price figure.