Choose the first pilot surface and document why it should be web, native or cross-platform.
FOUNDING ROLE BRIEF / PLATFORM / 03 OF 05
Senior Mobile App Developer, iOS and Android
Choose and build the smallest mobile surface the first Terminal pilot needs, beginning with private continuation or staff handoff rather than an entire fleet app.
THE ROLE / WHAT YOU OWN
About this role.
The current QR only opens the public demo on a phone; it does not transfer route, answer or session state. Staff handoff and a stateful phone journey are pilot work. Your first decision is whether that pilot needs a responsive web flow, one native app or a shared cross-platform shell. Evidence, not the job title, decides.
You are the first dedicated mobile hire, so you set the smallest credible architecture and the bar. The first surface must survive venue reality: patchy Wi-Fi, shared devices, loud floors and staff who have thirty seconds, not three minutes.
THE RAMP / START WITH WHAT EXISTS
Your first 90 days.
Every role starts with real work on the current software prototype and the first pilot plan. We will agree the milestones together and measure the result.
Connect one private-continuation or staff-handoff journey to the software demo end to end.
Deliver one pilot-ready build with authentication, recovery, telemetry and a measured usability baseline.
RESPONSIBILITIES / THE WORK
What you will do.
- 01
Choose and build the smallest mobile architecture the first paid pilot requires
- 02
Ship one staff-handoff or private-continuation journey with a clear completion event
- 03
Make that journey recover cleanly from poor venue connectivity
- 04
Implement only the identity, access and audit boundary required for the pilot
- 05
Own delivery, telemetry and release quality for the selected surface
- 06
Add routes, alerts, offline sync or a second platform only when evidence earns the scope
TECH / THE STACK
What you will work with.
The current Terminal is a local software demo. Deployment profiles may combine local, edge and cloud components; every provider must earn its place on latency, privacy, cost and reliability.
Decision first
- Responsive web, native or cross-platform based on pilot constraints
- A thin API boundary around continuation and handoff
- Measured latency and recovery behavior
Native when justified
- Swift and SwiftUI
- Kotlin and Jetpack Compose
- Push, offline state and device capabilities only where the journey requires them
Delivery
- Automated builds and tests
- One controlled pilot distribution path
- Crash and service telemetry
QUALIFICATIONS / THE BAR
What you bring.
Must have
- 6+ years of native mobile development with shipped apps on both platforms
- You have built real-time, connected apps, not only content screens
- Offline-first thinking and evidence you have applied it in production
- Fluent in the full store lifecycle: signing, review, phased rollout, crash triage
- Pragmatic about shared code: you choose per feature, not by ideology
Bonus points
- Kotlin Multiplatform experience
- Bluetooth or hardware integration work
- 3D, maps or AR on mobile
- Enterprise or MDM-managed device fleets
THE CULTURE / DAY TO DAY
How we work.
EVIDENCE OVER OPINION
Prototypes, evaluation harnesses, non-team tests and pilot measurements settle debates. The best argument is inspectable evidence.
PROTOTYPE TO PILOT
Work moves from the current software demo to hardware tests and then to a bounded venue pilot. Each stage is labeled, measured and allowed to fail honestly.
SMALL AND SENIOR
No layers, no committees. Five hires, two founders, one room when it matters.
DESIGNED FOR REAL FLOORS
We test for noise, glare, accessibility, latency and failure before a venue depends on the system.
WHAT WE OFFER / TERMS IN WRITING
Know the terms before you decide.
Cash and equity bands, operating location, employment jurisdiction and work-authorization policy are not yet published. Before an interview process advances, we will supply them and separate cash, equity, vesting and any profit-sharing terms in writing.
- A written offer that separates cash, equity, vesting and any profit-sharing terms
- Role scope and decision rights agreed before the start date
- Operating location, employment route, work authorization and travel expectations confirmed before interviews advance
- Direct work with both founders and senior ownership of a defined product layer
- A working pattern agreed for the role, including field research and pilot travel where needed
- A hardware and tools budget agreed before the start date
APPLY / PLATFORM
Tell us what you would build first.
Twelve months from now, people in the first pilot should be able to continue a route privately, and staff should resolve a handoff from an app you built. Send a short note with the apps you shipped, on both stores, and the hardest production incident they survived. A conversation with a founder follows within days.
Express interest in Senior Mobile App Developer, iOS and Android