The standalone UI layout planner
Explore screens and navigation before choosing how to build the application.
Reviewed 6 October 2026 · 2 min read
A design study, without an app project
The UI layout planner is a separate opt-in tool. Ask explicitly for a UI/UX plan or wireframe, then accept its offer. Ordinary “build a website” requests should not silently start it.
It creates declarative screens made from headings, text, cards, inputs, images and buttons. Buttons can navigate between the reference screens. You can explore a layout without installing an operating-system SDK.
I want a standalone UI layout study for a reading tracker. Offer the layout planner first. Show a library, book details and an add-book screen; I’ll decide on a framework later.
What the preview does and does not do
The browser preview demonstrates layout and screen-to-screen navigation. It does not run authentication, save a real form, or prove that an app works. Fonts and native controls can differ on the final platform.
The planner can consider web, Windows, Apple, Roblox or another target. “Platform-aware” means it can include constraints in the design brief; it does not turn a browser mock-up into a native application.
Turn the reference into a product
- Review the hierarchy, labels, empty states and main user journey.
- Request a specific revision, such as a quieter toolbar or clearer primary action.
- Choose a target framework and ask Helios to implement the accepted design.
- Build, run and test in the actual target runtime. Test keyboard access, narrow layouts and the main interaction.
Use this accepted layout as a reference. Build a working web app, keep its reading data locally, and test adding, filtering and completing a book. Distinguish the design reference from the tested implementation.