Fast vs Pro
Appsanic offers Fast and Pro on paid plans. Both use the same project tools, permission checks, saved files and verification workflow. Fast is the default; Pro provides another model option for demanding work. Neither choice guarantees a correct or complete app.
Choosing a model
Start with Fast for focused edits, new screens that follow an existing pattern, and fixes with clear reproduction steps. Consider Pro for changes across several features, intricate state, or an attempt that missed your requirements. Compare the resulting behavior and settled cost on your own project.
Both models can read relevant project files through the agent's tools. Selecting Pro does not guarantee that the entire project fits in context or that every file has been inspected. State the requirements and the journeys that must keep working.
Reasoning effort
The reasoning control adjusts the effort requested for a run. More effort can help with a difficult task, but may take longer and consume more credits. The number of internal reasoning steps is not fixed or shown as a product guarantee.
The agent checks output and can attempt repairs on either model. Follow any remaining verification steps, particularly device behavior, provider operations and store submission.
What they cost
Each model has its own rate card. The actual charge depends on recorded model usage, reasoning effort, context, retries and applicable services. There is no fixed per-request multiplier or fixed price for a one-line change.
The pricing examples apply current rates to recorded workloads and identify their dates and assumptions. Pro figures there are identical-usage illustrations, not measured Pro runs. Credits explains monthly allowances, spending limits and settlement.
Free includes templates and the code editor; running AI planning or build prompts requires an eligible paid plan.
Planning and switching
Choose a model before sending a build request. Changing the picker affects later requests, not an already running job.
Plan Mode is a separate planning workflow with its own configured model and metered usage. The Fast/Pro build choice does not make the planner run that same model. Review and refine the plan, approve it when ready, then use your selected build model for implementation.
A useful sequence is:
- Describe the behavior and constraints.
- Review the plan before approving a build.
- Exercise the completed output and report any gaps.
- Choose Fast or Pro for the next change based on its difficulty and the results so far.
Use Stop when you need to cancel a run. Wait for its final status before retrying, and check Account usage for its settled charge.
Next
Read Writing Prompts for concrete requirements and Credits for budgeting.