I built connected workflows for players, staff, attendance devices, fee records, and venue bookings across FastAPI, Next.js, and Flutter.
ROLE
Solo full-stack & mobile developer
2026 · Ongoing product
PRODUCT CONTEXT
The product serves academy staff, members, and venue bookers through distinct app surfaces, backed by shared organization and subscription services.
Engineering contributions
Staff and members belong to organizations; a venue booker may not. The API scopes organization data by tenant and booking data by the booking a user can access.
ZKTeco ADMS/PUSH events enter the backend through registered devices. Device serial numbers resolve tenancy, while attendance and access services connect those events to member records.
Venue availability combines hourly pricing, closures, and active booking slots. A database uniqueness constraint on ground, date, and hour resolves competing booking requests.
The product records fees and other transactions collected outside the app, then issues branded invoices and updates membership/reporting state. It does not process those payments.
Subscription tiers, expiry behavior, feature modules, notifications, and a super-admin console support running the service. Flutter now also has a browser release and desktop layout adaptations.
Mobile clients and release tooling are implemented. Store review preparation is described separately from public app-store approval.