MBG Dashboard

The brief.

The stack.

What it does.

• Menu planning calendar

  Functional weekly view with prev/next/today and ISO 8601 week numbers. Click an empty day to create a daily menu pre-filled with the date, click a filled menu to edit. Color-per-recipe via deterministic hash so the same recipe always reads as the same color across the week.

• Recipe builder + recipe scaler

  Full-page editor, not a modal — the complexity earns it. TKPI ingredient picker, auto-calculated nutrition + cost + AKG percentage in real time, sticky preview of totals against the target age group. Recipe scaler modal in the quick-tools drawer recalculates the BOM to any target portion count and re-quotes the cost.

• Inventory FEFO + bulk operations

  First-expired-first-out picking with per-batch tracking, expiry warnings, and stock movement history. Multi-select with a floating bulk action bar for stock writes — receive, adjust, discard a dozen lines without leaving the table.

• Production batch with HACCP gates

  Cook-core temperature gate at ≥75°C (HACCP CCP-3), holding-time state machine that walks safe → warning at 1h-remaining → critical at 30min → expired (blocks distribution). Photo-bukti required at batch complete and distribution checkpoints.

• Sixty-second traceability + sample bank

  Bank Sampel held ≥24 hours per Juknis 2026 with countdown chips per sample. Full incident traceability — supplier → ingredient batch → production → distribution → eight schools — required to resolve in under 60 seconds. Picker mode opens directly from any incident or batch.

• Compliance dashboard + Tren Operasional analytics

  Ten compliance rules compute in real time as the day's data lands — UMKM ratio, cashless ratio, hot-box temperature, AKG, protein variety, incident SLA. Tren Operasional view layers four longitudinal SVG charts on top: cost-per-portion weekly, daily production volume, on-time delivery, top expense category.

• Photo evidence pipeline

  Compliance demands a photo at every checkpoint — ingredient receipt QC, batch complete, distribution handoff, sample bank, daily QC. On desktop, photos live on the device filesystem rather than in the database, so the data store stays light and the gallery stays scrollable even after a few thousand captures.

• Audit-ready outputs + offline reports

  PDF Laporan Insiden BGN with severity badge, RCA, corrective/preventive actions, signature block. Daily, weekly, monthly PDF reports plus Excel multi-sheet workbooks. Everything generates on the kitchen's own device — no server round trip, fully offline.

• Tauri desktop polish

  Signed auto-updater with a persistent banner and a manual check in Settings. Daily backup writes a rotating snapshot of the full dataset to local app storage, so a corrupted day never costs more than the day. Global command palette for navigation, dark mode, and a five-step onboarding tour on first launch.

• License activation + read-only enforcement

  Ed25519-signed license tokens activate the binary locally — no internet phone-home, no telemetry, no cloud check. Fourteen-day trial, then the app drops to read-only mode without nag screens, deleted data, or surprise lockouts. Read-only enforcement guards write paths at four layers so the constraint holds even if a fork compiles from source and tries to route around it.

Architecture decisions.

• One product, two install paths

  Same app installs as a desktop binary (Windows, macOS, Linux) or runs as a web app — install once, work either way, no separate codebases to maintain. A kitchen with a shared Windows laptop runs the desktop binary; a supervisor checking from a tablet uses the PWA. The data and the workflow stay identical.

• Compliance baked into the workflow

  All ten Juknis MBG 2026 thresholds — sample hold hours, holding-time max, cook-core temp, UMKM ratio, cashless ratio, hot-box temp on arrival, AKG, protein variety, incident reporting SLA, traceability time — live as a single source of truth. The compliance dashboard reads them; every mandate UI computes against the same numbers. They never relax without a documented review.

• Offline-first because the deployment demands it

  SPPG kitchens run on flaky internet and shared commodity laptops. The database lives on the device — SQLite on desktop, IndexedDB on web. There is no remote authority to reconcile with. Reports export locally. The architecture matches the deployment reality instead of fighting it.

• Bahasa Indonesia as a first-class language, not a localization layer

  Native domain naming end to end — Kepala SPPG, Bank Sampel, Bahan Baku — not Manager, Sample Bank, Raw Material. Indonesian number formatting (Rp 14.000 with titik thousand separator, 1,5 kg with decimal koma), Indonesian date formatting (7 Mei 2026), and a professional asisten voice (Hapus resep ini permanen? not Apakah Anda yakin?). No emoji decoration, no cheerleader copy.

• Compliance is design surface, not a checkbox

  Every threshold has a UI consequence. Holding-time chips change color and block the distribute button at expired. UMKM ratio gates a chart segment. Sample-bank countdown lives next to every sample. The ten rules are the KPIs the operator looks at all day, not settings buried three menus deep.

• Hybrid distribution: MIT source, commercial binary

  Two paths to the same product. Source code is MIT — any SPPG (or developer at one) can fork the repo, compile, and self-host for free. The signed binary Caesar ships is commercially licensed (annual or lifetime tier), runs a fourteen-day trial then drops to read-only mode. The two models reinforce each other: the technical path is fork-and-compile, the convenience path is download-and-pay, and either way the kitchen owns its data on the kitchen's own device. No SaaS subscription, no per-seat fee, no cloud dependency.

What I'm learning.

• Single user is a feature, not a limitation

  v1.0 assumes one user — the Kepala SPPG. No roles, no permissions, no multi-tenant complexity. That assumption shed an entire dimension of work (auth flows, tenant isolation, audit of the audit) and moved the ship date months earlier.

• Tauri wins on disk and trust

  Tauri uses the platform's native webview — no bundled Chromium, no Electron tax. MBG Dashboard's signed Windows installer comes in at 6.77 MB. SPPG laptops are commodity Windows machines with limited disk; a small, auditable binary is the right shape for a tool that has to run on whatever's already there.

• Late-stage polish is its own design phase

  A late-stage UI audit caught twenty-six concrete usability gaps — chart labels overlapping at narrow widths, table action columns collapsing on tablets, progress bars overflowing on edge data. A spec gets you to feature-complete. Polish is what gets you to launchable.

• Auto-updater changes the velocity model

  A signed auto-updater means desktop fixes ship at web speed — push to the release feed, every kitchen running yesterday's build picks it up tonight. Once that loop is in place, the size of a release stops driving the schedule. Smaller, more frequent ships start to feel safer than big batched ones.