QUMI Docs
Development Journey

Development Milestones

Foundation

Initial QR/resource booking, tenant identity and owner/staff/customer operating surfaces.

Contract and workflow expansion

Broader API/controller coverage, RBAC, orders, customer flows, analytics, documents, payments and workflow checks.

Architecture realignment

Backend domains and frontend routes were reorganized to improve ownership and maintainability.

Pilot and release hardening

Pilot parity, blockers, auth/runtime evidence, release gates, recovery and localization became first-class engineering programmes.

Resource-native and vertical maturity

Generic resource authority, template/vertical governance and storefront capability contracts replaced workspace-only assumptions.

Staff/business-module maturity

OpsHub, booking/check-in, payments, CRM, HR, Finance, invoice, analytics and communications deepened.

Product-wide UX/i18n

Engineering moved from local page fixes to full-surface census and acceptance.

Planned next milestone

Make the already multi-vertical storefront visibly distinct by vertical, strengthen tenant identity/branding and improve onboarding/concierge experiences.