Three routes.
Three different budgets.
A web app runs in the browser; a PWA adds an installable experience on supported devices. A small, clearly scoped build can cost less than $500.
- No store listing required for browser delivery
- Databases, integrations, features, and ongoing services affect the quote
- Start with the job you need done; add capability as you grow
Keep the web-app core and add packaging for store submission. The web-app work still counts; testing, packaging, and store preparation add to that scope.
- Quoted for the features and platforms you need
- A store listing does not automatically require native development
- Store approval is not guaranteed by wrapping a website
If you know you need both the Apple App Store and Google Play, and we agree the product requires native development, budget at least $25,000 for the native work.
- This is the minimum native-build budget, not a fixed all-in project price
- Additional product scope, backend work, integrations, and ongoing support are priced separately
- We confirm the delivery route and scope with you before work begins
Native / both stores / minimum budgetThe store route is real. So is the bill.
Native for iOS and Android: $25,000 minimum for native work, with the full project scoped before quoting.
The store route is real. So is the bill.
Native for iOS and Android: $25,000 minimum for native work, with the full project scoped before quoting.
A native build is engineering for one specific device family. Signed builds, store review rounds, device testing, privacy declarations, update pipeline — the work that makes an icon on a home screen behave like it was always there.
The $25,000 floor is the minimum budget for native work covering both stores. It is not a blanket price for every feature. Backend work, integrations, additional product scope, and ongoing support are agreed and priced separately. What it doesn't cover is Apple's and Google's toll — store fees and the percentage they take of anything you sell through them. That bill comes from them, not us, but we'd be lying if we didn't mention it.
Straight talk: a store listing alone does not tell you whether an app is wrapped or native. We explain the route and scope before quoting.
The honest fork / web or nativeDo you actually need native?
Browser delivery, a store shell, or native device work — choose what the product needs.
Do you actually need native?
Browser delivery, a store shell, or native device work — choose what the product needs.
Start with what customers need to do. Can the job run in a browser? Is a store listing essential? Are there device, background, or performance requirements that call for native work? We assess those needs before choosing the route.
A store listing can mean wrapped or native; it does not automatically mean a $25,000 build. A small web app or PWA may be enough. When the agreed requirement is native delivery for both stores, $25,000 is the minimum native-build budget, with other project scope quoted separately.
Reality check: the 30% store toll, the review queue, and re-submitting every update is the price of being "an app." Some products need it. Most businesses don't.
The record / we actually ship theseTwelve years on the store isn't a pitch line.
Scan Quest 2012–2024 — plus Lehman, Bloomberg, Nomura, Wells Fargo mobility.
Twelve years on the store isn't a pitch line.
Scan Quest 2012–2024 — plus Lehman, Bloomberg, Nomura, Wells Fargo mobility.
Scan Quest launched on the App Store in 2012 and took updates until 2024 — twelve consecutive years live, through every iOS breaking change Apple shipped. Quiet Clubbing, Midnight Music, SilentSystem, Touchless Egg Hunt — real products, real store record, real people tapping them.
And it's not just our own IP. Tim's mobility career runs Lehman Brothers, Bloomberg, Nomura, and Wells Fargo — BlackBerry Enterprise, J2ME, Objective-C through Swift and Kotlin. When we quote a native build, it's a crew that's been shipping phone software since apps were new.
App Store Connect — the EAS portfolio, live listings
One folder on a real phone — four shipped EAS appsReceipts, not renders: every product named on this page existed in the store and ran on real devices — some still do.
Ready-built / ticketing & loyaltyWant ticketing or loyalty? We already built it.
QR, NFC, or barcode — every code single-use, no dup tickets, ever.
Want ticketing or loyalty? We already built it.
QR, NFC, or barcode — every code single-use, no dup tickets, ever.
If you need a ticketing or loyalty application, we don't start from zero — we have them built, and we make yours. Your name, your colors, your event or your counter — QR, NFC, or plain barcode, whatever your door staff and your customers actually have in their hands.
And the scam every venue knows dies here. Every code is single-use — you'll never see a duplicate ticket again. Nobody slips out the back, hands a ticket to a friend, and walks them in free. First scan admits, second scan flags. That door is locked.
On lock means on lock: a used code is a burned code. The only way in is a ticket the system has never seen.
Inside industries / the app that never sees a storeSome of our best builds
aren't in any store.
Inventory screens, phone-to-building apps, on-prem data — systems built for your building, not the App Store.
Some of our best builds
aren't in any store.
Inventory screens, phone-to-building apps, on-prem data — systems built for your building, not the App Store.
Some of the best applications we've built will never be listed anywhere. Inventory screens on the wall. Pick lists on the phone in the hand. A system that runs inside your building, on your own network, talking to the devices your crew already carries — Android or Apple, we write both and won't make you pick a side.
This is the same engineering as the store apps, pointed inward. The database can live on hardware in your back room and the app keeps working when the internet doesn't — local isn't a limitation, it's a feature. Software fitted to your floor plan and your process, not a SaaS template with your logo on it.
The fine print: the only store we don't write for is Windows Mobile — and we don't care to.
Same app / bigger glassThe app doesn't stop
at the phone.
The same app runs the menu board, the kitchen screen, the kiosk — the paper retires.
The app doesn't stop
at the phone.
The same app runs the menu board, the kitchen screen, the kiosk — the paper retires.
The same web app that installs on a phone runs the TV over the counter, the tablet at the table, and the board in the drive-thru lane. A browser is the player — no proprietary signage box, no per-screen license, no subscription to show your own menu. Which means the application doesn't just replace the paper menu. It replaces the printer, the ticket rail, the clipboard, and the yelling.
Price change, 86'd item, breakfast-to-lunch flip — update once and every board in the building changes before the customer finishes reading the old price. Seasonal menus swap on a schedule, not a reprint.
Paper becomes the option, not the load-bearing part. Keep the thermal printer for the one customer who asks — stop feeding it for the ninety-nine who don't.
Tickets land at the station that needs them — grill sees grill, fry sees fry. Expo bumps with a tap or a $6 clicker. No ribbons, no paper rail, no lost ticket, no "I never got that one."
Order-confirmation at the window, weather-rated boards in the lane, a presell board at the entrance. Breakfast flips to lunch on a timer — the ladder and the printed inserts retire.
The tablet is the register, the TV is the menu, and the location board tells the route where you parked. Sold out? One tap and the menu, the site, and the order page all say it at once.
A "now serving" screen calls the numbers — counter staff stop being an intercom. Works for the counter, the window, and the curbside spot.
Order another round, call the server, pay the check, keep the kids busy. A $150 Android in a locking mount does the job — no proprietary table hardware.
Any touchscreen running the same app — menu, mods, payment, ticket. The kiosk doesn't call in sick, doesn't mis-key the mod, and upsells every single time.
The glass is a commodity.
The app is the product.
Say the hardware numbers out loud: a menu board is a $90 TV and a $30 stick. A table tablet is a $150 Android in a locking mount. The sun-facing wall and the drive-thru lane get commercial 24/7 panels, because physics is real — but none of it is proprietary, and every screen swaps like a lightbulb. You buy the application once. Every screen it ever touches is just a browser with a different size of glass.
Say "app." We'll ask which kind.
Web app that installs from the browser. Wrapped build with a store listing. True native for both stores — a $25,000 minimum native-build budget, plus separately scoped product work. Whatever it is, it starts the same way: a case file telling us what it needs to do.
Tell us the job the application has to do. We'll tell you which of the three routes fits — and if the honest answer is "you don't need native," we'll say that too.
And you get an answer either way. We're a small shop on purpose — we turn down more cases than we take, and a fast honest no beats a slow maybe. But when a case is big and we're interested, we'd rather build the prototype than talk about it. That lane barely existed four years ago — it's a different market now.