Marketplaces & two-sided apps
Buyer and seller apps, listings, search and filtering, in-app messaging, ratings, dispute flows and split payouts.
The part that bites
Keeping two audiences in one codebase without either experience feeling secondary.
Work
We would rather show you the thinking than a wall of logos.
Client apps ship under NDA and our published case-study library is still being written. So here is something more useful than screenshots: what we build, the hard parts we have had to solve, and the standard every case study we publish will meet.
What we build
Six product categories we know the sharp edges of.
Each of these has a specific thing that goes wrong in production. Knowing which one is most of the value we bring.
Fintech & wallets
KYC onboarding, card and bank linking, transaction ledgers, statements, limits and biometric re-authentication.
The part that bites
A ledger that stays correct when the network dies mid-transfer.
On-demand & logistics
Live order tracking, driver and dispatcher apps, route display, background location, and push that actually arrives.
The part that bites
Battery-sane background location that survives aggressive Android OEM process killing.
Social & community
Feeds, profiles, follows, media upload, comments, moderation tooling and notification preferences.
The part that bites
Feed performance and media caching on a three-year-old mid-range phone.
Health, fitness & habit
HealthKit and Health Connect integration, wearable data, streaks, reminders and privacy-first data handling.
The part that bites
Health data rules differ per platform and per jurisdiction, and both stores check.
B2B & internal tools
Field data capture, offline-first forms, barcode and document scanning, role-based access and SSO.
The part that bites
Offline-first sync with conflict resolution users can understand.
Our standard
What a Cognify case study will contain.
Most agency case studies are a screenshot and an adjective. When ours go up — as client NDAs allow it — they will carry the things that would actually help you judge us.
Want references instead? Ask, and we will arrange a call with a client at a similar stage to you. That is worth more than a page we wrote about ourselves.
- 01The actual brief, including what we argued against
- 02Scope decisions: what made v1 and what was deliberately cut
- 03Architecture and why that stack, with the trade-offs stated
- 04The hardest technical problem and how it was solved
- 05Store review history — including any rejections and why
- 06Measured outcomes after launch, not projections
Publishing rejections and cut features is unusual. It is also the only version of a case study that tells you anything about how a studio behaves when a project gets difficult.
Founding clients
Early on a case-study library, deliberate about who fills it.
We are taking on a small number of projects we can publish in full — scope, architecture, review history, results. In exchange you get senior attention on a short queue and a studio with a direct stake in your launch going well enough to write about.
Start here
Your app could be the first one here.
Tell us what you are building. If it is a fit we will move fast; if it is not, we will say so and point you somewhere better.
NDA on request · Reply within one business day