pinomy.

Today’s motion: “This app needs a login screen.”

Make your case

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.

Our usual ruling on app approach (illustrative)
SituationUsual recommendationWhy
Occasional use, discovered via searchMobile web pageNobody installs an app for a yearly task
Weekly use, accounts, remindersCross-platform appOne codebase, notifications, home-screen presence
Camera, Bluetooth or heavy offlineNative or hybridPlatform 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

Discuss a build