CityFrame — a web-first map wallpaper generator
What it is
CityFrame turns any location on earth into a 4K map wallpaper, tuned for six device classes — phone, tablet, desktop, ultra-wide — in seconds. The product is web-based, so there is nothing to install. Pick a city, pick a style, download the set.
Why we built it
Every competitor in this niche was mobile-only, phone-only, and subscription-only. You had to install a native app, sign in, and pay monthly for something you used three or four times a year.
We saw room for the opposite: a web-first tool that supports every device class, needs no install, and sells once for lifetime access instead of running a subscription loop. CityFrame is the product of that bet.
What we shipped
- An interactive map picker with 21 distinct wallpaper styles — from minimalist line art to cinematic neon
- Six device presets covering phone, tablet, desktop, and ultra-wide monitors
- Optional AI enhancement for sharper 4K output
- Per-city pages with shareable URLs, so a wallpaper you generated can be handed to someone as a link
- Email sign-in with no password, lifetime Pro unlock — one payment, every feature forever
- Live on the web at cityframe.app
[SCREENSHOT: homepage hero with the map picker and style gallery] [SCREENSHOT: a generated wallpaper mocked up on a desktop monitor]
Numbers
CityFrame has generated roughly 2,000 wallpapers across the free and Pro tiers since launch. Pro is a lifetime purchase, so there is no MRR figure to report — what we have instead is a cohort of one-time buyers who return when they travel or move. We will share more numbers in a future post as the data window widens.
What we learned
Subscription by default isn't the right answer for every product. Most consumer SaaS assumes monthly recurring revenue is the only viable model. For a product where the user's need is episodic, not continuous, a lifetime purchase builds more trust and less churn — at the cost of squeezing unit economics on every single generation for the rest of the product's life. We accepted that trade deliberately.
Ship the simpler thing first. We launched with more infrastructure than we needed and took half of it out again in the first few weeks. The product now runs on a smaller, cheaper, more reliable footprint than the original plan, because real traffic told us what actually mattered faster than any spec could.
What this means for client work
Building CityFrame taught us that the hard part of a consumer product isn't the headline feature — it's the billing, the authentication, the per-use economics of AI, and the discipline to throw away infrastructure you no longer need. Which is why when clients ask us about adding AI features to their own products, the first conversation we insist on is the cost math, not the model choice. If the unit economics don't close, the feature doesn't ship.