Getting started: your first app
How to describe an app so Raina builds exactly what you had in mind, and what happens behind the scenes.
You don't need a spec, a wireframe, or any code — just describe the app the way you'd explain it to a friend. "A gym membership system with plans, renewals, and trainer schedules" is a complete first prompt. Even something as short as "I want to rent out cars" is enough to start.
What Raina actually does with your prompt
Before writing any code, Raina reads your description like a business analyst: what are the real entities involved (a car-rental request implies Car, Customer, Booking, and Payment — not just the ones you named), who uses the system (an admin/staff view gets built automatically if your description implies one — "manage," "dashboard," "approve"), what rules the business enforces (no double-booking, a late fee after a cutoff), and what the 2-4 key user journeys are.
That analysis becomes your app's actual data model and screens — not a mockup. If you asked for late fees, the fee is actually computed and enforced in the code, not just mentioned somewhere.
Tips for a better first build
More specific prompts produce more complete first builds. "A kanban board" gets you a working kanban board; "a kanban board for a five-person design team, with due dates and priority tags" gets you closer to what you'd actually use.
Don't worry about getting it perfect the first time — the fastest path to the right app is usually a decent first build followed by a couple of specific follow-up changes, not one perfect prompt.