membership-platform-flutter
Private GitHub repository
A 0→1 membership platform monorepo that pairs a Gourmet-branded Flutter member app with a NestJS modular-monolith backend, shared API contracts, and cross-platform design tokens.
Media
membership-platform-flutter
A 0→1 membership platform monorepo that pairs a Gourmet-branded Flutter member app with a NestJS modular-monolith backend, shared API contracts, and cross-platform design tokens.
Current project media uses four Flutter golden captures from the real member app: Home, Member Card, Wallet, and Profile.
Core member loop
The first shipped slice focuses on the member loop that has to work early in a real loyalty product, not on placeholder marketing screens.
The member app already connects OTP authentication, branded home entry, member-card token access, wallet summary, and profile maintenance in one consistent shell. That gives the project a usable baseline for future retail and CRM integration work.
The UI work is only one layer. The repo also keeps backend modules, contract definitions, and design tokens beside the Flutter code so later coupon, activity, and notification work can extend the same operating model instead of creating parallel prototypes.
- Flutter member app uses feature-first layered architecture.
- NestJS backend follows a modular-monolith structure for auth, member, wallet, coupon, and integration slices.
- OpenAPI and design tokens are versioned in-repo to reduce UI / API drift.
- Current media pack uses real Flutter golden captures from the app, not stitched marketing comps.
OTP-first member entry
Phone-based OTP flow is the first authentication slice, keeping onboarding light while preserving a real session boundary.
Operational membership token
The member card is treated as a working token surface with refresh and expiry behavior, not just a decorative QR placeholder.
Points visibility inside the app shell
Balance, pending value, and transaction history stay in one wallet view so members can understand state changes without leaving the app flow.
Monorepo-backed delivery baseline
Flutter app, NestJS backend, OpenAPI baseline, and design tokens stay in the same repo so product slices can ship with less contract drift.
Overview
A 0→1 membership platform monorepo that pairs a Gourmet-branded Flutter member app with a NestJS modular-monolith backend, shared API contracts, and cross-platform design tokens.
This project is built as a greenfield membership platform rather than a single demo screen set. The intent is to keep member experience, service contracts, and delivery structure aligned from the first slice.
The current shipped loop focuses on the member-facing surfaces that have to feel coherent early: OTP login, Gourmet-branded home, dynamic QR member card, wallet balance and history, and profile editing.
Under the UI, the repo already carries a NestJS modular monolith, OpenAPI baseline, design tokens, ADRs, and local runbooks so future coupon, activity, notification, and integration slices can grow on a stable backbone.
- The member app already ships OTP login and verification, a Gourmet home surface, a dynamic QR member card, wallet history, and editable profile flows.
- The backend baseline covers auth, member profile, member card token, wallet, coupon, and POS points-earn slices under one modular-monolith foundation.
- Keeping Flutter, NestJS, OpenAPI, and design tokens in one repo makes mobile UX, API contracts, and delivery slices evolve together instead of drifting apart.
Feedback
Feedback is not open for this project yet
This repository is not public yet. GitHub issue feedback will open after the release path and public cleanup are ready.