Kaki, redesigned
One design system for the website, admin, owner portal, POS and app. Start with the design guide, then the complete mockups, then the plan that takes it into the monorepo.
Design guide
Tokens, Archivo type, tiles, buttons, lists, data, score tracker, POS, motion, voice and the component catalogue.
Open guide →Integration plan
Branching (one PR at the end), shared packages, parity rules, and the waves of parallel agents.
Read plan →Open questions
About 40 decisions the mockups surfaced (money, the Jadwal timeline, navigation, copy, the app), each with my recommendation.
Answer →DESIGN-SYSTEM.md
The new v2 design doc that replaces docs/DESIGN-SYSTEM.md.
Read →Complete mockups
Website
kakimahjong.com: every route in the approved player’s-view style, including booking end to end and /game.
Open →POS (operator)
The web POS on a tablet: floor, bill and payment, the new Jadwal timeline, check-in, tabs, open play and more.
Open →Owner portal
The venue owner’s dashboard, locations, pricing, coaches, finance, reports and settings.
Open →Admin
Every admin route: overview, venues, bookings, money, users, moderation, staff and audit.
Open →App
Every screen of the consumer app: tabs, booking and QRIS, Cari Kaki, events, tournaments, clubs, chat, the score tracker, and account. The direction isn’t final yet.
Open →Score tracker flow 1
Today’s tracker flow in the new design (Riichi, Chombo, Catat menang, Seri, End game), clickable, to compare with Flow 2.
Play it →Score tracker flow 2
A clickable prototype of the new buttons (New hand, Delete last hand, End game, Cancel game) and the reordered New hand flow, with real Riichi points.
Play it →App onboarding
A clickable proposal for the first-run flow: value first, guest browsing, sign-in only when needed, and every question asked in context. Includes old vs new mapping and open questions.
Play it →Earlier explorations
The first rounds: the app ideas, Cari Kaki options, the three website directions and the colour comparison.
Open →Parity checklists
Website
Every route, action, state and API call.
Open →POS
Web POS vs native POS, plus the new Jadwal timeline.
Open →Owner
Locations, pricing, finance and operators.
Open →Admin
Every admin action and its guard rails.
Open →App
The consumer app’s full inventory, for the later app redesign.
Open →Architecture
How the token and component packages plug into Next and Expo.
Open →Locked decisions
redesign/v2. One PR to main when it has been tested.