Product engineering

Platform apps look like small projects. They are not. The client is the easy part. The platform imposes rate limits, at-least-once webhook delivery, review processes with opinions, and API changes on someone else's schedule.

These are distributed-systems problems at a smaller scale and with tighter deadlines.

Meta platform apps

We build against the permission model and review process as they actually are. We design integrations so a policy change or API deprecation is a contained piece of work, not a rewrite.

Shopify apps and storefronts

We treat webhooks as at-least-once from the first line, because they are. Idempotent handlers mean a redelivery during a flash sale does not duplicate an order.

Android

Native apps, offline-first where the domain calls for it, with a sync model designed up front. We have years of work on device fleets where the network cannot be assumed.

The backend

Clients get replaced and platforms deprecate. The backend, data model and integration contracts persist, so we design them first.

Three ways this is usually bought.

6–16 weeks

Build

Design through to store submission or app listing. Includes the backend, the review process and the operational tail nobody scopes for.

3–8 weeks

Rescue

An app that works but cannot scale, cannot pass review or cannot be changed safely. We diagnose first and rebuild only where it is cheaper than repair.

2–6 weeks

Platform architecture

The system behind the app: data model, API, integrations and webhook handling. We design it before the client is written.