Web and mobile apps that feel like one product.
One team builds the web app and the phone apps, so they share design, logic and release rhythm.
A web app and a phone app sharing one design, built by one focused team.
Overview
We build responsive web apps and iOS and Android apps from a shared design and a shared back end. Pages load fast, work with a keyboard and a screen reader, and cope with a poor connection. You get weekly releases to a test build on your own phone, not a promise of a launch.
A good fit if
- People use it on the move or every day, and need push, camera, location or offline use.
- The web app and the phone apps have to stay in step on one back end.
- An app store rejected you and the reason isn't clear.
- Separate vendors for web and mobile keep drifting apart.
Not the right start if
- People use it now and then, at a desk, or find it through search. A fast web app is enough, and cheaper.
- The app would only repeat your website. Apple rejects plain website wrappers. A web app may be the better answer.
- The idea hasn't been tested yet. Start with Discovery & MVP
Release
Every platform has its own gate
The same release reaches the web, iPhone and Android by different routes. Switch on a problem and see which route stops.
One build
-
Web
- Preview
- Production
- Speed check Held Responds to taps within 200 ms
-
iPhone
- TestFlight
- App Review
- Phased release Paused
-
Android
- Internal test
- Closed test Waiting
- Review
- Staged rollout Halted
- Stability check Crash rate under 1.09%
Live
Live on all three: the web on release, iPhone after review, Android through a staged rollout.
Live on all three: the web on release, iPhone after review, Android through a staged rollout. Android waits for a closed test with at least 12 testers for 14 days before it can go to production. We plan for it from the start. The Android rollout halts and the iPhone phased release pauses. Above a 1.09% crash rate, Google Play may show the app to fewer people. The web release is held: it fails Core Web Vitals until taps respond within 200 ms. Live on all three: the web on release, iPhone after review, Android through a staged rollout. Android waits for a closed test with at least 12 testers for 14 days before it can go to production. We plan for it from the start. The Android rollout halts and the iPhone phased release pauses. Above a 1.09% crash rate, Google Play may show the app to fewer people. The web release is held: it fails Core Web Vitals until taps respond within 200 ms.Every case
- All switches off
- Live on all three: the web on release, iPhone after review, Android through a staged rollout.
- New personal Google Play account
- Android waits for a closed test with at least 12 testers for 14 days before it can go to production. We plan for it from the start.
- Crash rate rises during rollout
- The Android rollout halts and the iPhone phased release pauses. Above a 1.09% crash rate, Google Play may show the app to fewer people.
- Taps respond slowly on the web
- The web release is held: it fails Core Web Vitals until taps respond within 200 ms.
Process
How it runs
You keep
- 01A journey map and a screen list per platform.
- 02The token set and component library, with accessibility notes.
- 03The API schema and an offline and sync policy.
- 04The pipelines and the update rules.
- 05The device matrix and its test log.
- 06The beta groups and a feedback log.
- 07Store-ready listings in accounts you own.
- 08A rollout plan and crash alerts.
-
01 of 08
Core journeys.
What people do on the web and on their phones, and which platform comes first.
You keep A journey map and a screen list per platform.
-
02 of 08
One design system.
Shared tokens and components that still respect iPhone and Android conventions.
You keep The token set and component library, with accessibility notes.
-
03 of 08
The API and offline plan.
One contract for every app, and a decision on what works without a signal.
You keep The API schema and an offline and sync policy.
-
04 of 08
Build pipelines.
Signed builds for each platform, and rules for what can update without a store release.
You keep The pipelines and the update rules.
-
05 of 08
Real devices.
A test matrix that includes a low-end Android phone, with screen readers and large text checked.
You keep The device matrix and its test log.
-
06 of 08
Beta.
TestFlight and a Google Play closed test with real users.
You keep The beta groups and a feedback log.
-
07 of 08
Store submission.
Listings, privacy labels, a demo account for reviewers and in-app account deletion.
You keep Store-ready listings in accounts you own.
-
08 of 08
Staged rollout.
A small share of users first, with rules for when to halt.
You keep A rollout plan and crash alerts.
Risks
Most rejections are avoidable
-
Rejected for being unfinished.
Crashes, placeholder screens and missing demo logins top Apple's list.
Prevented in step 7 -
Crashes after launch.
Past the store's thresholds, fewer people see the app.
Prevented in step 8 -
People don't come back.
Most installs are gone within a month without a reason to return.
Prevented in step 1
23%
Apple rejected 2,093,244 of the 9,100,620 app submissions it reviewed in 2025.
1.09%
Above this crash rate, Google Play says it may reduce your app's visibility.
Deliverables
What you keep
-
Responsive web app
Built to the accessibility standard your users and regulators expect.
-
iOS and Android app
Native feel, one codebase where it makes sense and native code where it doesn't.
-
Offline-ready features
The parts that must work on a train or a bad connection, designed in.
-
Shared API and back end
One source of truth behind both apps.
-
Analytics from day one
Events agreed up front, so you learn from the first user.
Done means
- The web app and both store apps are live, from one team on one back end.
- Builds meet the current store rules: Apple's required SDK and Google Play's required API level.
- Privacy labels, the data safety form and in-app account deletion are in place.
- The web app passes Core Web Vitals and WCAG 2.2 AA.
- Crash alerts fire before the stores' thresholds do.
- You own the store accounts, the signing keys and the repositories.
Sample
Store readiness check
| Built with the current iOS SDK | Done |
|---|---|
| Targets the current Android API level | Done |
| Privacy labels and data safety form | Done |
| Demo account for reviewers | Done |
| In-app account deletion | Done |
| Crash-free sessions in beta | 99.8% |
FAQ
Questions about Web & Mobile Apps
Still deciding?
Ask the people who would build it. We reply within one business day.
Cross-platform for most products, usually React Native with Expo, since one codebase costs less to build and keep in step. Native is worth it when the product is the device: heavy graphics, Bluetooth, background work or widgets.
Apple rejects plain website wrappers. A progressive web app is fine if you don't need the store, as long as iPhone users only get notifications after adding it to their home screen.
Apple reviews 90% of submissions within 48 hours. A new personal Google Play account must first run a closed test with at least 12 testers for 14 days, so we plan for it from the start.
Where you need it, yes. Offline support changes the architecture, so we decide which features need it during discovery, not after the build.
Yes. We prepare the listings, handle review feedback and release from accounts you own.
You do. Company accounts need a D-U-N-S number, which can take a few weeks to issue, so we start that early.
Contact
Have an idea or a stuck project? Let's talk.
We reply within one business day. If we're not the right team, we'll say so on the first call.
On the first call
- Who uses it, where, and how often.
- Which platforms come first.
- Any designs, store accounts or back end you already have.