The work
You'd be the person making the thing real, turning a well-considered set of designs and decisions into a cross-platform app that runs on iPhone and Android. Mobile-focused, but genuinely end-to-end: front-end UI, backend data and logic, the architecture decisions that hold them together, and the pipeline that gets it onto people's phones.
The product is in stealth for now, so there's only so much we can share publicly. Happy to walk through it properly under NDA.
Who we're looking for
You're experienced with modern cross-platform frameworks (Flutter, React Native, and similar), and comfortable working across them. Real mobile products often need more than one stack as they grow, and we want someone who can move with that.
What matters most is that you've shipped real apps to both the App Store and Google Play, and made them feel native on each.
Across the stack you should be comfortable with:
- Mobile UI. Declarative component patterns, design-system implementation (tokens, not hardcoded values), animations and gesture handling, form and validation flows, native module bridges when something needs them.
- Backend. Document-style databases, serverless functions, file storage, authentication including OAuth providers (Apple, Google), and the security and permissions layer that sits over all of it.
- Privacy and data protection. Thoughtful about what data is collected, where it lives, who can access it, and how it's removed when asked. Especially when the product touches sensitive territory.
- Architecture. State management choices, navigation, deep linking, offline-and-sync thinking, performance budgeting, schema migration patterns. Knowing when to reach for realtime listeners and when one-shot reads will do. Those decisions matter at scale.
- Testing: manual and automated. Unit tests for logic, integration tests for components, end-to-end tests for the critical paths, and disciplined cross-device QA on real hardware. With AI tools accelerating code output, we lean harder on testing, not less.
- Shipping. Cloud build pipelines, TestFlight + Play Console Internal submissions, release management, crash reporting, sensible analytics wiring. Familiar with App Store and Play Store policies, age ratings, and the privacy declarations both stores now require.
- Debugging instincts. Across native logs, network traces, store rejection reasons, push delivery failures, OAuth weirdness: the messy real-world stuff.
We particularly value:
- Cross-platform parity discipline. Every feature lands on iOS and Android together. No "iOS first, Android later".
- An accessibility instinct. Readable type, proper hit targets, dynamic type support, screen-reader friendly. The people who'll use this product depend on it.
- A feel for warm, plain-English UI. Copy that sounds like a person, not a system.
- Strong written-spec literacy. You can read a thoughtful brief and run with it without needing every step laid out.
- A critical eye for AI output. You use LLMs as tools, not as authority. You can spot a hallucinated API or a deprecated pattern, and you test what comes out before it ships.
- Delivers on milestones. You hit what you commit to, and flag risks early rather than at the deadline.
- Clear async communication. Much of our work happens in writing. You ask the right questions, surface decisions cleanly, and don't disappear between updates.
Nice to have
- Experience in sensitive domains (healthcare, eldercare, accessibility-led products)
- Wearable integrations (Apple HealthKit, Google Health Connect, Oura, Garmin)
- A portfolio that shows you care about how things feel, not just whether they work
How this works
- Milestone-based to start. The project will initially run on agreed milestones, with payment against each as it ships. This suits the stage we're at on both sides, and can evolve as the work does.
- Direct. You work with the founder. Decisions happen in conversation, not in a Jira ticket queue.
- Long-term potential. This isn't a one-off. If it works for both sides, the role can grow as the product does. Beyond this build, into ongoing platform work, new platforms, and integrations.