Expo (React Native) dev — small app + publish it to the App Store & Google Play, and teach us how

We need someone to build a small Expo app and — more importantly — get it published on both the Apple App Store and Google Play, then teach us how to release updates ourselves. We are an Australian cleaning and restoration company with an in-house software team. We build and run our own production web system (Python/Django, JavaScript, REST APIs, our own Linux servers). What we've never done is publish a MOBILE app — signing, provisioning, TestFlight, store review. That specific gap is what we're hiring for. This is deliberately a small job. Please don't quote it like a full product build. WHAT YOU'D BUILD A minimal customer app with four screens, and nothing more: 1. Log in / log out (email + password against our API, token stored securely) 2. "My jobs" — a list of the customer's jobs, pulled from our API 3. Job detail — read-only 4. Delete my account (Apple requires this) That's the whole feature list. No booking, no scheduling, no payments, no push notifications, no photo uploads. Those are out of scope — we'll build them ourselves later. We provide the backend. You build no server. Our REST API is just 5 endpoints, fully documented, with a staging server and test logins ready for you. WHAT WE ACTUALLY CARE ABOUT (THE REAL JOB) The app above is the easy part. Here's what we're really paying for: 1. Get it on the Apple App Store — under OUR existing Apple Developer account, not yours. Bundle ID, certificates, provisioning, TestFlight, privacy labels, submission, and seeing it through to approval. 2. Get it on Google Play — same, under OUR Play account. Package name, Play App Signing, internal testing track, Data Safety form, submission through to approval. 3. Teach us your release process. Record a walkthrough (~30-60 min) of the codebase and the release steps. Write the runbook. Then watch us push a release ourselves and correct our mistakes. The job isn't done until WE can ship an update without you. Important — you are not teaching non-technical clients. We are a software engineering team. We write and ship production code every day (Python/Django, JavaScript, REST APIs, Git, CI/CD, Linux servers we run ourselves). What we lack is specifically mobile store experience — signing, provisioning, TestFlight, App Store and Play review. That's the only gap. So this should be a fast, straightforward handover: talk to us like engineers, not like a client who needs hand-holding. You won't be explaining what a terminal or a Git branch is. Point us at the right commands and the right concepts and we'll take it from there. Please price the handover accordingly — it should be a short knowledge transfer between developers, not a training course. TECH - Expo (React Native), TypeScript. We've picked this on purpose: one codebase for both platforms, and EAS Build compiles iOS in the cloud so no Mac is needed. If you'd strongly recommend something else, make your case — but Expo is the default. - Code must be plain, boring, conventional Expo. One screen per file, one typed API client file. Our own team will extend this app afterwards without a mobile specialist, so clever abstractions are a problem, not a feature. - Code is delivered into our existing Git repo, in a self-contained "mobile/" folder. - Work-for-hire: we own the source and all signing material on final payment. No GPL/AGPL dependencies. MILESTONES (fixed price — please quote each one) Milestone 1 — App built: four screens running against our staging API on Android and iPhone. Milestone 2 — Signed builds live on TestFlight and the Play internal testing track, installable on our phones. Milestone 3 — Approved on both stores, walkthrough recorded, runbook written, credentials handed over, and we've done a release ourselves under your supervision. ONE RISK, STATED UP FRONT Apple sometimes rejects simple apps under guideline 4.2 (Minimum Functionality). We know. Milestone 3 includes seeing the app through review, so please factor in one round of resubmission, and tell us in your proposal how you'd handle a 4.2 rejection. If Apple ultimately demands more features than this brief covers, we'll treat that as separate additional work — we're not going to blame you for Apple. WHO THIS SUITS An intermediate developer who has personally shipped apps to both stores and has dealt with the review process. We're not looking for elaborate UI work — we're looking for someone who knows the store pipelines cold and is happy to teach. If you'd rather publish under your own developer account, or you're not comfortable teaching us to do releases without you, this isn't the right job for you. IN YOUR PROPOSAL, PLEASE INCLUDE 1. Your fixed price, broken down by the three milestones above. 2. Your timeline in working days (excluding store review waiting time). 3. One or two apps you've put on both stores — links. 4. Confirmation you'll publish under our store accounts and hand over every credential. 5. Confirmation you'll do the recorded walkthrough and supervise us through a release. 6. How you'd handle an Apple 4.2 rejection. Shortlisted applicants get the full written brief.