The problem
You are probably here because
A guest app for a hotel, a parent app for a school, a job app for a field team. One codebase, both app stores, and a web version where that makes more sense than an install.
- Your staff work off their phones and are still filling in paper.
- Customers keep asking whether you have an app.
- You need to reach people with a notification, not an email nobody opens.
- The work happens in a basement, a field or a lift, where the signal drops.
Included
What you get
Written down before anything is built, so you can price the conversation and hold us to it.
- One codebase, two stores
- iOS and Android built together, so a change ships to both. Roughly half the cost of building each separately.
- Works when the signal does not
- Field teams lose connection constantly. The app keeps working, queues what it could not send, and syncs when the bars come back.
- Push notifications people do not mute
- Set up properly, with the permission prompt asked at the right moment and controls so users pick what they hear about.
- Store submission, handled
- App Store and Play Store review is a process with its own rules. We write the listings, prepare the screenshots, handle the rejections, and get it published.
- An honest look at whether you need one
- A mobile web app costs less, needs no install and no store review. If that fits your case better, we will say so before you spend the money.
Process
How a project runs
In this order, with something you can look at early rather than a reveal at the end.
- 01
Decide app or web, honestly
Notifications, camera, offline and daily use point to an app. Occasional use by strangers points to the web. We work this out with you first.
- 02
Screens on paper before code
You see and change the flow while it is cheap to change.
- 03
On your own phone, early
A test build in your hand within weeks, updated as we go, so feedback comes from using it rather than looking at it.
- 04
Store submission and launch
We take the app through review, publish it, and stay on for the first update cycle when the real-world reports come in.
Tools
What we build with
- React Native
- Expo
- TypeScript
Ordinary, well-documented tools that other developers already know. Nothing proprietary that only we can maintain.
Industries
Where this comes up
The same problem looks different depending on the trade. These pages go into what it looks like in yours.
- HotelsBookings, front desk, guest messaging and housekeeping.Mobile Apps for hotels
- SchoolsAdmissions, attendance, parent portals and fees.Mobile Apps for schools
- EngineeringQuotes, job tracking, site reports and scheduling.Mobile Apps for engineering
- RestaurantsReservations, orders, phone lines and reporting.Mobile Apps for restaurants
Questions people ask
Do we really need an app?
Often not. If people use it occasionally and you need them to reach it without installing anything, a mobile website is cheaper and better. Apps win on daily use, notifications, camera and offline work.
How long does app store approval take?
Usually a few days once the app is ready, sometimes longer if the reviewer asks for changes. We build to the review guidelines from the start, which is what avoids most rejections.
Who owns the developer accounts?
You do, in your company name. We work inside your accounts. An agency that owns your App Store listing owns your app.
What about ongoing maintenance?
Apps need a release a few times a year just to keep up with iOS and Android changes. We plan for it rather than pretending it is free.