Building tips

Short answers to the questions people ask most often when they are starting out.

How do I write a good initial prompt?

Focus on core features and functionality. Do not mention specific technologies or programming languages — Floot picks the stack. Keep it concise; you will add detail as you go.

If the idea is still fuzzy, use Plan mode instead of trying to write the perfect prompt.

Any general build tips?

• Use Discuss mode for planning; turn it off when you want to actually build
• Feed Floot smaller, focused prompts rather than one giant brief
• Test a lot — after each change, click through the flow in the preview
• Handle UI polish last, and use the Annotate tool for visual changes
• Ask for a named checkpoint before a risky change so you can jump back

Should I try Floot before committing?

Yes. Use your free credits to see how far you get — and reach out if you get stuck. Free accounts can keep up to 2 projects with 1 published app; upgrade when you need more.

Will Floot perfectly match a complex design?

Not always. For the best results, attach design images and detailed notes about what should change. Iterating on one screen at a time beats asking for a whole redesign in a single prompt.

What if Floot keeps going in circles?

If the same error survives three attempts, stop and change the approach — restore to an earlier checkpoint, or switch to Discuss mode and work out what is really going on. See Troubleshooting.