Free plan: 1 active project, unlimited prompts, one platform (iOS or Android), bring your own AI agent, no card

EA Elena Avramenko@modaalbuilder

I barely open Figma or Claude Design anymore. My mobile vibecoding workflow:
-> Before: every screen in Claude Design, then a transfer into a builder. -> Now: the design lives where the build happens, and the whole loop runs on HTML before a line of Swift is written.
Why the old loop was slow: a general design tool needs the mobile context every time. Layouts for iPhone and for Android, safe areas, native principles like Liquid Glass, no website sizes. Many prompts per screen, then the hand-over into a builder, then the same questions again.
The steps, so you can set it up yourself:
1/ Give the agent the context. "I want to build a mobile app [give description] in this design style", plus add mood board: references I like, what I already have, what I do not want. Drop all as images to the Modaal.dev.
2/ Ask for three screens for your app in that style. Modaal returns the three screens, wireframes for the rest of the app, and the PRD, and shows the screens on different devices, with the safe areas.
3/ Iterate on the HTML until the direction is right. An HTML change takes seconds; a native build takes minutes. This is where the time goes, and where it is cheap.
4/ Pick the app design direction you like, then build flow by flow, screen by screen, each one against the design you already approved.
5/ At the end, the rest: micro-animations, the small emotional moments.

The result I feel now - building in html is about 10× faster vs directly writing in Swift, starting from mood board gives a lot of clarity on how you feel the app should be, and be less generic.

What does your design-to-build step look like today?
--
P.S. We're building Modaal - an AI app builder for native iOS and Android apps. Real Swift and Kotlin, written by your own AI agent, on a plan you approve first. Free plan, no card.

#vibecoding #Apps