On the Idea Wall · ▲ 0 votes
UrbanCore — the spec
UrbanCore is a browser-based city-planning game for everyday players who want to design small towns, manage budgets, and compete on how livable and efficient their layouts are. Players place zones, watch real-time metrics respond, and race up a weekly leaderboard — no engineering background required, no downloads needed.
---
Decisions locked
| Question | Answer |
|---|---|
| Shape | Online game (browser-based) |
| Audience | Everyday consumers |
| Core loop | Build residential blocks → get instant metric feedback → compare efficiency rankings weekly |
| Must-win metric | 10 weekly active players by day 30 |
---
The core loop
- Player starts a new town on a blank grid with a fixed starting budget.
- Player places zones (residential, commercial, roads) and immediately sees happiness and traffic-flow scores update on the canvas.
- Player manages remaining budget and resources, making trade-off decisions in real time.
- Player saves a weekly snapshot when satisfied with the town's state.
- Leaderboard updates each week; player sees how their efficiency score ranks against all other towns.
- Player reviews the weekly comparison tool, studies higher-ranked towns' layouts, and returns to iterate.
---
v1 scope
Zoning placement with instant metric feedback
A drag-to-place grid interface where each zone type (residential, commercial, road) updates efficiency, happiness, and traffic scores the moment it lands. Lives on the main Town Canvas screen.
Leaderboard ranked by efficiency score
A ranked list of all players' towns sorted by a composite efficiency score (density, traffic flow, happiness). Refreshes each week and lives on the Leaderboard screen.
Weekly town snapshot comparison tool
At the close of each weekly cycle, the system freezes a timestamped snapshot of every player's town. Players can view a side-by-side comparison of their layout against top-ranked towns. Lives on the Compare screen.
Budget constraints and resource management
Every town starts with a fixed cash budget and resource caps. Each zone placed has a cost; road connections carry maintenance overhead. A persistent budget bar on the Town Canvas enforces real trade-offs and prevents unconstrained sprawl.
Real-time happiness and traffic-flow visualization
An overlay toggle on the Town Canvas colors zones by happiness level (resident satisfaction derived from proximity to services and green space) and animates traffic density along roads. Updates continuously as zones are placed or removed.
---
Deliberately later
- Buildable structure library with unlock progression — unlock mechanics add retention depth, but they require a content library that would bloat v1 scope before the core loop is validated.
- Multiplayer town visits and rating system — social layers belong after the weekly leaderboard proves players are returning on its own; building social before retention is confirmed risks engineering the wrong thing.
- Preset challenge scenarios — scenario design is a content production workstream; once the sandbox loop is stable, scenarios become a natural expansion that reuses all existing systems.
---
Data model sketch
users— user_id, email, phone, created_at, notification_preferencetowns— town_id, user_id, name, grid_state (JSON), budget_remaining, created_at, updated_atzones— zone_id, town_id, type (residential/commercial/road), grid_x, grid_y, cost, placed_atmetrics— metric_id, town_id, efficiency_score, happiness_score, traffic_score, calculated_atsnapshots— snapshot_id, town_id, week_number, year, grid_state (JSON), efficiency_score, captured_atleaderboard_entries— entry_id, snapshot_id, user_id, rank, week_number, yearnotifications— notification_id, user_id, channel (email/SMS), event_type, sent_at
---
Screens
- Town Canvas — primary build screen; grid, zone palette, budget bar, real-time metric panel, and overlay toggles for happiness and traffic.
- Leaderboard — ranked list of this week's towns with efficiency scores, player names, and a link to each snapshot.
- Compare — side-by-side weekly snapshot viewer; select any two towns to overlay their layouts and scores.
- Town Dashboard — summary of the player's current town: score history, weekly rank trend, budget breakdown.
- Account / Settings — email or SMS notification preferences, display name, password management.
- Onboarding / New Town — minimal flow to name a town, confirm starting budget, and land on the Canvas.
---
How to use this document
- Bring it into Mind Palace, where the guided platform and its AI coach pick up from exactly this document and build the product with you step by step.
- Hand it to a developer as the complete v1 brief — scope, data model, and screen list are all here.
- Keep it as the single source of truth during your build; every feature decision should trace back to something on this page.
This is Ezekiel's. Build yours.
A spec like this is step 3 of Mind Palace's nine — the other six take a weekend: working software, a real offer, first customers.
Want to build this with Ezekiel?
Tell us who you are and we'll broker the introduction — their contact details stay private until they say yes.