The basics
What is Modaal?
What is Modaal?
What is spec-driven development? How is it different from vibe coding?
What is spec-driven development? How is it different from vibe coding?
- define requirements and constraints up front
- document system design + key decisions
- break work into implementable tasks with acceptance criteria
- keep everything traceable from intent → implementation
How is Modaal different from Cursor/Claude or other AI coding tools?
How is Modaal different from Cursor/Claude or other AI coding tools?
- generating full app structure (screens, navigation, data models, modules)
- maintaining cross-artifact synchronization (spec ↔ design ↔ data ↔ code)
- producing native code that compiles, runs, and is meant to ship
Getting started
How can I get started with Modaal?
How can I get started with Modaal?
- Describe what you want to build (users, key journeys, must-have features)
- Work on screens, flows, and logic (iterate in plain language, step by step)
- Check how it looks on simulator or real device
What should I provide to get the best results?
What should I provide to get the best results?
- core user journeys (happy path + 2–3 key edge cases)
- your MVP feature list and what “done” means
- data objects you care about (e.g., User, Project, Session)
- any must-have constraints (offline, background work, sensors, auth, etc.)
- example apps you like (for UX reference)
Can I import designs (Figma) or bring my own design system?
Can I import designs (Figma) or bring my own design system?
What is the difference between Vibe, Refine and Specify
What is the difference between Vibe, Refine and Specify
-
Vibe -
“I have an idea, just go with it.”
Use for: brainstorming, quick prototypes, exploratory coding, creative experiments.
-
Refine -
“Turn my idea into a well-structured PRD.”
Use for: PRD refinement, requirements clarification, specification writing.
-
**Specify - **
Rigorous cycle: specification → planning → tasks → implementation.
Use for: complex projects that benefit from structured execution, or when requirements are already clear.
- Clarify — close gaps in requirements, ask/answer key questions
- Plan — propose architecture + approach
- Tasks — break into executable tickets / steps
- Analyze — sanity checks (edge cases, consistency, risks)
- Implement — write the code and wire everything together
Default recommendation: if you’re not sure, start with Refine.
Once the PRD is solid, switch to Vibe (move fast) or Specify (go structured).
Code and ownership
Do I own the code?
Do I own the code?
Can I edit the code after export?
Can I edit the code after export?
- refactor
- add libraries
- integrate your backend
- ship through your normal CI/CD
Platforms and tech
Which platforms are supported?
Which platforms are supported?
What stack does Modaal generate?
What stack does Modaal generate?
- SwiftUI screens for iOS
- data models and API logic
- background tasks where relevant
Capabilities
Can Modaal handle complex app features?
Can Modaal handle complex app features?
- widgets and OS surfaces (e.g., Live Activities)
- offline mode and background work
- sensors / hardware access
- watch companions (where relevant)
- performance-critical experiences
Can I use Modaal with my existing backend and APIs?
Can I use Modaal with my existing backend and APIs?
- endpoints + auth method
- key request/response shapes
- error states and retry behavior you want
How the workflow stays coherent
How does Modaal keep specs, design, and code in sync?
How does Modaal keep specs, design, and code in sync?