16
Map web application · prototype
WowPass Map
A map-oriented monorepo separating API, web frontend and data-sync worker.
Prototype source inspected · deployment unverified
- Period
- 2026
- Role
- Web application developer
PROJECT / DECISION RECORD
From the problem to the implementation
- 01Problem
Tightly coupling map data ingestion, API and UI increases the cost of change.
- 02Design decision
Separate API, web, worker and shared/database packages within a monorepo.
- 03Implementation
NestJS API, Next.js frontend, worker, Prisma schema and shared packages.
Problem
16Tightly coupling map data ingestion, API and UI increases the cost of change.
Constraints
- Public deployment, user metrics and data freshness were not verified.
- A prototype repository is not proof of a launched product.
- Data ingestion, API contracts and UI evolve on different schedules.
Engineering decisions
- Separate API, web, worker and shared/database packages within a monorepo.
- Separate API, web and synchronization worker into dedicated apps.
- Maintain Prisma schema and shared types in packages rather than copying them per app.
Implementation
- NestJS API, Next.js frontend, worker, Prisma schema and shared packages.
- The repository contains NestJS API, Next.js web and dedicated worker directories.
- Live data freshness, deployment and user adoption are not verified by this source review.
Verification / evidence
Source evidenceObserved
The repository README identifies API, web, worker, database and shared packages.
Result / current state
Source exists, without a claim of a launched service.
Current statusPrototype source inspected · deployment unverified