Product documentation
Build, refine, and publish your app.
Practical guidance for taking an idea from the first request to a tested, shareable app.
Quick start
Create a first project in a few focused steps. You can refine every decision later.
- 1
Open the workspace and describe the result you want, who will use it, and the most important action they should complete.
- 2
Choose Action for a direct change or Plan when you want to review the approach and credit quote before building.
- 3
Let the build finish, then test the main workflow in Preview on desktop and mobile sizes.
- 4
Ask for focused changes one at a time. State what should remain unchanged when it matters.
- 5
Deploy when the preview is ready, then share the published link or connect your own domain.
Ways to build
Use the entry point that best fits your workflow. All three methods create projects you can continue editing in the builder.
Type a request
Describe the app in the workspace and refine it through follow-up messages.
Open workspaceCall to build
Discuss the idea by phone, confirm the app name, and approve the plan before building.
Call nowStart from a template
Load a working design, then replace its content and features with your own.
Browse templatesUse a template
Templates are complete starting points. They are best when the layout is close to what you need.
- 1
Open Templates and choose a design that matches the type of app you need.
- 2
Load the template to create a new project with an immediate preview.
- 3
Replace sample names, numbers, images, and actions with your real content.
- 4
Test each visible control before publishing. Sample data is for preview only until you connect persistent data.
Builder workspace
The builder keeps your conversation, project controls, code, and live preview in one workspace.
Action and Plan
Action applies a request directly. Plan lets you review the approach and approve the quote before implementation.
Preview and Code
Preview runs the app. Code lets you inspect the generated files without leaving the project.
Device sizes
Switch between desktop, tablet, and mobile views to find layout issues before deployment.
Content and Migration
Use project tools to manage content or bring an existing project into the workspace.
Cloud and Database
Connect persistent data and manage the resources the app needs.
Deploy, Domain, and Share
Publish a tested build, attach a domain, and control how other people access it.
Write effective prompts
A useful request describes the outcome and constraints without dictating unnecessary implementation details.
A strong request includes:
- The audience and main goal
- The essential pages or views
- The primary actions users take
- Real content, labels, and data rules
- Visual direction and brand colors
- Mobile or accessibility requirements
Example: Build a mobile-friendly client portal for a coaching business. Clients should sign in, view sessions, complete tasks, and send a contact request. Use a calm neutral palette with green for completed work.
Preview and test
A successful build is not finished until its main workflow has been tested.
- 1
Open every page and confirm that navigation reaches the expected destination.
- 2
Use forms, menus, dialogs, filters, and important buttons with valid and invalid inputs.
- 3
Check desktop, tablet, and mobile sizes for clipped text, overlap, and unreachable controls.
- 4
Confirm that saved information still appears after a refresh when the app uses a database.
- 5
Resolve visible errors in Preview before deploying or connecting a custom domain.
Restore a version
Use project history when a recent change is worse than the last working version.
Open the version or history control, compare the saved point with the current project, and restore the version you want. Restoring changes the project files, so preview the result before making additional edits or deploying.
Deploy and share
Deployment creates a public version of the project. Preview remains the place to test unfinished work.
- 1
Finish the build and test the latest preview.
- 2
Select Deploy and review any displayed credit cost or required setting.
- 3
Wait for the published link, then open it in a separate browser window.
- 4
Use Share when collaborators need project access, or send the public link to visitors.
- 5
Deploy again after later changes when you want the public version updated.
Custom domains
Connect a domain you control after the app has a successful deployment.
- 1
Open Domain in the builder and enter the full domain or subdomain you want to use.
- 2
Add the displayed DNS record at the company that manages your domain.
- 3
Return to the project and verify the domain after the DNS change has propagated.
- 4
Keep the DNS record in place. Removing or changing it can disconnect the published app.
DNS changes are not instant. If verification fails immediately, confirm the exact host and value, then retry later.
GitHub and downloads
Keep a copy of the project outside TikkaBurrito when you need source control or a local handoff.
GitHub
Connect GitHub, select a repository, and push the current project files. Review repository access before authorizing a connection.
Download
Download the current files when you want a portable copy. A download does not include private account credentials or connected secrets.
Data and secrets
Persistent apps need a data connection. Private credentials should be stored only in the controls intended for secrets.
- Use Database to provision or connect the data source used by the project.
- Use Cloud or environment controls for API keys and private configuration.
- Never paste passwords, private keys, access tokens, or customer data into a build prompt.
- Test create, edit, delete, sign-in, and refresh behavior before publishing a data-backed app.
- Remove unused connections and rotate a credential if it was exposed.
Credits and billing
Credits pay for build work. Plans, renewals, payment methods, and invoices are managed from Billing.
When a build needs approval, review its quote before continuing. Approval authorizes the displayed credit amount, not an additional subscription.
Open Settings, then Billing, to view the current plan, renewal state, payment methods, invoices, and available plan changes. A pending cancellation can be resumed from the same page.
Contact support before retrying a charge or plan change repeatedly if the billing page reports an error.
Security and privacy
Treat generated apps and their connections like any other production software.
- Share project access only with people who need it.
- Keep secrets out of prompts, screenshots, public repositories, and downloaded files.
- Review generated forms and data access before collecting personal information.
- Use your own privacy notice and consent flow when your published app collects visitor data.
- Report suspected abuse or unauthorized access through Support.
Troubleshooting
Retry only after checking the message shown by the builder. Repeated retries can hide the original cause.
The project could not be created
Confirm that you are signed in, enter a clear request, then retry once. Refresh the workspace if the same message remains.
The build paused before completion
Open the project and use Retry build. Your last request is saved, and a paused build should not keep its quoted credits.
A quote needs approval
Review the displayed credit quote and approve it before starting or retrying the build. The builder will not proceed without approval.
The preview is blank or reports an error
Wait for the build to finish, refresh the preview, and check another device size. Ask the builder to fix the visible error if it persists.
A deployment or domain is not ready
Check that the latest build has a working preview first. Domain changes can take time to update across the internet.
Changes were not saved
Keep the project open, reconnect to the internet, and retry the last request. Contact support before starting over if work is missing.
Get support
Send the project link, the exact action you took, and the complete error message. Do not include passwords or API keys.