The easiest way to lose a curious player is to put work between them and the game.

The Unfinished Kingdom is being built for the browser because entering the game should be as simple as opening a link. No large installer. No platform-specific build required before someone can try the first battle. A phone, tablet, laptop, or desktop should be enough.

A game renderer inside an ordinary interface

Browser-first does not mean the game has to feel like a web page with a combat animation pasted into it. A dedicated game renderer handles the battlefield while normal interface components handle menus, settings, the Armory, and account features. The device performs visual rendering and most routine simulation work. Servers will eventually validate important progression without being asked to render every sword swing.

That split matters for experience and cost. Continuous games can become expensive if every small action requires server processing. They can also become fragile if progression exists only inside the current browser tab. Our direction is local, responsive play paired with compact verified checkpoints and cloud saves when accounts arrive.

Installation stays optional

The game is also being prepared as a Progressive Web App. Players will be able to add it to a phone home screen and launch it in a more app-like window. The browser version remains the primary product, so installation is always optional.

The phone screen is the real constraint

Mobile browsers bring their own difficulties. Address bars expand and collapse. Bottom toolbars consume valuable space. Screen height can change while the player is doing nothing. The game cannot rely on an idealized phone rectangle. Its portrait layout has to survive the actual usable area left by Safari and Chrome.

Desktop players receive a wider presentation with more scenery and side panels, but mobile remains the strictest design test. If combat, currencies, skills, upgrades, and navigation cannot remain understandable on a phone, adding more pixels on desktop will not solve the underlying problem.

Our target is straightforward: click a link, press Start, and let Cabinet 14 do the rest.