Problem, approach, outcome, and the architecture decisions with their tradeoffs. Filter stacks combine: pick two tags to see projects using both.
Delivery drivers work for hours with no connectivity, then sync. The hard problem is not the sync, it is what happens when the field and the office disagree.
A pharmacy management system that keeps selling when the internet drops, then reconciles every till operation exactly once when it returns.
Rent a scooter or e-bike from an app: scan the QR, the physical lock opens over cellular, ride, park in a permitted zone, pay by the minute from a prepaid wallet.
Two-sided marketplace for architecture and design work: the platform holds the money until delivery is confirmed, with bidding happening in real-time chat.
A complete restaurant operating system on one multi-tenant backend: customer ordering, driver dispatch, owner dashboard and point of sale.
Storefront, app and operations dashboard sitting in front of an external ERP, with data flowing both directions and staying consistent.
Find hotels, restaurants and attractions near you, ranked by real distance, across three separate venue types in one query.
GraphQL commerce backend where the client rearranges their own storefront from the dashboard, over an inventory ledger with a single mutation point.
One backend serving many client websites, each defining its own content types, its own team permissions and its own subscription.
Inherited a TypeScript and SQL codebase, migrated the stack, and came out with fewer models and more capability.
Conflict-free timetable generation across grades, sections, teachers and subjects, using a language model constrained by a hard specification and checked by real code.
A formal pollution-scoring instrument turned into an API: georeferenced water, air and land contamination cases scored against a defined criteria set.