Services
Mobile apps that behave well on a hectic shift.
We build iOS and Android apps for staff and visitors: sign-in, booking changes, rota swaps, room checks and internal checklists. Here is how we decide what to build and how we build it.
Choosing the right kind of app
One codebase for iPhone and Android. This is our usual starting point for staff tools, because it keeps cost and maintenance in proportion. We typically use Flutter or React Native and explain the trade-off for your case.
Suits: rota apps, checklists, internal directories, booking changes.
Separate apps written for each platform. Worth it when an app relies heavily on device features, such as dependable background behaviour or close integration with hardware readers.
Suits: kiosk-style sign-in with scanners, apps with demanding offline needs.
A website that can be added to the home screen. Often the most sensible choice for occasional users. No store review, quick updates, and it works on shared desktop computers too.
Suits: visitor forms, simple status pages, lightweight internal tools.
What a mobile build includes
- Flows sketched with the people who will use the app, before visual design.
- Offline behaviour decided on purpose: what still works without signal, and what waits.
- Accessible text sizes, contrast and screen reader labels, tested on real devices.
- Sign-in that suits shared devices where several staff use one tablet.
- Crash reporting and release notes set up before the first public version.
- A handover pack with source code, store accounts and a plain guide to updates.
Questions about mobile work
Who owns the app store accounts?
You do. We help you create Apple and Google developer accounts in your organisation's name and work inside them as invited team members.
Can staff use their own phones?
Yes, if your policies allow. We design sign-in and data storage with that in mind and keep sensitive information off the device where possible.
How do updates reach people?
Through the stores, or directly for installable web apps. We set up a simple release routine and explain each step.