Mobile and web applications

We build server-rendered applications that are fast on first paint, properly indexable and usable on a slow connection. Server rendering is not an aesthetic choice: on a merchant site, every tenth of a second of waiting is paid for in lost orders.

The architecture stays deliberately readable. A relational database, an explicit schema, versioned migrations. We avoid assemblies of services that make diagnosis impossible the day something breaks.

• Server rendering with measured time to first paint
• Explicit relational schema and versioned migrations
• Real internationalisation, localised addresses included
• Accessibility verified by keyboard and by contrast

Depending on the use case, an application installable from the browser is enough and avoids store distribution constraints. When hardware access, notifications or a presence in an application store is needed, we produce a cross-platform native application from a single codebase.

We settle that choice at the start of the project, with the costs of publishing, updating and compliance laid on the table. It is the decision that weighs most heavily on the following three years of budget.

• Documented trade-off between installable and native applications
• One codebase for both platforms
• Publishing, signing and update cycle handled
• Graceful behaviour without a connection

A badly designed internal tool costs more than a badly designed public platform, because its cost is paid in human hours every single day. We give back offices the same care as customer-facing interfaces: fast search, bulk actions, exports, change history.

The programming interfaces we deliver are versioned, documented and authenticated with revocable tokens. An interface without a version is a debt taken out in the name of whoever will consume it.

• Back offices designed for intensive daily use
• Change history and traceable actions
• Versioned, documented and authenticated interfaces
• Spreadsheet exports for offline work