Deliverables
What we ship.
See it before you pay
We don’t promise a photocopy of every website page. We do promise an app that feels like your product—your look and the screens that matter—with previews along the way so you’re not buying blind.
Native mobile work, not a web shell
- → Swift / SwiftUI (iOS) and Kotlin / Jetpack Compose (Android) for the pages and flows in your agreed scope — real UI code you open in Xcode or Android Studio, not a permanent WebView.
- → Clear alignment from your product: what we learn from your code and your answers, so the build matches what you approved.
- → Fully wired delivery when you choose it — data and APIs hooked up so you are not starting from blank screens.
In your handoff zip
README + JSON artifacts
Session README, scan output, native plan, reviews, parity and intent — a paper trail of what was agreed and generated.
Native source
Plan-row scaffolds and delivery entry files (scaffold or fully wired) — Swift for Xcode (iOS) and Kotlin for Android Studio when you pick both platforms.
Store ship guides
APP_STORE_GUIDE.md (iOS — TestFlight and the App Store on your Apple account) and PLAY_STORE_GUIDE.md (Android — Google Play internal testing and release on your Google account). Signing, beta, and submission steps travel with the code.
Read the launch guide before you buy →How does this compare?
Three honest options for getting from a working web product to native iPhone and Android apps — and where each one fits.
| Mobile contractor | Capacitor / WebView | Rewrite | |
|---|---|---|---|
| Real native UI | ✓ | ✗ — your web app inside a frame | ✓ — Swift / SwiftUI + Kotlin / Compose |
| Time to first build | weeks → months | hours | ~24h scoped pass |
| Cost predictability | hourly bills · scope creep | low upfront · debt later | scoped band before build |
| Owns the source after | sometimes | yes | yes — yours |
| Best for | bespoke design · multi-quarter roadmaps | proof-of-concept · internal tools | shipping real native apps from a real web product, fast |
If your situation is “I want a 6-month mobile design partner,” it's probably not us. If it's “I have a working web product and want real apps on the App Store and Google Play this quarter,” it is.
What we don't do well yet
The product copy on this page is confident on purpose. Here's where it isn't — so you can decide before paying instead of after.
Heavy custom animation parity
Native iOS and Android have motion idioms that don't map 1:1 to web CSS animations. We pick the closest native equivalent; if your design depends on a custom shader or physics, we surface it as an inspection note rather than silently approximate.
Real-time collaborative UI (Docs-style)
The native layer ships URLSession + WebSocket plumbing. Full CRDT / OT collaboration logic isn't auto- generated — you wire that on top.
AR / camera / sensor-heavy experiences
We generate the permission scaffolds (camera, location, photos, etc.) and the right usage descriptions, but actual ARKit / ARCore scenes and computer-vision pipelines need hand-written native code.
Tablet / watch variants
We ship phone-first layouts from your web source of truth. iPad-specific layouts, Android tablet polish, and Apple Watch variants are on your team.
If your product depends on any of these, talk to us before paying — we'll either confirm it's in scope or honestly say it isn't.
What stays on your side
- → Apple and Google developer accounts, certificates, provisioning, App Store Connect or Google Play Console, TestFlight or Google Play internal testing, and store submission.
- → Privacy labels, compliance, and industry rules for your product (we are not your lawyers).
- → Ongoing polish after handoff — same as any shipped app team.