Development
Mobile development
iOS and Android apps on Flutter or React Native — plus the server side behind them: sign-up, tokens, profiles, notifications, Firebase.
- Reply to your brief
- within 24 hours
- First call
- 30 minutes, no commitment
- First working version
- in 5–6 weeks
Process
What happens, and when
The work is split into stages, and each one has a named result. You see it yourself rather than reading about it in a report.
Days 1–7
Requirements and devices
We work out what the app has to run on: the minimum iOS and Android versions, what it does with no connection, what has to arrive as a notification. The list of phones it gets tested on is drawn up here too — it sets how much testing there is, which is why it is agreed before the work starts rather than at the end.
You get — Minimum OS versions and the test phone list
Week 2
Navigation and data
We lay out navigation and the data behind it for a phone: what lives on the device and opens offline, what is fetched on demand, how a screen behaves on a slow connection. Notifications are settled here as well — that single choice pulls the server side along with it, and the permissions the app has to ask for.
You get — A screen map with offline and notification rules
Weeks 3–5
Builds on your phone
Every week you get a build and install it on your own phone — not a video, not screenshots. The code is shared, but both platforms get checked: the differences live in small things — keyboards, the back gesture, permissions, what happens when a call comes in over the app.
You get — A weekly build checked on both platforms
Before the release
The release build
We put together the release build with live keys — server, Firebase, payments — and walk the app through on a slow network and on the oldest phone from the list. The launch date gets planned with room to spare: a submitted build joins a review queue at Apple and Google, and neither side decides how long that queue is.
You get — A live-keys build submitted to the stores
After the release
Support for older versions
Mobile updates are not instant: some people stay for months on the version already installed. So the server keeps understanding older clients, and the app reports its own crashes — otherwise you hear about a breakage from a one-star review.
You get — Crash reports and support for older clients
What the work covers
One codebase for iOS and Android
shared code, a separate build per platform, and a change lands in both versions at once
The database behind it
tables, relations and indexes chosen for the queries a mobile client makes
User accounts
sign-up, sign-in, tokens, roles and permissions
The server behind the app
a REST and WebSocket API for the mobile client, user profiles, server-side scenarios
Notifications and payments
notification sending on the server side, Firebase, a payment provider connected
Response times
caching for frequent requests, heavy work moved off the request, faster reads from the database
What we need from you
- Apps close to what you have in mind, with a note on what works for your case and what doesn’t
- What the app has to do: the screens, what a person does on them, and what the server does in response
- Access to the services the app depends on: your server, Firebase, the payment provider
What people usually ask
Contact
Send a description of the task
A reply with the scope, the timeline and a budget estimate comes within 24 hours.
The first call is 30 minutes, with no commitment on your side.
01
You describe the task
Five questions in the form, or a plain email — whichever suits you.
02
We answer within a day
With the scope, the timeline and a budget estimate, based on what you told us.
03
We talk for 30 minutes
To clear up whatever is unclear. It commits you to nothing.