Apps & web
Built to hold up under questioning.
We choose technology the way we choose features: by stating the case for it, the case against it and what would make us change our minds.
A
Mobile apps
Most of our mobile work uses a cross-platform framework such as Flutter or React Native, because one codebase is easier for a small organisation to maintain. We switch to native Swift or Kotlin when the case is strong: heavy use of device sensors, demanding animation, or platform features that cross-platform tools reach late.
Every app we build handles poor connections deliberately. We decide, feature by feature, what works offline, what queues until signal returns and what tells the user plainly that it cannot proceed. Notifications are opt-in and specific. Text respects the system font size. Screen readers get real labels.
| Situation | Usual recommendation | Why |
|---|---|---|
| Occasional use, discovered via search | Mobile web page | Nobody installs an app for a yearly task |
| Weekly use, accounts, reminders | Cross-platform app | One codebase, notifications, home-screen presence |
| Camera, Bluetooth or heavy offline | Native or hybrid | Platform features arrive first natively |
B
Websites and web applications
For organisation websites we prefer static or lightly server-rendered pages: they load quickly, cost little to host and have fewer moving parts to break. Content management is added when someone will actually update the site weekly, not because every site is expected to have one.
For web applications such as portals, booking tools, dashboards and internal systems, we build with mainstream, well-documented frameworks and a relational database. Roles and permissions are designed on paper first. Exports, audit trails and data retention are agreed before launch, not discovered after it.
What you receive at handover
- The repository, in your organisation’s account, with a readme a new developer can follow.
- A decisions log recording what was chosen, what was rejected and why.
- Environment notes: hosting, domains, keys you control and where backups live.
- An accessibility statement with known issues listed honestly.
- A support option, never an obligation.