Case Studies

The constraint, the call we made, and what shipped

These are written by sector rather than by client name. Most of what we build ships under a client's own developer account, so we treat every engagement the same way: the engineering is described in full, the client isn't named, and every claim is tagged with how you can check it.

5.0★ across 5 verified Clutch reviews 100% Job Success over 49 Upwork jobs 10+ apps live on the App Store & Google Play A Flutter SDK published on pub.dev
Abstract illustration of a point-of-sale dashboard layout A stylised phone outline with blocked-out shapes standing in for a summary card, a bar chart and two stat tiles. An abstract illustration in brand colours, not a screenshot — no real interface or client branding is shown.
POS / Retail

Three roles, one app, and a Saturday with no internet

For a multi-location salon group — owner, supervisor and cashier see three genuinely different products, enforced in the data layer rather than the interface.

iOS + Android End-to-end build Verified proof
Abstract illustration of an encrypted records layout A stylised phone outline with a locked summary panel above a list of blocked-out record rows. An abstract illustration in brand colours, not a screenshot — no real interface or client branding is shown.
Fintech

Taking over someone else’s React Native app, and encrypting what it held

For a small-business finance startup — we inherited the stack instead of billing for a rewrite, then moved the records behind the Android Keystore.

Android Codebase takeover Verified proof
No case studies in that sector yet. Ask us about it — there is almost certainly relevant work we haven’t written up.

Want the version with the names in it?

We’ll walk you through the closest match to your project on a call, screens and all, under NDA. That conversation is a lot more useful than a page anyway.

Talk to us Book a free call

More: our work · the engineering blog · what clients say