Crown Harbor - city builder game

The description states that Crown Harbor is a "browser-based isometric city builder focused on production chains, roads and physical resource delivery." It is described as a settlement-building game where players gather resources, construct buildings, manage workers, organize transport routes, expand production chains, and uncover the surrounding map.

It includes features such as forests, stone deposits, mountains, rivers, ports, warehouses, local storage, settlement goals, weather events, and scouting expeditions launched from the Settlement Center. The game uses isometric rendering, procedural map generation, and deterministic simulation elements.

The author notes it was built using Astro, JavaScript, HTML Canvas, and CSS, with modules for terrain, buildings, economy, logistics, exploration, rendering, UI, and save management.

Evidence Self-reported by the author; no independent verification.

The description states that Crown Harbor is inspired by classic isometric city-building games with beautiful artwork and a strong focus on settlement development. It emphasizes planning, resource management, production chains, exploration, and thoughtful expansion. Combat is not the main priority — the focus is on designing a thriving settlement and gradually turning it into a prosperous coastal town.

The author also mentions that they are proud of creating a complete playable settlement-building loop with multiple scenarios and a Creative mode, including seventeen building types, warehouse upgrades, finite natural resources, roads, bridges, physical deliveries, production chains, local storage, weather events, and scouting expeditions.

Evidence Self-reported claims about inspiration, focus, features, and accomplishments; no evidence of market positioning or competitive differentiation beyond self-description.

The description does not explicitly identify a target customer or ideal customer profile (ICP). It describes the game as being for players interested in city-building, resource management, logistics simulation, and exploration. However, there is no indication of specific demographics, user personas, or market segments.

Evidence Not evidenced; no mention of who plays this game or how it would be monetized.

There is no evidence provided regarding a business model or pricing strategy. The description does not mention any form of monetization, subscriptions, in-app purchases, ads, or other revenue streams.

Evidence Not evidenced; no indication of how the game might generate income.

The author states that the game was built as a lightweight browser experience using Astro, JavaScript, HTML Canvas, and CSS. It includes deterministic map generation, local saves, save migration, automated tests, generated building textures, and a custom isometric renderer.

It also features modules for terrain, buildings, economy, logistics, exploration, rendering, UI, and save management. The game supports multiple scenarios, a Creative mode, and seventeen building types.

Evidence Self-reported technical details; no evidence of scalability, performance metrics, or delivery infrastructure beyond the author's own account.

There is no evidence of traction or maturity in terms of user engagement, downloads, retention, or revenue. The project was submitted to a hackathon and has no data on active users, monetization, or growth trajectory.

Evidence Not evidenced; no signs of adoption, usage, or commercial success beyond the author's own description.

The description does not provide any information about competitors or the competitive landscape. It does not reference similar games, platforms, or market players.

Evidence Not evidenced; no mention of competition or market positioning.

• Single-person development team: The project is built by one person (Radek Jankowski), which raises questions about scalability and long-term maintenance.
• No commercial traction or monetization strategy: There is no evidence of users, revenue, or a clear path to profitability.
• Hackathon submission: This suggests the project is in an early stage and may not yet be ready for market.
• Lack of external validation: No third-party reviews, press coverage, or user feedback are mentioned.

Inference The lack of evidence for traction, monetization, or team capacity raises concerns about whether this will become a viable product.

1. What is the intended monetization strategy for Crown Harbor?
2. How does the game plan to scale beyond its current single-developer scope?
3. Are there any plans to add multiplayer or social features?
4. Has the founder considered how to attract and retain players in a crowded market?
5. What are the key performance indicators (KPIs) that will define success for this project?