Skip to content
06Selected work

Systems built for the real world.

Four platforms, four different sets of constraints — and the engineering decisions each one turned on.

  1. 01Consumer AI

    Mindora

    AI journaling and wellness companion

    Web · React Native

    JAVA 21SPRING BOOT 3REACT 19REACT NATIVEPYTHONELASTICSEARCHRABBITMQKUBERNETES

    AI & Intelligent Systems
    Challenge
    Journaling apps capture what you write and tell you nothing about it. Understanding how your mood moved across months of entries meant reading every one of them back.
    Approach
    A product where the writing surface and the analysis are one system. Entries are scored for mood as they are written, indexed for retrieval, and returned as trends — a mood radar, positivity over time, a month at a glance — beside an assistant that answers questions about your own entries and helps rewrite, summarise and tag them. The mobile client is React Native at feature parity with the web app.
    Engineering
    Twelve deployable services — eleven Java, one Python Flask — behind a Spring Cloud Gateway with Eureka discovery and Redis-backed distributed rate limiting. The journal service publishes to an exchange the search service consumes, so Elasticsearch indexing never sits on the write path. Entries are stored as ciphertext under AES-GCM, and the AI layer falls through Gemini to Anthropic to HuggingFace and finally to deterministic heuristics, so a provider outage degrades the feature instead of breaking it.
  2. 02Retail & commerce

    Aqvion POS

    Retail operations as an installable desktop application

    Windows desktop · Multi-terminal

    JAVA 21SPRING BOOT 3POSTGRESQLNEXT.JSELECTRONNSIS

    Software Engineering
    Challenge
    Small and mid-size retailers run sales, stock, suppliers, payables and online orders across separate systems or on paper. Cloud POS is worse, not better, when the shop's connection is unreliable and the till still has to take money.
    Approach
    One platform covering point of sale, inventory with batch and expiry tracking, customers and store credit, suppliers and purchasing, accounts payable, cash-register sessions, quotations, promotions, budgets and financial reporting — shipped as a single Windows installer rather than a hosted service.
    Engineering
    Electron bundles the entire stack: the Next.js front end, the Spring Boot backend, a JRE, Node and PostgreSQL, assembled by electron-builder into one NSIS installer. The main process supervises those children with wait-on readiness checks, a single-instance lock and graceful shutdown. Inventory is a ledger — current stock is a read model over an auditable movement history — and receipts print to 58mm and 80mm thermal hardware.
  3. 03Education

    School Management System

    Offline-first school administration

    Windows desktop

    ELECTRONREACTTYPESCRIPTSQLITEPRISMA

    Software Engineering
    Challenge
    Schools on unreliable connections still need admissions, fees, exams, results and attendance to work every day. A cloud product stops being a product the moment the line drops.
    Approach
    A Windows application where every core function runs against a local database with no server and no internet: admissions and student records, fee structures, slips, exam fees, fines and discounts, marks and result cards, attendance, behaviour records, certificates, and reporting — under role-based access.
    Engineering
    Electron and React over SQLite through Prisma, packaged as a single Windows installer. Report cards, fee slips and certificates are generated locally as PDFs, with Excel import and export for bulk data and built-in database backup and restore. WhatsApp messaging is isolated as an optional integration so the core never depends on it.
  4. 04Brand & digital product

    AQVION LABS

    This site — a design system, not a template

    Web

    NEXT.JS 16TYPESCRIPTTAILWIND V4CANVASFRAMER MOTION

    Digital Products
    Challenge
    A technology company's own site is the first proof of how it builds. A template would have said the opposite of everything the copy claims.
    Approach
    A design system before a page: colour sampled directly from the brand mark so interface and logo share one colour space, a fluid type scale, one easing family, and layout primitives everything else composes from. The hero's Intelligence Field is a canvas systems diagram — data paths converging on the emblem — rather than a stock particle effect.
    Engineering
    The field runs at roughly 0.2ms a frame: static structure is painted once to its own canvas, and only the pulse trails are redrawn, into dirty rectangles rather than a full clear. Everything animated is transform or opacity. The hero copy is server-rendered at full opacity and the entrance is opt-in behind an attribute set before first paint, so no content ever waits on JavaScript to become visible.