@Hicham Char Love this question 🙌 Short answer: way less effort than it looks once you lock in a pattern. What I did in this build was basically: 1. Let Gemini 3 handle the “bones” of the UI • One-shot prompt → layout, components, basic state. • I treat that as a static front first: buttons, forms, lists, modals all wired visually, but with fake handlers. 2. Move to Cursor and turn UI events into real hooks • In Cursor, I go through the key interactions and do a simple pass: • onSubmit → call Supabase insert/update • onClick → fetch, filter or trigger a mutation • Cursor is great here because you can literally say: “Wire this handleCreateClient to insert into the clients table with fields X, Y, Z” and it will scaffold 80–90% of the code. 3. Drop in Supabase once, reuse everywhere • Add Supabase client + env vars once (SUPABASE_URL, ANON_KEY). • Create small helper functions in one file (e.g. db.ts) like createClient, getClients, updateClientStatus. • Then most of the effort is “connect UI event → call helper function” which is fast with AI help. In terms of real effort: • Getting the first UI from Gemini: 2–3 minutes • Wiring the main flows (auth + CRUD + a couple of views) in Cursor: 5 focused minutes • The rest is just small iterations and polish. Biggest win: you’re never rewriting the UI. You just layer real logic underneath what Gemini gave you, and let Cursor do most of the glue work.

@Hicham Char Thanks so muc! I did define JSON schemas, but they’re not insanely rigid — the reliability comes more from naming + descriptions + a bit of validation in n8n than from super–strict schemas.

@Habeebat Ismaeel Thanks so much!

@Kyren Cater Thanks so much!

@Rodrigo Anez Thanks so much!