# Brand & Communication Source: https://docs.aiwa.codes/agency/brand-studio Set your agency's name, logo, colour, tagline and invitation wording in AIWA, preview what clients see, and send client e-mail from your own address. Your clients should see your agency, not AIWA. The **Brand & Communication** tab of the agency console controls how your agency appears in the client portal, on invitation pages and in every e-mail clients receive. **Your name, your logo, your voice.** Brand & Communication is part of the [agency console](/agency/console-overview), available on the Agency and Enterprise plans. Owners and Admins can edit it. ## Your Agency's Identity | Field | Where clients see it | | - | - | | **Agency name** | Invitations, the invitation page, the client portal and e-mail sign-offs | | **Logo** | Invitations and the client portal, in place of your name | | **Accent colour** | Buttons, highlights and comment pins in the portal | | **Tagline** | One line under your name in the portal and on the invitation page | | **Contact e-mail** | Where client replies land, and where the portal's Help link writes to | ### Logo Drop your logo into the logo field, or paste it. If you don't have a logo yet, choose a logo style and select **Generate two logos**. Pick the one you like; it becomes your logo when you save. ### Accent colour Pick a colour, or select **Suggest colours** for two accents that read well in the app. You can give a mood to steer the suggestions. AIWA checks that the colour is readable on the app's background. If it is too dark, the save is refused and a lighter version is suggested. ## Invitation Wording You can personalise the invitation e-mail your clients receive: * **Subject**: leave it blank to use the standard subject * **Introduction**: leave it blank to use the standard introduction Select **Write for me** to have AIWA draft both the subject and the introduction in your agency's voice. Edit the result before saving. ## Live Preview Beside the form, a live preview shows your unsaved changes: * **Client portal**: your header, buttons and comment panel, as clients see them * **Invitation e-mail**: the subject, introduction, sender and reply-to address Switch between desktop and phone widths to check both. ## What the Brand Helpers Cost The AI helpers are paid from your workspace's credits: | Helper | Cost | | - | - | | Suggest colours | 1 credit | | Write for me | 1 credit | | Generate logos | 4 credits per logo delivered (2 logos per run) | If AI suggestions are unavailable, AIWA offers a curated suggestion instead, free of charge. There are fair-use limits so a loop can't turn into a bill: up to 30 text suggestions an hour and 8 logo generations a day. Brand helper spending appears as **Brand helpers** on the [Usage tab](/agency/spend-limits). ## Your Sending Address By default, client e-mail goes out from AIWA's address under your agency's name. Replies go to your contact e-mail. To send from your own domain instead, connect your agency's Resend account: In Brand & Communication, find **Sending address** and choose to connect. Use a Resend API key with **full access**, so AIWA can verify your exact sending domain. The key is encrypted and never shown again. Enter the address mail should come from and select **Verify and save sender**. Once connected, the tab shows which address e-mail leaves from. You can send a test e-mail, or disconnect at any time. After disconnecting, e-mail goes out from AIWA's address again until you connect another sender. ## Failed E-mails If a notification e-mail can't be delivered after several attempts, or the recipient's server rejects it, it appears under **Failed e-mails**. Select **Retry** to queue it again. A message the recipient marked as spam can't be retried. Failed invitations and notifications also appear under **Needs you** on the console's Overview. ## Next: Spending Limits & Usage With your brand in place, the next step is controlling how credits are spent across your team and projects. Set monthly allowances per person and budgets per project, and see where credits go. # Client Hand-off & Sign-off Source: https://docs.aiwa.codes/agency/client-handoff Hand a finished, live AIWA project to your client, get their sign-off, and give them Traffic and Accounts pages for their site. A hand-off tells your client their live site is finished and theirs. The client receives a clear summary of what they're getting, and signs it off when they're happy. Optionally, they also get a **Traffic** page and an **Accounts** page for their site. **Finish projects cleanly, with a record that the client agreed.** Hand-offs are part of the [agency console](/agency/console-overview), available on the Agency and Enterprise plans. ## Before You Start To send a hand-off: * The project must be **live** (published). * At least one **client** must be on the project. If there isn't one, the dialog opens the invite dialog first. * You need permission to **publish** the project. ## Send a Hand-off In the agency console, open **Projects** and find the live project. Select **Hand off** on the project's row or card. The dialog names the clients who will receive the hand-off. Write a short note to the client, up to 2,000 characters. Switch **Site traffic** and **Manage accounts** on or off. See below. The dialog shows the hand-off document exactly as the client will read it. Send it when it looks right. ## What the Hand-off Document Contains The document summarises the finished site: * Its address * Its pages * What the site keeps (its data) * The connected services * How to get help It also lists what the client can do in their portal, such as leaving comments on the site, viewing traffic and managing accounts. The client can select **Download PDF** to save a copy using their browser's Save as PDF. ## Traffic and Accounts Two switches decide which extra pages the client gets. ### Site traffic On by default. The client gets a **Traffic** page showing: * Page views * Visitors (counted per day, so someone who visits on two days counts twice) * Top pages * Where visitors come from They can look at the last 7, 30 or 90 days. ### Manage accounts On by default when the site has sign-in. The client gets an **Accounts** page listing the people with an account on their site. From it, they can: * Invite someone (they get an e-mail to choose their own password) * Deactivate or reactivate an account * Send a password reset * Sign an account out Only the workspace Owner can switch **Manage accounts** on. Anyone who can send the hand-off can switch it off. Each change a client makes on the Accounts page appears in your console's **Activity** log, for your team only. Your team manages accounts through **App users** in the builder. You can change both switches later from the same dialog. Changing them doesn't e-mail anyone. ## Sign-off The clients receive one e-mail linking to the hand-off page in their portal. The first client to select **Sign off** completes it. They can add an optional note. Signing off tells your agency the project is finished as handed over; the client can still leave comments afterwards. When the client signs off, the Owner, the Admins and the person who sent the hand-off are told. In the console's **Projects** tab, each project shows where its hand-off stands: * **Waiting for sign-off** * **Signed off** Use the two filters of the same names to see them together. ## Withdraw or Send Again * A hand-off waiting for sign-off can be **withdrawn**. Nobody is e-mailed. * You can replace a waiting hand-off with a new one and a new note. * A signed hand-off stays on record. **Hand off again** asks the client for a new sign-off. ## A Hand-off Changes Nothing on the Site Sending, changing, withdrawing or signing a hand-off never touches the site or its deployment. Publishing doesn't depend on a hand-off either. It is a record between you and your client, not a release step. ## Next: Building From Telegram Agency owners can also check on projects and request work from their phone. Next, we'll look at the Telegram assistant. Connect Telegram and check on projects, get links and request builds from a chat. # The Client Portal Source: https://docs.aiwa.codes/agency/client-portal What your clients see in AIWA: a branded portal with their live site, pinned comments and threaded replies, and no access to your builder, files or spending. The client portal is where your clients see their work. It shows the live site for each of their projects, with a comment panel beside it, under your agency's name, logo and colour. **One calm page per project.** Client invitations and the client portal are available on the Agency and Enterprise plans. ## How a Client Arrives You invite the client from the agency console or the project's People tab. They receive an e-mail under your agency's name. The link opens a page naming your agency, the project and the invited e-mail address, before the client has an account. The client signs up or signs in with the invited address. Where it's enabled, they can ask for a one-time sign-in link instead of choosing a password. The client lands in the portal for their projects. ## What the Client Sees ### Their projects The portal lists the client's projects under your brand. If they have only one, it opens straight away. ### The live site Each project page shows the published site in a frame. * If the project isn't published yet, the portal says so instead. * While a new publish is landing, the site stays visible and a bar says it is updating. Publishing is the release. The client always sees what is live at the project's address, never a draft. ### The comment panel Beside the site is the comment panel, where the client can: * Drop a pin on a spot on the page and comment on it * Leave a comment about the whole site * Read your team's replies and reply back * Mark their own comment as done, or reopen it * Select **Looks good** when they're happy See [Commenting & Feedback](/teams/commenting) for how pins and threads work. ### Focus mode Focus mode puts the site full screen, with the comment panel at its side. It works on phones too: when a client places a pin, the panel moves aside so the comment bubble stays visible. ### Help The portal's Help link writes to your agency's contact e-mail, so client questions come to you. ## What the Client Never Sees * The builder, prompts or chat * Files and code * Deploy and hosting details * Your other team members or other clients * Credits, spending or billing Clients don't take a seat on your plan and never spend your credits. ## After a Hand-off When you [hand off](/agency/client-handoff) a project, the client's project page gains a small menu: | Page | What it shows | | - | - | | **Site** | The live site and comments | | **Hand-off** | The hand-off document, with Sign off and Download PDF | | **Traffic** | Visits to their site, if you shared it | | **Accounts** | The people with an account on their site, if you shared it | ## Preview the Portal as Your Client Your team can open the client view of any project to see exactly what the client sees. On the Accounts page, the team sees a note that only the client changes accounts there; the team uses **App users** in the builder. You can also preview your portal's branding in [Brand & Communication](/agency/brand-studio) before inviting anyone. ## Next: Client Hand-off & Sign-off When the work is finished, you can formally hand the site to the client and ask them to sign it off. Hand a live project to your client, get their sign-off, and share Traffic and Accounts. # The Agency Console Source: https://docs.aiwa.codes/agency/console-overview Run client work from one place in AIWA: turn on your agency profile, then manage projects, clients, team, usage, activity and brand from the agency console. The agency console is where an agency runs its client work in AIWA. It brings together everything that happens across your projects: what clients said, which sites are live, who is spending credits, and what still needs an answer. **One place to see the whole agency.** The agency console is available on the Agency and Enterprise plans. ## What the Agency Profile Adds The console is not a separate product. It is a layer on top of your ordinary AIWA workspace, switched on by your **agency profile**. With the profile on, you get: * **The console**, in the sidebar as **Agency console** * **A branded client portal**: clients see their sites under your agency's name, logo and colour * **Branded e-mail**: invitations and comment notifications go out under your agency's name Some things work the same whether the profile is on or off: * Inviting team members and clients, and choosing who sees which project * Monthly allowances and project budgets * Comment e-mails between clients and your team ## Turn On Your Agency Profile In the sidebar, open **Agency console**. If the profile is off, the console shows the setup step. Add your agency's display name, logo, accent colour and a contact e-mail address. Only the workspace Owner can switch the profile on or off. Connect your own Resend account so e-mail leaves from your domain. Until then, e-mail is sent from AIWA's address under your agency's name. See [Brand & Communication](/agency/brand-studio). Turning the profile off later hides the console, removes your branding from the portal and stops the one-time sign-in links in invitations. It doesn't change anyone's access and doesn't stop comment e-mails. ## The Setup Checklist Until your setup is complete, the Overview shows a checklist with the next step highlighted: | Step | Required | | - | - | | Name your agency | Yes | | Add a client contact e-mail | Yes | | Add your logo | Optional | | Personalise your invitation | Optional | | Connect a sending address | Optional | | Create your first project | Yes | | Send your first invitation | Yes | Once the required steps are done, the checklist shrinks to a "Setup complete" row that still lists the optional steps. ## The Console Tabs Owners and Admins see every tab. Other team members see Overview, Projects and Activity. ### Overview How the agency is doing and what needs an answer. * **Counts for a period**: credits spent, client comments (and how many are still open), sites published and clients joined. Choose Today, or the last 7, 30 or 365 days. * **Top spenders** for the period. * **Needs you**: open client comments that nobody on your team has replied to, invitations whose e-mail failed, and notifications that couldn't be delivered. * **Active projects**: the six with the newest activity, each saying what happened and when. ### Projects Every project you can see, with: * Its status: Live, Publishing or Not published * The client's company and who on your team is responsible * Open comments * The budget left * The client hand-off status Search, filter and sort the list, and switch between a **List** and **Cards** view. Two filters, **Waiting for sign-off** and **Signed off**, show where each [hand-off](/agency/client-handoff) stands. ### Clients Your clients, grouped by company, with their projects. Invite, resend, revoke, or remove a client from a project here. ### Team Your team members, with their role, scope, assigned projects and permissions, plus pending invitations and their e-mail status. Invite, change, remove, resend and revoke from here. See [Roles & Permissions](/teams/roles-permissions). ### Usage What each team member spent this month against their monthly allowance, and what each project has spent against its budget. See [Spending Limits & Usage](/agency/spend-limits). ### Activity The workspace's event log: comments, invitations, access changes, publishes and more. Filter by category, project, visibility and date. ### Brand & Communication Your agency's name, logo, colour, invitation wording and sending address, with a live preview. See [Brand & Communication](/agency/brand-studio). ## Notifications The bell in the console is your notification inbox. From it you can choose, for each category, how you want to hear about things: | Category | Choices | | - | - | | Feedback (comments, hand-offs) | Immediately, hourly digest, or off | | Operations (for example a failing sender) | Immediately, digest, or off | | Access (changes to your own access) | Always immediately | Clients receive e-mails only. They don't have an inbox. ## Next: Brand & Communication Your clients see your brand, not AIWA's. Next, we'll set up your agency's name, logo, colours and e-mail. Set your agency's logo, colour, invitation wording and sending address. # Spending Limits & Usage Source: https://docs.aiwa.codes/agency/spend-limits Control AIWA credit spending with a monthly allowance per team member and a budget per project, and see spending by day and by type on the Usage tab. When several people build in one workspace, they all spend from the same credit balance. Spending limits keep that under control. You can cap what each person spends in a month and what each project can spend in total. **Know where your credits go, and decide how far they can go.** ## Two Kinds of Limit | Limit | Applies to | Resets | | - | - | - | | **Monthly allowance** | One team member | At the start of each calendar month (UTC) | | **Project budget** | One project | Never. It is a total for the project's lifetime | For either limit: * **Blank** means no limit * **0** means no paid work at all Both limits are honoured on every workspace that has them set, whether or not the agency profile is on. ## Who Can Spend Credits Only people who can build can spend credits: * Owners, Admins and Editors spend from the workspace balance when they build. * Viewers and Clients never spend credits. Reviewing, commenting and replying are always free. ## How Limits Are Checked Before a paid action starts, AIWA checks, in order: 1. The person is allowed to spend on this project. 2. The workspace has enough credits. 3. The person's monthly allowance allows it. 4. The project's budget allows it. If any check fails, the action doesn't start and nothing is charged. Limits are checked when an action starts. Two actions started at the same moment can go over a limit by the cost of one action. ## What People See When a Limit Is Reached | Situation | Message | | - | - | | A team member's allowance is used up | "Your monthly allowance is used up." Reviewing and commenting still work; they can ask for more allowance. | | A project's budget is used up | "This project has reached its budget." An Owner or Admin can raise it from Usage. | | The workspace balance is used up | "The workspace balance is used up." Add credits to continue. | ## The Usage Tab Open the **Usage** tab of the [agency console](/agency/console-overview). Owners and Admins can see it. ### The month at a glance Three figures at the top: * **Spent this month** * **Balance**: the credits left in the workspace * **Resets**: when monthly allowances start again Below them: * **Spend day by day** for the month * **Spend by type**: | Type | Includes | | - | - | | Builds | Building and changing projects | | Brand helpers | Logo, colour and invitation-wording suggestions | | Briefs and ideas | Briefs, idea shuffles, voice transcription | | Mobile and release kits | Mobile readiness scans, Android builds, store kits | | Other | Anything else | The days and the types each add up to the month's total. The page also notes spending that isn't tied to a project, and spending by people who have since left. ### People What each team member has spent this month against their monthly allowance. ### Projects What each project has spent in total against its budget. ## Set a Limit In the agency console, open the **Usage** tab. Use the **People** table for monthly allowances, or the **Projects** table for project budgets. Enter a number of credits, leave it blank for no limit, or enter 0 to stop paid work. Limits aren't set in the invite dialog. Set a new team member's allowance here after they join. ## Good Practice * Give contractors a monthly allowance that matches the work you've agreed. * Give each client project a budget based on what you've quoted. * Check **Top spenders** on the console's Overview from time to time. * Use 0 to pause paid work on a project without removing anyone. For how credits themselves work, see [Credits and Plans](/billing/credits-and-plans). ## Next: The Client Portal Next, we'll look at the other side of the agency: what your clients see. The branded page where clients see their live site and comment on it. # Build From Telegram Source: https://docs.aiwa.codes/agency/telegram Connect your AIWA workspace to Telegram to check project status, get live links, and request new sites and changes from a private chat on your phone. You don't always have the builder open. The AIWA Telegram assistant lets you check on your projects and ask for work from a private Telegram chat. Describe a site, ask for a change, or ask how a project is doing, and AIWA replies in the chat. **Move work forward from your phone.** Telegram is available on the Agency and Enterprise plans, for the workspace Owner and Admins. Telegram may not be offered on every workspace. If you don't see the Telegram card in Settings, it isn't available for your workspace yet. ## Connect Telegram In AIWA, open **Settings** and find the **Telegram** card. AIWA creates a one-time connection command. It expires after a short time; the card shows a countdown. Select **Open Telegram** to open the AIWA bot with the code attached, or copy the command and send it to the bot in a private chat. Back in AIWA, the card updates when the connection is made. You can also select **Check connection**. If the command expires before you use it, start a new one. The card shows when your Telegram is connected. Select **Disconnect** to remove the connection at any time. The assistant works in private chats only. It doesn't work in group chats, and your clients can't use it. ## What You Can Ask Write to the assistant in plain language. ### Check on a project > How is the Oakwood Dental site doing? AIWA replies with the project's status and, once the site is live, its live link. ### Start a new site > Build a website for Oakwood Dental. It needs services, testimonials and a booking section. Make it calm and professional. If something essential is missing, AIWA asks one short question before it starts. It won't invent testimonials, contact details or business claims. ### Change an existing site > Change the hero headline to "Gentle dental care for the whole family". > Add a pricing section with three plans. ### Publish > Publish the site. > Go live. ### Just talk it through Questions, greetings and brainstorming don't start any work or spend credits on a build. Only a clear request to build, change or publish does. ## Builds Go Live Automatically From Telegram, a build or change request is published for you when it finishes. You don't need to approve a preview or open the dashboard. * AIWA only sends a live link once it has checked the address works. * While the site is publishing, AIWA tells you it will send the link when it's ready. Because Telegram builds publish automatically, be careful when asking for changes to a site that real customers are already using. For larger changes to a live site, use the builder and test in the preview first. ## Credits Telegram builds use your workspace's credits, exactly like builds in the builder. Your plan's limits, and any [spending limits](/agency/spend-limits) on you or the project, still apply. If you run out, the assistant tells you: > You're out of credits. Please add more and try again. Top up from Billing in AIWA, then ask again. ## If Something Goes Wrong If a build or publish can't be finished, the assistant says so in one short message and keeps your work saved. You can ask it to try again, or open the project in the builder. ## Next: Credits and Plans Every build, in the builder or from Telegram, uses credits. Next, we'll look at how credits and plans work. What a credit is, what uses one, and how plans and top-ups work. # Cancellation and refunds in AIWA Source: https://docs.aiwa.codes/billing/cancellation-refunds How to cancel your AIWA plan, what you keep afterwards, and when subscriptions and credit top-ups can be refunded. You can cancel your AIWA plan at any time. This page covers how to cancel, what happens to your account, and when you can get a refund. This page summarizes AIWA's [Refund and Cancellation Policy](https://aiwa.codes/legal). If the two ever differ, the policy applies. ## How to cancel Go to **Settings → Plan & usage** and choose **Manage billing**. Only the workspace owner can cancel. Choose to cancel your subscription and confirm. Cancellation takes effect at the **end of your current billing period**. Until then you keep your paid plan and its features. ## What happens after cancellation At the end of the billing period, your workspace moves to **Launchpad**: * Your projects and data are kept and stay accessible. * Unused **monthly plan credits** don't carry over. * Unused **top-up credits** stay in your account. * Your monthly allowance becomes Launchpad's 80 credits. You can reactivate at any time. A new billing cycle starts on the day you reactivate. ## Subscription refunds You can get a full refund of a subscription payment if: * You ask within **7 days** of the payment * You haven't used any credits in that billing period * It is your first refund request for a subscription payment If you've used any credits in a billing period, that period can't be refunded, and there are no partial refunds for partial use. Each billing period is treated separately. ## Top-up refunds A top-up you haven't used any of can be refunded within **7 days** of purchase. Once any of a top-up's credits have been used, it can't be refunded. ## AppSumo purchases AppSumo lifetime deals are refunded through AppSumo, within 60 days of purchase. If you have trouble with AppSumo's process, contact us and we'll help. ## How to request a refund Email **[billing@aiwa.codes](mailto:billing@aiwa.codes)** with: * The email address on your AIWA account * The date of the charge * A short reason for the request We aim to reply within 3 business days. Approved refunds usually reach your statement within 5 to 10 business days, depending on your bank. ## Technical problems and duplicate charges If a significant technical problem stopped you using AIWA and we couldn't fix it in reasonable time, contact us. You may be eligible for a refund or credit even outside the normal window. If you were charged twice, or see a charge you don't recognise, email **[billing@aiwa.codes](mailto:billing@aiwa.codes)** straight away. Please contact us before starting a chargeback with your bank. Most billing problems are solved quickly, and a chargeback without contacting us first can lead to the account being suspended while it is investigated. ## Next: Plan Inclusions See exactly what each plan includes. # What Each Action Costs Source: https://docs.aiwa.codes/billing/credit-costs What AIWA actions cost in credits: how builds and edits are charged, and the fixed price of images, voice, Explore, the Brief, mobile kits and other tools. AIWA charges credits in two ways: * **Builds, edits and repairs** are charged by the work your request needs. * **Standalone tools**, like generating an image or building an Android app, have a fixed price. ## Builds, edits and repairs A complete application, a one-line copy change and an automatic repair all need different amounts of work, so they cost different amounts. There is no single price for "a build" or "an edit". What goes into a build's charge: * Planning the work and checking the plan * Writing and checking the code * Generated images the build creates for your design * Any automatic repair rounds needed to make the build work After each request, the chat shows what was charged. That figure is the source of truth. AIWA is rolling out usage-based charging gradually. The charge shown in your workspace is always the one that applies to you. See [How credits work](/billing/how-credits-work#usage-based-charges). ## Standalone tools | Action | Credits | | - | - | | Ask a question in Explore mode | 1 | | Write a Brief (1 free per day, then) | 2 | | Generate an image | 4 per image | | Stock photo | Free | | Transcribe a voice message | 2 | | Shuffle the dashboard idea suggestions | 2 | | Mobile readiness scan (standard) | Free | | Mobile readiness scan (deep check) | 2 | | Build an Android APK | 10 | | Google Play release kit | 5 | | App Store submission kit | 10 | **Agency console brand helpers** (Agency plan): | Action | Credits | | - | - | | Generate a logo | 4 per logo delivered | | Suggest accent colours | 1 | | Suggest invitation copy | 1 | If a brand helper can't produce a result and falls back to a ready-made suggestion, you are not charged. On Launchpad you can shuffle idea suggestions up to 2 times a day. ## What's free | Action | Credits | | - | - | | Publishing and republishing | 0 | | Hosting your published app | 0 | | Connecting a custom domain | 0 | | Clarifying questions before a build | 0 | | Inviting teammates and clients | 0 | | Restoring an earlier version | 0 | Your plan's feature and project limits still apply. ## Budgeting your work * Be clear about what you want so AIWA gets it right the first time. See [Writing effective prompts](/building/writing-effective-prompts). * Use **Explore** (1 credit) to ask about your app before you change it. * Use a **Brief** when an idea is still fuzzy. It costs far less than a build in the wrong direction. * Ask for focused changes rather than rebuilding whole pages. ## Next: Monthly vs Top-Up Credits Learn how your plan credits and purchased credits work together. # Credits and plans Source: https://docs.aiwa.codes/billing/credits-and-plans How AIWA billing works in one page: what a credit is, what each plan includes, how top-ups work, and where to manage it all. Building on AIWA runs on **credits**. A credit is the unit of AI work: you hold a balance, building spends from it, and you top up or move to a larger plan when you want more. This page is the short version of the whole Billing section. Each part links to the page with the details. ## The plans at a glance | Plan | Price | Credits each month | Projects | | - | - | - | - | | Launchpad | Free | 80 | 5 | | Solo | \$20/month or \$210/year | 200 | 100 | | Agency | \$149/month or \$1,565/year | 1,000 | Unlimited | | Enterprise | Talk to us | Custom | Unlimited | Agencies that want to resell AIWA under their own brand can join the [White Label program](/white-label/overview). See [Plans overview](/billing/plans) for what each plan is for, and [Plan inclusions](/billing/plan-inclusions) for the full feature list. ## What uses credits Work that asks the AI to think, write or fix something costs credits. Work that only manages your own projects does not. Building and editing a project, planning, automatic repairs, generated images, voice transcription, mobile build kits and a few other AI tools. Opening and editing your projects by hand, publishing, connecting a domain, inviting teammates and managing your account. A larger request costs more than a small one because it is more work. A one-line change to a button is cheap. Building a new section from scratch is not. See [How credits work](/billing/how-credits-work) and [Credit costs](/billing/credit-costs). ## Two kinds of credits Your plan's allowance. It resets to the full amount at the start of each monthly cycle. Credits you buy on a paid plan, at \$0.10 each. They never expire. AIWA spends your monthly credits first and only then dips into top-ups. See [Monthly vs top-up credits](/billing/monthly-vs-topup) and [Topping up](/billing/topping-up). ## Where to manage billing Everything lives in **Settings → Plan & usage**: * **Upgrade** or **Change plan** to compare plans and upgrade. * **Add credits** to buy a top-up. * **Manage billing** to open the secure billing portal, where you can update your card, see invoices, downgrade or cancel. Only the workspace owner can change the plan or pay. Your balance is always visible while you build, so you can watch a charge land as it happens rather than discovering it later. ## Running low If your balance runs out in the middle of a build, a one-time overdraft lets the build finish. After that, top up or upgrade to keep going. Nothing about your projects changes while you decide. If a payment fails, your plan and credits stay in place while you fix it. See [Failed payments](/billing/failed-payments). ## Next: Plans overview Compare Launchpad, Solo, Agency and Enterprise in detail. # Failed payments in AIWA Source: https://docs.aiwa.codes/billing/failed-payments What happens when a payment fails on your AIWA account, how to fix it, and why your projects and published apps stay online. Sometimes a payment doesn't go through: a card expires, a bank declines the charge, or a payment needs extra confirmation. This page explains what happens and how to fix it. ## What happens when a payment fails When a subscription payment fails, your account enters a **grace period**: * You keep your plan and its features. * You keep your credits and can keep building. * Your projects and published apps stay online. * Your subscription is marked as **past due** until the payment succeeds. While a payment is outstanding you can't change your plan. Settle the open payment first, then upgrade or switch. ## How to fix it Go to **Settings → Plan & usage** and choose **Manage billing**. Only the workspace owner can do this. Add a new card or update the details of your existing one. Pay the outstanding invoice from the portal. Your subscription becomes active again as soon as it is paid. ## If an upgrade payment fails If you upgrade and the payment is declined or needs bank confirmation, the upgrade waits. You stay on your current plan until the payment completes. Nothing is lost. ## If the subscription is eventually cancelled If a payment is never completed and the subscription ends, your workspace moves to **Launchpad**: * Your projects, versions and data are kept. * Your top-up credits are kept. * Your monthly allowance becomes Launchpad's 80 credits. * Paid features, such as custom domains and badge removal, stop applying. You can subscribe again at any time to get your plan back. ## Avoiding failed payments * Keep your card details up to date in **Manage billing**. * Check that your bank allows recurring payments to online services. * For annual plans, make sure your card is valid at renewal time. ## Need help? If you think a charge is wrong or was taken twice, email **[billing@aiwa.codes](mailto:billing@aiwa.codes)** with your account email and the date of the charge. ## Next: Cancellation & Refunds How to cancel your plan and when you can get a refund. # How Credits Work Source: https://docs.aiwa.codes/billing/how-credits-work Credits measure AI-powered work in AIWA. Learn what uses credits, why requests cost different amounts, the one-time overdraft, and how to see your balance. Credits measure the AI work AIWA does for your projects. Building, editing, planning, generated images and automatic repairs use credits. Looking at your project, publishing it and managing your account do not. ## What uses credits | Uses credits | Free | | - | - | | Building a new project | Opening and browsing your projects | | Editing and iterating | Sharing preview and live links | | Planning in Plan mode | Publishing and republishing | | Automatic repairs after a build | Connecting a custom domain | | Questions in Explore mode | Inviting teammates and clients | | Generated images | Restoring an earlier version | | Voice transcription | Clarifying questions AIWA asks before a build | | Mobile build kits | Managing billing and settings | See [Credit costs](/billing/credit-costs) for the price of each standalone action. ## Why requests cost different amounts A small edit and a complete application are very different amounts of work. ```text theme={null} Change a button label → little work → few credits Add a booking page → more work → more credits Build a SaaS with login, database, payments, dashboard → a lot of work → many credits ``` There is no fixed number of apps or edits that a credit allowance buys. As a guide, Launchpad's 80 monthly credits are sized to cover one complete first build plus a few edits. The charge shown in your builder after each request is the source of truth for what that request cost. ## Usage-based charges AIWA is gradually moving builds and edits to usage-based charging, where the charge follows the actual work done for your request: planning, building, images and repairs. When usage-based charging is active for your workspace: * AIWA sets aside enough credits before each step. Setting credits aside is not a charge. * When the step finishes, the real charge is taken and anything left over is returned. * The receipt in the chat shows what was charged, and the total for the build so far. * A receipt can briefly show as **settling usage** while the final figure is confirmed. If the next step can't set aside enough credits, the build pauses so you can top up and carry on. ## Monthly credits and top-ups Your plan gives you a monthly allowance. Credits you buy as a top-up are kept separately. * Monthly credits reset to your plan's full amount at the start of each cycle. * Top-up credits never expire. * AIWA spends monthly credits first, then top-ups. See [Monthly vs top-up credits](/billing/monthly-vs-topup). ## The one-time overdraft Every workspace gets a one-time cushion of **20 credits** it can go below zero into, so a build that runs out of credits halfway can still finish instead of stopping. If you use it, your balance shows as negative. The amount you overdrew comes off your next monthly allowance. The cushion does not refill once it has been used. ## Seeing your balance Your balance is shown in the builder while you work, and in **Settings → Plan & usage**, together with when your monthly credits reset. AIWA Credit Balance Agency workspaces can also see spending broken down by person, project and type in the [agency console](/agency/spend-limits). ## When you run out When your balance is too low for the next request, AIWA tells you before it starts. You can: * Top up straight away on Solo or Agency * Upgrade to a larger plan * Wait for your monthly credits to reset Your projects and published sites are not affected by your credit balance. ## Next: Credit Costs See what each AIWA action costs. # Monthly Credits vs Top-Up Credits Source: https://docs.aiwa.codes/billing/monthly-vs-topup How AIWA monthly plan credits and purchased top-up credits behave: when monthly credits reset, why top-ups never expire, and which credits are used first. AIWA keeps two kinds of credits: * **Monthly credits** come with your plan and reset every cycle. * **Top-up credits** are credits you buy. They never expire. ## The simple version | | Monthly credits | Top-up credits | | - | - | - | | Where they come from | Your plan | A purchase | | How many | 80, 200 or 1,000 depending on plan | As many as you buy | | Reset each cycle | Yes, back to your plan's amount | No | | Expire | Unused ones don't carry over | Never | | Used first | Yes | After monthly credits run out | | Available on | Every plan | Solo and Agency | ## Monthly credits Every plan includes a monthly allowance: | Plan | Monthly credits | | - | - | | Launchpad | 80 | | Solo | 200 | | Agency | 1,000 | | Enterprise | Custom | At the start of each cycle, your monthly balance is **reset to your plan's full amount**. Unused monthly credits do not carry over to the next cycle. ```text theme={null} Agency plan, 1,000 credits a month Cycle 1: use 700 → 300 left Cycle 2 starts → balance back to 1,000 (not 1,300) ``` On an annual plan you pay for the year, but your credits still arrive every month. ## Top-up credits Top-ups are credits you buy on Solo or Agency, at \$0.10 each. See [Topping up](/billing/topping-up). Top-up credits: * Are added to your balance as soon as payment completes * Don't expire and aren't affected by the monthly reset * Stay in your account if you downgrade or cancel ## Which credits are used first? AIWA spends your **monthly credits first**. Top-ups are only used once your monthly credits for the cycle are gone. ```text theme={null} Monthly: 50 Top-up: 300 Request costs 80 → 50 from monthly → 30 from top-up Monthly: 0 Top-up: 270 ``` This way, the credits that would be lost at the reset are always used before the ones you keep. ## If you overdrew If a build used your [one-time overdraft](/billing/how-credits-work#the-one-time-overdraft), the amount you went below zero comes off your next monthly allowance. For example, if you overdrew by 9 on Launchpad, your next cycle starts at 71 instead of 80. ## Busy months and quiet months **Quiet month:** your monthly credits reset anyway, but your top-ups stay. **Busy month:** once your monthly credits are used, top-ups keep you going. If you're regularly topping up, a larger plan may be better value; compare in **Settings → Plan & usage**. ## Your projects don't depend on your balance Credits pay for AI work. Your projects, versions and published sites stay where they are whatever your balance is. ## Quick reference | Question | Answer | | - | - | | Do monthly credits roll over? | No, they reset to your plan's amount each cycle | | Do top-up credits expire? | No | | Which are used first? | Monthly credits | | Can I top up on Launchpad? | No, top-ups need Solo or Agency | | Do I lose top-ups if I cancel? | No | ## Next: Topping Up Buy more credits when you need them. # What is included in my AIWA plan Source: https://docs.aiwa.codes/billing/plan-inclusions The full list of what each AIWA plan includes: credits, projects, seats, building, publishing, domains, export, collaboration and mobile. This page lists what each plan includes, area by area. For prices and who each plan is for, see [Plans overview](/billing/plans). ✓ = included · – = not included ## Credits and limits | | Launchpad | Solo | Agency | Enterprise | | - | - | - | - | - | | Price | Free | \$20/mo or \$210/yr | \$149/mo or \$1,565/yr | Custom | | Monthly credits | 80 | 200 | 1,000 | Custom | | Projects | 5 | 100 | Unlimited | Unlimited | | Team seats (including owner) | 3 | 1 | 15 | Unlimited | | Extra editor seats | – | – | \$19/month each | Custom | | Top-ups at \$0.10/credit | – | ✓ | ✓ | ✓ | | Attachments per message | 5 | 10 | 10 | 10 | | AI-generated images per project | 2 | 10 | 25 | 25 | | Stock photos per project | 7 | 20 | 50 | 50 | Image allowances are per project, across all of its builds. Your logo doesn't count towards them, and when a project reaches its limit AIWA uses free stock photos instead. ## Building | | Launchpad | Solo | Agency | Enterprise | | - | - | - | - | - | | Build, Plan, Explore and Debug modes | ✓ | ✓ | ✓ | ✓ | | AIWA Min | ✓ | ✓ | ✓ | ✓ | | AIWA Max | – | ✓ | ✓ | ✓ | | Brief (1 free per day) | ✓ | ✓ | ✓ | ✓ | | Connectors | ✓ | ✓ | ✓ | ✓ | | Version history and restore | ✓ | ✓ | ✓ | ✓ | | Remix and share links | ✓ | ✓ | ✓ | ✓ | Paid plans start new requests on AIWA Max. You can switch to Min whenever you like. ## Publishing and domains | | Launchpad | Solo | Agency | Enterprise | | - | - | - | - | - | | Publish to a live URL | ✓ | ✓ | ✓ | ✓ | | No "Made with AIWA" badge | – | ✓ | ✓ | ✓ | | Custom domains | – | ✓ | ✓ | ✓ | | Site analytics | – | ✓ | ✓ | ✓ | | Only your workspace, or selected members, can view a site | – | – | ✓ | ✓ | ## Code | | Launchpad | Solo | Agency | Enterprise | | - | - | - | - | - | | Code export | – | ✓ | ✓ | ✓ | | GitHub sync | – | ✓ | ✓ | ✓ | ## Team and clients | | Launchpad | Solo | Agency | Enterprise | | - | - | - | - | - | | Invite teammates who can view | ✓ | – | ✓ | ✓ | | Invite teammates who can edit | – | – | ✓ | ✓ | | Invite clients to review and comment | – | – | ✓ | ✓ | | Agency console | – | – | ✓ | ✓ | | Client portal and hand-off | – | – | ✓ | ✓ | | Build from Telegram | – | – | ✓ | ✓ | Clients you invite never use a team seat. ## Mobile | | Launchpad | Solo | Agency | Enterprise | | - | - | - | - | - | | Mobile readiness scan | ✓ | ✓ | ✓ | ✓ | | Android APK | – | – | ✓ | ✓ | | Google Play release kit | – | – | ✓ | ✓ | | App Store submission kit | – | – | ✓ | ✓ | | Download the mobile source project | – | – | ✓ | ✓ | Mobile builds and kits unlock once your project scores 80 or more on the readiness scan. Each one also has a credit price; see [Credit costs](/billing/credit-costs). ## Enterprise extras Enterprise adds custom credit volumes, unlimited seats and options such as SSO/SAML, an audit log, custom contracts and onboarding, agreed with our team. ## Next: White Label Sell AIWA to your own customers under your own brand. # Plans Overview Source: https://docs.aiwa.codes/billing/plans Compare AIWA's Launchpad, Solo, Agency and Enterprise plans: prices, monthly credits, project limits, seats and who each plan is for. AIWA has a plan for everyone, from someone building their first app to an agency delivering projects for many clients. Every plan gives you the full building experience. Paid plans add more credits, more projects, your own domain, code export, team and client collaboration, and mobile app kits. **Start free. Upgrade when your products and your team need more.** AIWA Pricing Plans ## AIWA plans at a glance | Plan | Price | Credits each month | Projects | Team seats | | - | - | - | - | - | | Launchpad | Free | 80 | 5 | 3 (viewers only) | | Solo | \$20/month or \$210/year | 200 | 100 | 1 | | Agency | \$149/month or \$1,565/year | 1,000 | Unlimited | 15 | | Enterprise | Talk to us | Custom | Unlimited | Unlimited | Team seats include the owner. Clients you invite to review a project are free and never use a seat. The prices and allowances in AIWA's Billing screen are always the source of truth for your account. ## Launchpad **Free** Launchpad lets you build and publish a real project before you pay anything. * 80 credits every month, enough for a complete first build and a few edits * Up to 5 projects * Live preview and publishing to a live URL * Share links, remix and version history * Invite up to 2 people to view your work * A small "Made with AIWA" badge on published sites Launchpad runs on **AIWA Min**. Top-ups are not available on Launchpad; upgrade to Solo when you need more. ## Solo **\$20/month**, or **\$210/year** billed annually Solo is for founders, freelancers and anyone building products for themselves. * 200 credits every month * Up to 100 projects * Everything in Launchpad * **AIWA Max** for deeper reasoning on hard requests * No AIWA badge on your published sites * Custom domains * Site analytics on published sites * Code export and GitHub sync * Top-ups at \$0.10 per credit Solo is a one-person plan. To invite teammates who can edit, or to invite clients, you need Agency. ## Agency **\$149/month**, or **\$1,565/year** billed annually Agency is for people who build for other people: web agencies, studios, consultants and freelancers with several clients. * 1,000 credits every month * Unlimited projects * Everything in Solo * Up to 15 team seats, with extra editor seats at \$19/month each * Invite clients to review, comment on and sign off their project * The [agency console](/agency/console-overview) for clients, team, usage and branding * Control who can see a published site, not only public * Android APK, Google Play kit and App Store kit for mobile apps * Larger image allowances per project * Build and manage projects from [Telegram](/agency/telegram) ```text theme={null} AGENCY ↓ AIWA ↓ ┌─────────┬─────────┬─────────┐ ↓ ↓ ↓ ↓ Client A Client B Client C Client D ``` ## Enterprise **Talk to us** Enterprise is for organizations that need AIWA at a larger scale, or that need extra security, governance or commercial terms. * Custom credit volumes * Unlimited seats, clients and projects * Everything in Agency * Options such as SSO/SAML and an audit log, custom contracts and onboarding, agreed with our team Book a call from the Enterprise card on the pricing table. ## White Label If you want to sell AIWA to your own customers under your own brand, domain and prices, see the [White Label program](/white-label/overview). It is a separate partner plan, not an upgrade of Agency. ## Monthly vs annual billing Solo and Agency can be paid monthly or annually. An annual plan costs **10.5 months' worth** of the monthly price, so you save one and a half months: | Plan | Monthly | Annual | You save | | - | - | - | - | | Solo | \$20 | \$210 | \$30 a year | | Agency | \$149 | \$1,565 | \$223 a year | You pay for the year up front, but **your credits still arrive every month**. An annual Agency plan gives you 1,000 credits each month, not 12,000 at once. ## Lifetime deals AIWA no longer sells lifetime deals. If you bought one earlier, including through AppSumo, your account keeps the terms you bought. ## Which plan should I choose? **Choose Launchpad if** you're discovering AIWA and want to build your first project. **Choose Solo if** you're building for yourself and want your own domain, no badge, code export and more credits. **Choose Agency if** you work with clients or a team, want mobile app kits, or build at higher volume. **Talk to us about Enterprise if** you need custom volumes, SSO or custom contracts. You can start free and upgrade at any time. Your projects come with you. ## Next: How Credits Work Understand how AIWA credits are used as you build. # Topping Up Credits Source: https://docs.aiwa.codes/billing/topping-up Buy extra AIWA credits at $0.10 each on Solo or Agency. Choose a budget from $5 to $2,000; top-up credits never expire. When you need more credits than your plan includes, you can buy a top-up without changing your plan. **Top-up credits cost \$0.10 each, and they never expire.** ## Who can top up Top-ups are available on **Solo** and **Agency**. On Launchpad, [upgrade to Solo](/billing/upgrading-downgrading) to get more credits. Only the workspace owner can buy credits. ## Top-up pricing You choose a whole-dollar budget from **\$5 to \$2,000**, and you get 10 credits for every dollar. | You pay | You get | | - | - | | \$5 | 50 credits | | \$20 | 200 credits | | \$50 | 500 credits | | \$100 | 1,000 credits | | \$2,000 | 20,000 credits | The \$5, \$20 and \$50 amounts are one-click options. Choose **Custom** for any other whole-dollar amount. ## How to top up Go to **Settings → Plan & usage**, or use **Add credits** when AIWA tells you your balance is low. Pick \$5, \$20 or \$50, or choose **Custom** and enter a whole-dollar amount. Complete payment in the secure checkout. The credits are added to your balance as soon as payment completes. AIWA Credits Topup ## Top-up credits never expire Top-up credits are kept separately from your monthly allowance. They aren't touched by the monthly reset, and they stay in your account if you downgrade or cancel. ## Your plan credits are used first AIWA always spends your monthly plan credits before your top-up credits. See [Monthly vs top-up credits](/billing/monthly-vs-topup). ## Top up or upgrade? | Situation | Better choice | | - | - | | A one-off busy week | Top up | | You keep running out every month | Upgrade | | You need features from a bigger plan | Upgrade | Upgrading also gives you plan features, such as team seats and client review on Agency. When you top up on Solo, AIWA shows you how Agency compares per credit, so you can decide. ## You don't need credits to publish Publishing, hosting and connecting a domain don't use credits. Your published apps stay online whatever your balance. ## Refunds A top-up you haven't used any of can be refunded within 7 days of purchase. See [Cancellation and refunds](/billing/cancellation-refunds). ## Next: Upgrading & Downgrading Learn how to change your AIWA plan. # Upgrading and downgrading your AIWA plan Source: https://docs.aiwa.codes/billing/upgrading-downgrading Change your AIWA plan at any time. Learn how upgrades are prorated, what happens to your credits, and what changes when you downgrade. You can change your AIWA plan whenever your needs change. Only the workspace owner can change the plan. ## The simple version ```text theme={null} UPGRADE ↓ Pay the prorated difference now ↓ New plan and its full monthly credits straight away DOWNGRADE ↓ Done in the billing portal ↓ Fewer features and credits; your projects stay ``` ## Upgrading your plan Go to **Settings → Plan & usage** and choose **Upgrade** (or **Change plan** if you're already on a paid plan). Choose Solo or Agency, monthly or annual. AIWA shows exactly what you'll pay today, and what the plan costs on repeat, before you confirm. If you already pay for a plan, an upgrade is **prorated**: you pay the difference for the rest of the current period, charged immediately. ## What happens to my credits when I upgrade? As soon as the upgrade is paid: * Your monthly balance is set to the **new plan's full monthly allowance**. Moving from Solo to Agency gives you 1,000 monthly credits straight away. * Your **top-up credits are untouched**. * Any overdraft you used is taken off the new allowance. If the payment needs extra confirmation from your bank, or is declined, the upgrade waits until it's paid. ## Moving from monthly to annual Switching the same plan from monthly to annual counts as an upgrade and is done in **Change plan**. You save one and a half months a year. ## Downgrading your plan Downgrades, including annual to monthly, are done in the secure billing portal: Go to **Settings → Plan & usage** and choose **Manage billing**. Choose the plan you want, and check when the change takes effect. ## What changes when you downgrade You keep: * All your projects, versions and published sites * Your top-up credits * Your code, data and connectors You lose the features of the higher plan. For example, moving from **Agency to Solo**: * You can no longer invite editors or clients. People already on your team keep their access. * Android, Google Play and App Store kits are no longer available for new builds. Kits you already built stay downloadable. * Your monthly allowance becomes 200 credits from your next cycle. Moving from **Solo to Launchpad**: * Your published sites show the "Made with AIWA" badge again. * Custom domains, code export, GitHub sync and AIWA Max are no longer available. * Your monthly allowance becomes 80 credits. ## Project limits after a downgrade Each plan has a project limit: 5 on Launchpad, 100 on Solo and unlimited on Agency. If you downgrade with more projects than the new limit, **nothing is deleted**. You keep every project, but you can't create new ones until you're back under the limit or upgrade again. ## Upgrading again later You can upgrade again at any time. Your projects are exactly where you left them, and the higher plan's features come back as soon as the upgrade is paid. ## Quick reference | Question | Answer | | - | - | | Who can change the plan? | The workspace owner | | Are upgrades prorated? | Yes, charged immediately | | Do I get the new credits right away? | Yes, once the upgrade is paid | | Where do I downgrade or cancel? | Manage billing (billing portal) | | Do I keep my projects? | Yes, always | | Do I keep my top-ups? | Yes | ## Next: Failed Payments What happens if a payment doesn't go through, and how to fix it. # Build Mode Source: https://docs.aiwa.codes/building/build-mode Use Build Mode to have AIWA create pages, features, and functionality directly, from your first prompt to ongoing product changes. Build Mode is where AIWA turns your instructions into changes inside your application. Use Build Mode when you're ready for AIWA to create, modify, or implement something. You can use it to build an entire application from your first prompt or make a small change to a product you've been working on for months. If you know what you want AIWA to create or change, Build Mode is usually the place to start. ## What Build Mode does When you submit a request in Build Mode, AIWA works directly on your project. Depending on your request, AIWA may: * Create new pages * Build components * Change existing designs * Add application features * Create forms and workflows * Add database functionality * Implement authentication * Create APIs and server-side logic * Connect external services * Modify existing functionality * Fix implementation issues You describe the outcome you want, and AIWA handles the implementation required to achieve it. ## Starting a build Select **Build** from the mode selector. AIWA Four Modes Then describe what you want AIWA to do. For example: > Add a Projects page to the construction website. Display completed projects in a responsive grid with a large project image, project name, location, project type, and completion year. Add filters for Residential, Commercial, and Infrastructure. Submit your request and AIWA will begin working on the project. ## Building a new application You can use Build Mode from the very beginning of a project. For example: > Build a modern booking application for a beauty salon. Customers should be able to browse services, choose a stylist, select an available date and time, and make a booking. Staff should have a dashboard for viewing and managing appointments. AIWA can use this request to begin creating the application. For straightforward products, you may not need to create a detailed plan first. For more complex products, consider using Plan Mode before starting the build. ## Building from an approved plan Build Mode becomes especially powerful when you've already worked through a complex feature in Plan Mode. The workflow becomes: Describe the feature and let AIWA determine what needs to be built. Review the specification and correct anything that isn't right. Confirm the direction once you're satisfied with the plan. Move to Build Mode and implement the approved specification. This separates product decisions from implementation. For complex work, that can make the development process much easier to manage. ## Watch AIWA work Once a build starts, AIWA begins making the changes required by your request. Depending on the size of the task, this may involve several parts of your application. AIWA may create or modify: **Frontend** Pages, layouts, components, forms, navigation, responsive interfaces, and other user-facing elements. **Backend** Application logic, APIs, database interactions, authentication, and server-side functionality. **Integrations** Connections to external services required by the feature. As AIWA works, you can follow the progress from the project workspace. AIWA Building ## Review the result Once the build completes, inspect what AIWA created. Don't only look at whether the page appears. Interact with the application. For example, if AIWA built a lead management feature: * Create a lead * Edit the lead * Search for it * Apply filters * Refresh the application * Check whether the data persists * Try the experience on mobile * Test empty and error states where relevant The goal is to review the feature as a user, not just as a screenshot. ## Continue with follow-up prompts You don't need to get everything perfect in one build. Continue talking to AIWA. For example, after building a dashboard: > Make the upcoming tasks section more prominent and move recent activity below the project list. Then: > Add a date range filter to the dashboard metrics. Then: > Make the dashboard cards stack into a single column on small mobile screens. Each instruction evolves the existing application. ## Tell AIWA what should stay unchanged When you're modifying an application, it can be useful to explicitly protect parts that already work. For example: > Redesign the hero section to make it feel more premium. Keep the existing navigation, brand colors, page content, and all sections below the hero unchanged. Or: > Add filtering to the customer table. Don't change the existing customer creation or editing functionality. This helps define the scope of the build. The more mature your application becomes, the more useful clear boundaries become. Tell AIWA both **what should change** and, when important, **what should remain unchanged**. ## Build features in logical increments You don't have to ask AIWA to implement an entire complex product in one enormous build. Breaking major work into logical stages gives you opportunities to review each part. For example, when building a marketplace: **Build 1: Accounts** > Add customer and seller authentication with separate onboarding experiences. **Build 2: Listings** > Allow sellers to create, edit, publish, and archive product listings. **Build 3: Discovery** > Build the marketplace browsing experience with search, categories, filters, and product detail pages. **Build 4: Transactions** > Add the purchasing workflow and payment integration. **Build 5: Seller dashboard** > Create a seller dashboard for managing listings, orders, and revenue. This makes it easier to test the product as it grows. ## Build Mode can work with your existing application Build Mode isn't only for new projects. You can open an existing AIWA project and continue from where you stopped. For example: > Add a notification system to the existing application. Don't redesign the current dashboard. Add a notification icon to the existing header and allow users to mark notifications as read. AIWA works within the context of your existing project. This is part of what makes AIWA an ongoing product development environment rather than a one-time application generator. ## When to use Plan instead Build Mode is best when the direction is clear. Switch to Plan Mode first when you're making a change that requires significant decisions. For example: > Convert this application into a multi-tenant SaaS where companies can create separate workspaces, invite users, assign roles, and maintain completely isolated data. That's not just a UI change. It affects authentication, authorization, database architecture, application state, APIs, and potentially existing data. Planning first gives AIWA an opportunity to reason through those dependencies. A simple rule: **If you know what needs to change, Build. If you need to figure out how a major change should work, Plan first.** ## Build Mode vs Plan Mode | | Build Mode | Plan Mode | | - | - | - | | Creates or modifies your app | Yes | No | | Best for implementation | Yes | No | | Best for quick changes | Yes | Usually not | | Creates a detailed specification first | Not necessarily | Yes | | Best for major architectural decisions | After planning | Yes | | Useful throughout a project | Yes | When needed | They are designed to work together rather than compete with each other. ## What if the build isn't right? You don't have to start over. First, tell AIWA specifically what isn't correct. Instead of: > This isn't right. Try: > The new customer form is correct, but after creating a customer the modal stays open and the customer doesn't appear in the table until I refresh the page. Keep the form design unchanged and fix those two issues. If something is genuinely broken and requires investigation, switch to Debug Mode. We'll cover diagnosing and fixing application problems in **Fixing Errors**. ## A good Build Mode habit For meaningful features, use this loop: **Request → Build → Test → Refine** Don't judge a build only by appearance. Ask: * Does it look right? * Does it behave correctly? * Does the data persist? * Does it work for the intended user? * Does it work on different screen sizes? * Did anything that previously worked break? Then give AIWA your next instruction. ## Build continuously Your application doesn't have to be finished after the first generation. You might begin with: > Build a client portal for my agency. Then over time add: > Client onboarding. > Project management. > Invoice tracking. > Team permissions. > Automated email updates. > Analytics. The application evolves through successive builds as your needs change. That's the core idea behind working with AIWA as your AI product team. ## Next: AIWA Min vs AIWA Max Now that you know when to use Build and Plan, the next decision is how much reasoning your task requires. Next, we'll look at AIWA Min vs AIWA Max: when to prioritize speed and when to use deeper reasoning. Choose fast reasoning or deep reasoning for each task. # Working with Existing Projects Source: https://docs.aiwa.codes/building/existing-projects Continue developing an existing AIWA project or bring outside code into AIWA safely without rebuilding features you already have. You don't always have to start with a blank idea. Sometimes you already have an application, website, design, or codebase and want to continue developing it with AIWA. How you work with an existing project depends on where that project currently lives and how much of it AIWA can access. This guide explains the best way to approach existing applications without accidentally rebuilding functionality you already have. ## Existing AIWA projects The simplest case is an application you've already created with AIWA. Open the existing project from your AIWA dashboard and continue the conversation. Because you're working inside the same project, AIWA has access to the existing application context. For example: > Add a customer portal to this application where customers can see their projects, invoices, files, and recent updates. Or: > Redesign the dashboard while preserving the existing authentication, database, APIs, and customer management functionality. You don't need to create another project just because you're adding a major feature. If you're evolving the same product, continue working inside the existing AIWA project whenever possible. ## Start by understanding what already exists When working with an established application, don't immediately ask AIWA to make major changes. First, make sure AIWA understands the current product. For significant work, Explore Mode is useful. For example: > Analyze the existing application before changing anything. Explain the current architecture, main pages, data model, authentication flow, major features, integrations, and anything important I should understand before we continue development. This gives you an opportunity to confirm that AIWA understands the project correctly. ## Then explain what you want to change Once the existing application is understood, describe the desired outcome. For example: > We want to add subscriptions to this application. Users should have Free, Pro, and Business plans with different feature limits. For a focused change, you may be able to move directly into Build Mode. For a major change, use Plan Mode first. > Create a plan for introducing subscriptions without changing the existing authentication or customer data. Include Stripe checkout, subscription state, feature entitlements, upgrades, downgrades, cancellations, webhooks, and billing portal access. This separates understanding the existing system from modifying it. ## Preserve existing functionality One of the most important principles when working with an existing application is telling AIWA what must not change. Suppose your existing application already has working authentication. Instead of: > Add team workspaces. Try: > Add team workspaces to the existing application. Preserve the current Google and email/password authentication. Don't replace the existing authentication system unless the new workspace architecture absolutely requires a change. Or: > Redesign the dashboard. Preserve all existing API behavior, database functionality, filters, and user permissions. This request is only about presentation and information hierarchy. The more mature the application, the more important these boundaries become. ## Work in stages Large existing applications should usually be changed incrementally. Imagine you have an existing single-user CRM and want to turn it into a platform for agencies. Trying to do everything in one instruction creates a large change surface. A better workflow might be: Ask AIWA to understand the existing CRM, its data model, authentication, and important workflows. Create a specification for introducing agency workspaces, team members, roles, and data isolation. Implement the approved architecture. Verify existing CRM functionality still works within the new workspace structure. Add invitations, team management, permissions, billing, or other agency features in logical stages. This gives you opportunities to validate the application throughout the migration. ## Existing code outside AIWA You may already have an application that was built using another development environment or AI coding tool. For example, your project might currently exist: * On your computer * In a Git repository * On another development platform * On a VPS * On another hosting provider The first question is whether the existing project can currently be brought into an AIWA project in a supported way. Don't assume that a live website URL gives AIWA access to the application's source code, database, server configuration, or backend. A deployed application and its underlying codebase are not the same thing. ## A live URL is not the source code If you have: ```text theme={null} https://example.com ``` AIWA may be able to understand what the public-facing application looks like when appropriate, but the URL itself does not automatically provide access to everything behind it. A production application may include: * Frontend source code * Backend code * Database schemas * Environment variables * Authentication configuration * APIs * Server configuration * Private business logic Much of this isn't exposed through the public website. If you want to continue developing an existing product, access to the actual project files is much more useful than simply providing the production URL. ## GitHub and external repositories If your application is stored in GitHub or another Git-based workflow, the ideal development workflow is to work from the actual repository rather than trying to reconstruct the application from its live website. However, GitHub export and GitHub import are different capabilities. AIWA can export supported projects to GitHub, allowing you to take your AIWA-generated code into a traditional development workflow. If direct repository import is available in your AIWA account, follow the import options shown in the project creation experience. If you don't see an option to import an existing repository, don't create a blank project and assume AIWA automatically has access to your GitHub code. ## Moving a project from another builder You may have originally created your application using another AI development platform. In that case, the safest migration approach is to work from the application's actual source code whenever possible. Before migrating, identify: * The frontend framework * Backend architecture * Database * Authentication provider * Environment variables * External integrations * File storage * Deployment environment The visible UI is only one part of an application. A successful migration needs to account for the systems behind it as well. ## Don't rebuild blindly Suppose you have a working SaaS application and want to continue it with AIWA. Avoid starting with: > Rebuild this application. Instead, first understand what you're bringing over. A better objective is: > Preserve the existing product behavior and continue development from the current application rather than recreating features unnecessarily. If a migration requires replacing part of the existing architecture, that should be an intentional decision rather than an accidental consequence of rebuilding. ## Working with an existing design Sometimes you don't have an existing codebase. You have a design or reference you want AIWA to turn into a working product. In that situation, explain what you're providing and what you want AIWA to create. For example: > Use this design as the visual direction for the application. Recreate the layout and responsive experience, then implement the required functionality behind it. Also describe any behavior that isn't obvious from the visual reference. A screenshot can show what a dashboard looks like. It can't necessarily explain: * Where its data comes from * What permissions apply * What happens when buttons are clicked * How filters behave * How users authenticate Give AIWA that product context separately. ## Continuing development outside AIWA AIWA also gives you flexibility when you want to take your project elsewhere. For supported projects, you can export your application code or move it into a GitHub-based development workflow. From there, your team can manage its own: * Repository * Deployment workflow * Infrastructure * VPS or cloud environment * Development process This is useful for teams that want AIWA to accelerate product development while retaining control over their code and infrastructure. AIWA Github Integration ## Hosting and development are different AIWA can host published AIWA projects for you. But hosting and development are separate concepts. You might: **Build with AIWA → Host with AIWA** or, where your project and plan support it: **Build with AIWA → Export code → Host elsewhere** For example, an agency may export a project and deploy it to its own VPS infrastructure. Once the project is managed outside AIWA, responsibility for that external deployment environment belongs to whoever operates it. ## Before making major changes When continuing an existing application, use this checklist: * Does AIWA understand what already exists? * Have I identified functionality that must be preserved? * Is the requested change focused or architectural? * Should I use Explore before making changes? * Should I use Plan Mode? * Are there existing integrations that must remain intact? * Could the change affect existing data? * Could it affect authentication or permissions? * Do I have a way to test the existing workflows afterward? The goal isn't simply to make the new feature work. The goal is to make the new feature work without unnecessarily breaking the product you already have. ## A recommended workflow For significant existing applications, use: **Understand → Protect → Plan → Build → Test** **Understand** Make sure AIWA understands the current application. **Protect** Identify existing functionality that must remain unchanged. **Plan** Think through major changes before implementation. **Build** Implement the approved change. **Test** Test both the new functionality and the existing workflows it could affect. This is especially important as your application becomes larger and more valuable. ## Your existing product can keep evolving AIWA isn't only for turning new ideas into first versions. The larger opportunity is continuing to develop software after that first version exists. You can use AIWA to: * Improve existing experiences * Add features * Extend workflows * Modernize interfaces * Introduce integrations * Debug problems * Restructure parts of a product * Prepare larger changes through planning * Continue evolving an AIWA application over time The objective is not always to start over. It's to keep moving the product forward. ## You've completed Building with AIWA You now know how to: * Write effective prompts * Choose between Build, Plan, Explore, and Debug * Plan complex work before implementation * Build and modify applications * Choose between AIWA Min and AIWA Max * Work with Project Memory * Iterate on your application * Debug problems * Approach existing projects safely Together, these concepts form the core AIWA development workflow. ## Next: What AIWA Builds For You Until now, we've focused primarily on how you work with AIWA. Next, we'll go underneath the application. We'll look at what AIWA can set up for you, including database, authentication, forms, uploads, APIs, server-side functionality, and project data, without requiring you to manually assemble the entire backend infrastructure. See what AIWA sets up automatically, from database to auth to APIs. # Fixing Errors Source: https://docs.aiwa.codes/building/fixing-errors Use Debug Mode to describe broken behavior, share errors, and let AIWA find the root cause without rebuilding working features. Errors can happen while building software. A feature may not behave as expected. A form may stop submitting. An integration may fail. A page may not load. Or AIWA may encounter an error while implementing a change. When that happens, you don't necessarily need to understand the underlying code yourself. Use **Debug Mode** to give AIWA the problem and let your AI product team investigate what went wrong. > **Describe what happened. Let AIWA investigate the cause. Fix the underlying problem.** ## When to use Debug Mode Use Debug Mode when something that should work doesn't. For example: > Users can create an account, but after signing in they're redirected back to the login page. Or: > When I click Create Workspace, nothing happens and the browser console shows an error. Or: > Stripe checkout completes successfully, but the user's subscription isn't updated in the dashboard. These are different from normal Build requests. You're not asking AIWA to create something new. You're asking it to investigate existing behavior and determine why it isn't working correctly. ## Start with what you can observe You don't need to diagnose the problem before talking to AIWA. Start by describing what you see. For example: > The contact form isn't working. That's enough to begin, but you can make the request more useful by adding context: > The contact form displays correctly, but when I click Submit nothing happens. The form should save the enquiry and show a success message. Debug the complete submission flow and fix the underlying issue. The second prompt gives AIWA three useful pieces of information: **What exists:** The contact form. **What should happen:** The enquiry should be saved and a success message displayed. **What actually happens:** Nothing happens after clicking Submit. ## A simple debugging prompt formula When possible, structure your debugging request around: **Expected behavior → Actual behavior → Error → Reproduction steps** For example: > When a user clicks Create Workspace, a new workspace should be created and the user should be redirected to its dashboard. Instead, the button enters a loading state and nothing else happens. The browser console shows a 500 error. This happens every time I create a workspace. Debug the complete workspace creation flow and fix the root cause. You don't need all four pieces every time. Give AIWA whatever information you have. ## Use Debug Mode Select **Debug** from the AIWA mode selector. AIWA Four Modes Then describe the problem. AIWA can investigate the application and determine what may be causing the issue. Depending on the problem, this can involve checking areas such as: * Frontend behavior * Application state * API requests * Server-side logic * Authentication * Database operations * Integrations * Configuration * Build behavior The goal is not simply to hide the visible error. The goal is to identify and correct the underlying problem. ## Give AIWA the error message If you have an error message, include it. For example: > Failed to create workspace: 500 Internal Server Error Then explain when it happens: > This error appears every time I click Create Workspace. Debug the workspace creation flow and determine why the API is returning 500. You don't need to understand what the error means before sharing it. AIWA can use it as evidence while investigating the problem. Copy the complete error when possible. A specific error message is usually more useful than saying "it doesn't work." ## Share reproduction steps For bugs that only happen during a particular workflow, tell AIWA how to reproduce them. For example: ```text theme={null} 1. Sign in 2. Open Settings 3. Go to Workspace 4. Click Create Workspace 5. Enter a workspace name 6. Click Create 7. The button loads indefinitely ``` Then explain what should happen instead. > The workspace should be created and opened automatically. Reproduction steps help AIWA understand exactly where the failure occurs. ## Tell AIWA what changed If the problem started after a recent change, mention it. For example: > This worked before we changed the authentication flow. Since that change, newly registered users can't access the dashboard. Debug the issue without removing the new authentication system. Or: > File uploads stopped working after we added the new profile page. Existing uploads worked before this change. This gives AIWA another useful clue while investigating. ## Don't ask AIWA to rebuild everything immediately When something breaks, it can be tempting to say: > Rebuild the entire feature. That isn't always the best first response. The issue may be caused by one incorrect request, database operation, permission check, or state update. Instead, start with: > Investigate why this feature is failing, identify the root cause, and fix it without changing unrelated functionality. This encourages a focused repair. If the rest of the feature is working correctly, explicitly tell AIWA to preserve it while debugging the broken behavior. ## Protect working functionality Suppose users can create and edit leads correctly, but deleting a lead fails. Instead of: > Fix the Leads feature. Try: > Creating, editing, searching, and filtering leads all work correctly. Only deletion is failing. Debug the delete flow and fix it without changing the existing lead creation, editing, search, or filtering behavior. This defines the boundary of the repair. The same principle applies to design. > Fix the form submission issue. Don't redesign the form or change its fields. ## Test the fix Once AIWA completes the repair, reproduce the original problem again. If the issue was: > Creating a workspace fails. Test: Follow the same steps that originally caused the error. Confirm that the expected behavior now occurs. Where relevant, refresh the application and make sure the result persists. Make sure the fix didn't break nearby functionality. A bug isn't fixed simply because the error message disappeared. The expected workflow should work correctly. ## If the first fix doesn't work Sometimes the first attempt won't completely solve a problem. Don't start the explanation from scratch. Continue the debugging conversation. For example: > The 500 error is gone, but the workspace still isn't being created. The button now finishes loading and returns to its normal state. Continue debugging from the current implementation and find out why no workspace record is being created. Or: > The subscription now updates correctly after payment, but only after refreshing the dashboard. Fix the state update so the new plan appears immediately after checkout. Each test gives AIWA additional information. Debugging can be iterative too. ## Visual problems vs functional errors Not everything that looks wrong is a software error. For example: > The cards have too much spacing. That's probably a Build request. > The cards disappear completely on mobile. That may be a Debug request. Similarly: > Make the signup form shorter. → Build > Clicking Sign Up produces an error. → Debug A simple distinction is: **I want this to work differently** → Build **This should already work, but it doesn't** → Debug ## When the problem is an integration External services can introduce another layer of debugging. For example: > Stripe checkout opens correctly, but completed payments aren't activating subscriptions. Or: > Emails stopped sending after connecting Resend. Or: > Images appear to upload successfully but don't display afterward. Tell AIWA: * Which integration is involved * What action you're performing * What should happen * What actually happens * Any error message you see Never paste passwords or sensitive secret credentials into normal prompts. Use AIWA's supported connector and secret-management flows for credentials where available. ## When to use AIWA Max Many bugs are focused enough for AIWA Min. For example: > This button links to the wrong page. Min should usually be sufficient. But some bugs involve several interconnected systems. For example: > Google authentication succeeds, but users are sometimes created without a workspace. They can then access the dashboard but API requests fail because no workspace membership exists. That may involve: * Authentication * User creation * Database transactions * Workspace creation * Membership * Authorization * Redirect logic For difficult problems like this, Debug + Max can provide deeper reasoning. A useful rule is: **Focused bug** → Debug + Min **Complex or persistent bug** → Debug + Max ## A strong debugging prompt Here's a reusable template: ```text theme={null} Something is not working correctly in [FEATURE]. Expected behavior: [WHAT SHOULD HAPPEN] Actual behavior: [WHAT HAPPENS INSTEAD] Error: [PASTE ERROR IF AVAILABLE] Steps to reproduce: 1. [STEP] 2. [STEP] 3. [STEP] This started: [AFTER A CHANGE / ALWAYS / UNKNOWN] Debug the complete flow, identify the root cause, and fix the underlying issue. Preserve: [FUNCTIONALITY THAT ALREADY WORKS] ``` You don't have to fill every section. Use whatever information you have. ## Errors are part of building software Even with AI-assisted development, software can fail for many reasons. What changes with AIWA is how you can approach the problem. Instead of needing to understand every layer yourself, you can describe the symptoms and work with your AI product team to investigate them. The debugging loop becomes: **Observe → Describe → Investigate → Fix → Test → Repeat if necessary** ## Need more specific help? Later in these docs, [the Troubleshooting section](/troubleshooting/stuck-generating) provides dedicated guides for common problems, including: * [Project stuck generating](/troubleshooting/stuck-generating) * [Preview not loading](/troubleshooting/preview-wont-load) * [AIWA generation errors](/troubleshooting/generated-error) * [Deployment failures](/troubleshooting/wont-deploy) * [Domain connection problems](/troubleshooting/domain-not-connecting) * [Credit issues](/troubleshooting/credits-disappeared) * [Stripe integration problems](/troubleshooting/stripe-not-working) * [Database problems](/troubleshooting/database-not-working) * [Mobile export errors](/troubleshooting/mobile-export-errors) Those guides are designed around the specific symptom you're experiencing. ## Next: Working with Existing Projects So far, we've focused heavily on applications created and evolved inside AIWA. But you may also have an existing project or codebase you want to continue working with. Next, we'll cover Working with Existing Projects and how to bring existing development work into your AIWA workflow. Bring an existing project into your AIWA workflow. # The Four Modes: Build, Plan, Explore, Debug Source: https://docs.aiwa.codes/building/four-modes Choose the right AIWA mode for each request, from creating features to planning, exploring, and debugging your application confidently. AIWA gives you four modes for working with your AI product team: **Build, Plan, Explore, and Debug.** AIWA Four Modes Each mode changes how AIWA approaches your request. You don't need to use the same mode throughout a project. You can switch modes depending on what you're trying to accomplish. A simple way to think about them is: | Mode | Use it when you want to... | | - | - | | Build | Create or change something | | Plan | Think through something before building | | Explore | Understand your project or investigate possibilities | | Debug | Find and fix something that isn't working | ## Build Mode Build Mode is for taking action. Use Build when you know what you want AIWA to create, modify, or implement. For example: > Add a pricing section with three plans to the homepage. Or: > Create a customer dashboard where users can view their active subscriptions and billing history. AIWA analyzes the request and works on the application. Use Build when you want to: * Create a new application * Add a page * Add a feature * Change an existing feature * Update the design * Connect functionality * Modify application behavior * Implement an approved plan For straightforward requests, Build will often be the mode you use most frequently. ## Plan Mode Plan Mode is for thinking before building. Use Plan when the change is complex enough that you want AIWA to understand the requirements and determine an approach before implementation begins. For example: > Add multi-tenant workspaces to this application. Each company should have separate users, data, roles, and permissions. Instead of immediately changing the application, Plan Mode allows AIWA to think through what needs to happen. A plan may cover areas such as: * Product requirements * User flows * Application structure * Data requirements * Authentication and permissions * Technical implementation * Dependencies * Potential issues You can review the plan before moving into implementation. Use Plan when: * Building a complex application * Adding a major feature * Changing application architecture * Introducing new user roles or permissions * Adding complex workflows * Making changes that affect several parts of the product If a change could significantly affect your existing application, planning it first can help you understand the scope before implementation. ## Explore Mode Explore Mode is for understanding before deciding what to do. Sometimes you don't want AIWA to immediately build or change anything. You may want to understand your application, investigate an idea, evaluate possibilities, or figure out the best approach. For example: > Analyze this application and explain how authentication currently works. Or: > What would we need to change to turn this single-user application into a team-based SaaS product? Or: > Review the current dashboard and suggest ways to improve the user experience. Explore Mode is useful when the outcome of the conversation isn't necessarily code. Use Explore when you want to: * Understand an existing feature * Analyze your application * Explore product ideas * Compare possible approaches * Review existing functionality * Ask questions about your project * Identify opportunities for improvement * Understand the impact of a potential change Think of Explore as talking through the product with your AI product team before deciding what to do next. ## Debug Mode Debug Mode is for investigating problems. Use Debug when something isn't working as expected. Instead of treating the issue as a normal feature request, AIWA focuses on identifying the cause of the problem and determining how to fix it. For example: > Users can submit the signup form, but they're not being redirected to the dashboard after registration. Find out what's causing this and fix it. Or: > The application throws an error whenever I try to create a new workspace. Debug the issue and fix the underlying cause. Debug Mode is useful for problems involving: * Runtime errors * Broken functionality * Failed API requests * Database issues * Authentication problems * Integration errors * Unexpected application behavior * Build errors * Deployment-related problems ### Give AIWA useful debugging context When possible, include: * What you expected to happen * What actually happened * Steps that reproduce the problem * Any error message you received For example: > When I click "Create Workspace," I expect the workspace to be created and the dashboard to open. Instead, nothing happens and the browser console shows a 500 error. Debug the complete flow and fix the underlying problem. The more useful context AIWA has, the easier it is to investigate the issue. ## Choosing the right mode Here's a simple decision guide. **I know what I want created** Use Build. > Add a customer testimonials section. **I know what I want, but it's a major change** Use Plan first. > Add team workspaces, invitations, roles, and workspace-level data isolation. **I'm not sure what I should do yet** Use Explore. > Review my onboarding experience and suggest how we could improve activation. **Something is broken** Use Debug. > Google login redirects back to the login page instead of the dashboard. Find the cause and fix it. ## You can switch modes as you work The four modes aren't separate workflows. They can work together throughout the lifecycle of your product. For example, imagine you want to add subscriptions to your SaaS application. > Review the existing application and tell me what we would need to add subscription billing. Use Explore to understand the problem. > Create a plan for adding three subscription tiers with Stripe, feature access based on plan, and a customer billing portal. Use Plan to structure the implementation. > Implement the approved subscription plan. Use Build to create it. > Subscription checkout works, but after payment the user's account still shows the Free plan. Find and fix the problem. Use Debug when something doesn't behave correctly. This is one of the advantages of treating AIWA as a product team rather than simply a code generator. Different stages of product development require different kinds of thinking. ## Quick reference | If you want AIWA to... | Choose | | - | - | | Build something new | Build | | Modify an existing feature | Build | | Implement a design change | Build | | Think through a complex feature | Plan | | Design an architecture before implementation | Plan | | Explain how something currently works | Explore | | Review your product and suggest improvements | Explore | | Compare different approaches | Explore | | Investigate an error | Debug | | Fix broken functionality | Debug | | Diagnose an integration problem | Debug | There's no penalty for switching modes. Choose the mode that best matches what you need from AIWA at that moment. ## A simple rule to remember If you're unsure which mode to choose, remember: **Build creates. Plan thinks ahead. Explore investigates. Debug fixes.** As you spend more time building with AIWA, choosing a mode will become natural. ## Next: The Brief Before you choose a mode, it helps to know exactly what you're asking for. Next, we'll look at the Brief, where AIWA interviews you about your idea and writes the request for you. Let AIWA ask the right questions before it builds. # Iterating on Your App Source: https://docs.aiwa.codes/building/iterating Evolve your AIWA project with focused follow-up prompts that improve design, functionality, workflows, and user experience over time. Your first build is just the beginning. AIWA is designed for continuous product development. Once your first version is working, you can keep talking to your AI product team to improve the design, add functionality, change workflows, and expand the application over time. You don't need to start over every time your idea changes. **Build → Review → Improve → Repeat** ## Your app is meant to evolve Most successful products aren't built perfectly in one attempt. They evolve. You might begin with: > Build a booking website for a fitness studio. After seeing the first version, you might realize you need customer accounts: > Add customer accounts so members can log in and see their upcoming bookings. Later: > Add monthly memberships with three subscription plans. Then: > Create a member dashboard showing bookings, membership status, payment history, and available classes. You're still building the same product. AIWA helps you evolve it one decision at a time. ## The AIWA iteration loop A useful way to work with AIWA is through a continuous development loop. Create the first version of a feature or product. Use the application and see how it actually looks and behaves. Decide what should be improved, changed, removed, or added. Tell AIWA what you want to change. Review the new version and make sure the change works as expected. Continue evolving the application as your needs change. You can repeat this process throughout the life of your product. ## Start by using what AIWA built After AIWA completes a feature, interact with it before immediately asking for more changes. If AIWA creates a CRM, for example: * Create a lead. * Edit the lead. * Search for it. * Change its status. * Create a follow-up. * Refresh the page. * Try it on mobile. This can reveal things that aren't obvious from simply looking at the interface. You might discover: * An important action is difficult to find * A workflow requires too many steps * Information is missing * A mobile layout needs improvement * A feature behaves differently than expected * Another feature would make the workflow much better Those observations become your next prompts. ## Iterate on design You can ask AIWA to improve specific parts of your application's visual experience. Instead of: > Make it look better. Try: > The dashboard feels visually flat. Improve the information hierarchy. Make the primary KPIs more prominent, reduce the visual weight of secondary information, and add more spacing between the major sections. Keep the existing functionality unchanged. Or: > The hero section has too much text above the fold. Shorten the supporting copy, make the headline more prominent, and give the primary CTA more visual emphasis. Keep the existing navigation and brand colors. Specific feedback gives AIWA a clearer problem to solve. ## Iterate on functionality You can also expand existing features. Suppose your CRM already has a Leads page. Your first version might allow users to create and edit leads. Later: > Add search and filters to the Leads page. Users should be able to search by name, email, or phone and filter by status and assigned agent. Then: > Add bulk actions so users can select multiple leads and assign them to an agent or change their status. Then: > Add CSV import so users can upload an existing list of leads. The feature becomes more sophisticated over time. You don't need to anticipate everything during the first build. ## Iterate on workflows Some of the most valuable improvements aren't new pages. They're improvements to how users accomplish something. For example, imagine your application requires: **Lead → Open Lead → Create Follow-up → Select Agent → Choose Date → Save** After using it, you might decide this is too slow. You could tell AIWA: > Improve the lead follow-up workflow. Add a quick "Schedule Follow-up" action directly on the lead detail page. Preselect the lead and assigned agent so the user only needs to choose the follow-up type and due date. You're not asking for an entirely new feature. You're improving the existing product experience. ## Make focused changes When possible, keep iteration prompts focused. For example: > On the Properties page only, increase the property image size and move the price directly below the property name. Keep the filters, search, pagination, and property creation flow unchanged. This clearly defines the scope. Focused prompts are especially useful as your application becomes larger because they reduce unnecessary changes to parts that already work. ## Protect what already works As your product matures, some functionality may already be exactly how you want it. Tell AIWA when it should be preserved. For example: > Redesign the checkout page to make the pricing summary clearer. Do not change the existing Stripe integration, payment logic, subscription plans, or checkout functionality. Or: > Improve the mobile navigation. Keep the desktop navigation completely unchanged. A useful iteration prompt often contains both: **What should change** and **what should stay the same.** ## Change direction when you need to Iteration isn't only about small improvements. Sometimes you learn that the product itself needs to change. Imagine you initially built: > A project management tool for freelancers. After talking to customers, you decide agencies are a better market. You can ask AIWA to help you understand the implications before rebuilding everything. Use Explore or Plan: > We originally built this product for individual freelancers. We now want to reposition it for agencies managing multiple clients. Analyze the existing application and identify what needs to change in the product, data model, permissions, navigation, onboarding, and workflows. Don't implement anything yet. Once you've reviewed the direction, you can plan and build the changes. ## Use the right mode while iterating Iteration can involve all four AIWA modes. **Build** When you know what should change: > Add a status filter to the Orders page. **Plan** When the change has significant dependencies: > Plan how to add multi-currency support across products, checkout, invoices, reporting, and existing customer data. **Explore** When you're not sure what the best improvement is: > Review the current onboarding flow and identify the biggest sources of friction for a first-time user. **Debug** When an existing feature isn't working: > Customers can successfully complete payment, but their subscription isn't being activated afterward. Find the cause and fix it. Iteration isn't a single type of work. Your mode should change depending on the problem you're solving. ## Use feedback to improve your product Once real people begin using your application, their feedback can become input for AIWA. Suppose customers tell you: > "I can't easily tell which invoices are overdue." You can turn that directly into a product request: > Users are having difficulty identifying overdue invoices. Improve the invoices page so overdue invoices are immediately recognizable. Add an Overdue filter and clearly display how many days each overdue invoice is past due. Preserve the existing invoice creation and payment functionality. This creates a powerful loop: **Users → Feedback → AIWA → Product improvement → Users** ## You can iterate after publishing Your application doesn't stop evolving because you've published it. You can return to AIWA, make changes, test them, and publish the updated version. For example: **Version 1** Launch your booking application. **Version 2** Add customer accounts. **Version 3** Add payments. **Version 4** Add subscriptions. **Version 5** Add staff scheduling. **Version 6** Add automated reminders. Your live application can continue evolving alongside your business. ## Small iterations vs major changes Not every iteration should be treated the same way. **Small iteration** > Change the CTA copy. Build + Min. **Focused feature** > Add search and filtering to the customer list. Build + Min may be enough. **Significant feature** > Add subscription billing with multiple plans and feature restrictions. Consider Plan + Max, then Build. **Major product change** > Convert this single-user application into a multi-tenant platform for agencies. Plan + Max is strongly recommended before implementation. Match the AIWA workflow to the complexity of the change. ## Don't keep adding features blindly Iteration doesn't always mean adding more. Sometimes the right improvement is to simplify. You can ask AIWA: > Review this dashboard and identify information that appears redundant or unnecessarily complex. Or: > The onboarding process currently has seven steps. Analyze whether we can reduce the number of steps without removing required information. Or: > This page has too many actions competing for attention. Simplify the interface around the three actions users perform most frequently. Good product development involves removing friction, not just adding functionality. ## When an iteration goes wrong If a change doesn't produce the result you expected, don't immediately rebuild the entire feature. Explain what went wrong. For example: > The new design is better, but you removed the status filters from the original page. Restore the existing filters while keeping the new layout. If the change introduces an actual error or breaks existing functionality, use Debug Mode. That's what we'll cover next. ## Build products, not generations AI-generated software can sometimes be thought of as: **Prompt → Generated app → Done** AIWA is designed around a different model: **Idea → Build → Use → Learn → Improve → Ship → Learn → Improve again** Your product isn't defined by its first prompt. It can continue evolving as you understand your users, your market, and your own ideas better. That's what it means to work with AIWA as your AI product team. ## Next: Fixing Errors Not every iteration is about adding or improving something. Sometimes something simply doesn't work. Next, we'll look at how to work with AIWA when you encounter errors, broken features, unexpected behavior, or failed integrations. Diagnose and fix broken features, errors, and unexpected behavior. # AIWA Min vs AIWA Max Source: https://docs.aiwa.codes/building/min-vs-max Learn when to pick AIWA Min for fast execution and AIWA Max for deeper reasoning across complex product and engineering work. AIWA gives you two levels of intelligence for working on your projects: **AIWA Min** and **AIWA Max**. Both can build and work on your applications, but they're optimized for different kinds of tasks. **AIWA Min** prioritizes speed and efficiency. **AIWA Max** uses deeper reasoning for more complex product and engineering work. The simplest rule is: **Use Min for straightforward work. Use Max when the task requires deeper thinking.** ## Which plans include Min and Max | Plan | AIWA Min | AIWA Max | Starts on | | - | - | - | - | | Launchpad (free) | Yes | Upgrade to unlock | Min | | Solo, Agency, Enterprise | Yes | Yes | Max | Paid workspaces open on **AIWA Max** by default. You can switch to Min at any time from the model menu in the composer, and AIWA remembers your choice. Min and Max are the same AIWA agent with a different thinking budget. Max spends longer reasoning before it acts, which is why it can use more credits on the same request. ## Quick comparison | | AIWA Min | AIWA Max | | - | - | - | | Speed | Faster | More deliberate | | Credit usage | Lower | Higher | | Simple changes | Excellent | Usually unnecessary | | UI changes | Excellent | Good | | Complex features | Good | Recommended | | Architecture | Limited | Recommended | | Complex debugging | Good | Recommended | | Large product changes | Good | Recommended | Using Max for every request isn't necessary. Choosing the right model for the task helps you use your AIWA credits more efficiently. AIWA Min Vs Max ## AIWA Min AIWA Min is optimized for fast, focused development work. Use Min when your request is relatively straightforward and doesn't require extensive reasoning across many parts of your application. Examples include: > Change the hero headline to "Build Better. Build Faster." > Add another item to the FAQ. > Make these cards display in two columns on tablets. > Add a phone number field to the contact form. > Change the primary button color to match our brand. For these kinds of requests, deeper reasoning usually isn't necessary. Min can understand the instruction and execute it efficiently. ### When to use AIWA Min Min is a good choice for: * Copy changes * Small design adjustments * Adding simple sections * Updating existing components * Straightforward page creation * Responsive layout changes * Simple forms * Minor feature modifications * Focused fixes * Routine iteration As your application evolves, many of your day-to-day changes will fall into this category. ## AIWA Max AIWA Max is designed for work that benefits from deeper reasoning and broader understanding of your application. Some product changes aren't isolated. They affect several systems at once and require AIWA to reason about how those systems interact. For example: > Convert this application into a multi-tenant SaaS. Companies should have separate workspaces, invite team members, assign roles and permissions, switch between workspaces, and maintain complete data isolation. That request potentially affects: * Authentication * Authorization * Database structure * APIs * Application state * Navigation * Existing features * Security * User experience This is the kind of work where Max becomes valuable. ### When to use AIWA Max Consider Max for: * Complex SaaS applications * Major new features * Architecture decisions * Database-heavy functionality * Authentication and authorization * Multi-user systems * Complex integrations * Major application restructuring * Difficult debugging * Features spanning many parts of your application * Complex Plan Mode sessions Think of Max as the option for situations where AIWA needs to reason across the product, rather than simply execute a focused instruction. ## A practical example Imagine you're building a CRM. You want to change the dashboard headline. > Change "Welcome back" to "Good morning, Sarah." Use Min. Then you want to add another filter to the leads page. > Add a lead source filter with Website, Referral, Facebook, Google, and Other. Use Min. Then you decide to introduce teams. > Add multi-tenant workspaces where companies can invite agents, assign roles, and keep all CRM data isolated between organizations. Use Max. Later, a button needs repositioning. > Move the Create Lead button beside the search bar on desktop. Switch back to Min. You don't need to stay on one model for the entire project. ## Match intelligence to the task A useful way to think about Min and Max is to consider the reasoning surface of your request. **Small reasoning surface** The change affects one clear part of the application. > Increase the spacing between these cards. Min. **Medium reasoning surface** The change affects several related components but the desired behavior is clear. > Add filtering and pagination to the customer list. Min will often be sufficient. **Large reasoning surface** The change affects several systems and requires architectural decisions. > Add organization-level roles and permissions throughout the application. Max. The more dependencies AIWA needs to reason about, the more useful Max becomes. ## Min doesn't mean low quality It's important to understand that Min isn't simply a worse version of Max. Min is optimized for a different kind of work. Using deep reasoning to change a headline or add a simple button would often be unnecessary. The goal is to use the appropriate level of intelligence for the problem you're solving. Think of it like choosing the right member of a product team for the task. You wouldn't need an architecture review to change a sentence on a landing page. ## Max doesn't replace a good prompt Using Max doesn't mean your instructions can be unclear. Compare: > Improve my SaaS. with: > Review the onboarding flow for this SaaS application. New users currently sign up and immediately reach an empty dashboard. Improve the onboarding experience so they understand what to do next and can reach their first successful outcome quickly. The second request gives Max a much clearer problem to reason about. Good context plus appropriate intelligence usually produces better results. ## Using Min and Max with AIWA modes Your model choice and your mode solve different problems. **Mode** tells AIWA how to approach the request. **Min or Max** determines how much reasoning to apply. For example: **Build + Min** > Add another pricing tier to this page. Straightforward implementation. **Build + Max** > Implement the approved multi-tenant workspace architecture across the existing application. Complex implementation. **Plan + Min** > Plan a simple testimonials feature for the homepage. Possible, although probably unnecessary. **Plan + Max** > Plan how to add marketplace functionality with buyers, sellers, listings, orders, payments, commissions, and disputes to the existing SaaS. This requires much deeper product and technical reasoning. ## Max is especially useful with Plan Mode For significant features, Plan + Max can be a powerful combination. For example: > Analyze the existing application and create a plan for introducing subscription billing with Free, Pro, and Business tiers. Cover Stripe integration, feature entitlements, upgrades, downgrades, cancellations, webhooks, billing portal access, database changes, and failure scenarios. Max can reason through the dependencies before anything is implemented. Once the plan is approved, you can move into Build Mode for implementation. ## Use your credits intentionally More reasoning requires more computation, so Min and Max may consume credits differently. That doesn't mean you should avoid Max. It means you should use it where the additional reasoning creates value. A good default strategy is: Paid workspaces start on Max. For normal development and focused changes, switching to Min is usually enough. If the request involves several systems, dependencies, or important product decisions, consider Max. Use deeper reasoning for architecture, complex planning, difficult features, and challenging debugging. Once you're back to straightforward iteration, switch to Min again. This gives you a balance between speed, intelligence, and credit efficiency. ## Which one should I choose? If you're unsure, ask yourself: **Is AIWA mostly executing my instruction, or does it need to figure out a complex problem?** If it's mostly executing: → AIWA Min If it needs substantial reasoning: → AIWA Max A simple rule to remember: **Min for execution. Max for complexity.** You can switch between them throughout the life of your project. ## Next: Project Memory AIWA doesn't only respond to the prompt in front of it. As your application grows, maintaining context about the product becomes increasingly important. See how AIWA remembers context about your product as it grows. # Plan Mode Source: https://docs.aiwa.codes/building/plan-mode Use Plan Mode to have AIWA design a structured specification you can review and refine before any code is written. Plan Mode lets AIWA think through your product or feature before making changes to your application. Instead of immediately implementing your request, AIWA analyzes what you're trying to accomplish and creates a structured plan for how it should be built. This is especially useful for complex applications, major features, architectural changes, or anything you want to review before implementation begins. **Plan first. Review the approach. Then build with confidence.** ## When to use Plan Mode You don't need Plan Mode for every request. A simple change like: > Change the primary button from blue to green. can usually go directly to Build Mode. But consider a request like: > Add a complete team workspace system. Users should be able to create workspaces, invite team members, assign roles, switch between workspaces, and keep each workspace's data separate. That change can affect: * Authentication * Database structure * Permissions * Navigation * Application logic * Existing data * Multiple pages and components This is a good candidate for Plan Mode. Plan Mode works particularly well for: * New SaaS applications * Complex features * Authentication systems * Databases and data models * User roles and permissions * Payment systems * Multi-step workflows * Major redesigns * Large changes to an existing application * Features involving several integrations A useful rule: **the more parts of your application a change could affect, the more useful planning becomes.** ## Starting a plan Select **Plan** from the mode selector before submitting your prompt. AIWA Plan & Build Modes Then describe what you want to accomplish. For example: > Build a CRM for a real estate agency. Agents should be able to manage leads, properties, deals, and follow-ups. Include team workspaces with Owner, Admin, and Agent roles. Each workspace's data must remain separate. AIWA will analyze the request before implementation. ## AIWA turns your idea into a specification Plan Mode goes beyond simply rewriting your prompt. AIWA thinks through the different parts required to make the product work. For a complex application, the resulting plan can cover areas such as: * Product goals * User requirements * Pages and routes * User experience * Design direction * Data models * Application functionality * Authentication and permissions * API behavior * Integrations * Implementation tasks The exact plan depends on what you're building. ## Understanding your AIWA plan AIWA organizes complex plans into structured sections. ### Product Intent Product Intent defines what you're building, who it's for, and what the product is supposed to accomplish. For example: > EstateFlow is a CRM for real estate agencies. It helps brokerage owners and agents manage leads, properties, deals, follow-ups, and team activity from one workspace. This gives the rest of the build a clear direction. ### Requirements Requirements describe what users should be able to do and how the application should behave. For example: > When an agent creates a lead, the system should save the lead's contact information, status, assigned agent, budget, property interest, and notes. Good requirements help turn a broad product idea into specific functionality. ### Experience and Design This section describes how the application should look and behave from the user's perspective. It can include: * Visual direction * Layout * Navigation * Responsive behavior * Typography * Colors * Important UI states * Page structure This helps AIWA think about the application as a product experience rather than only a collection of features. ### Data and Functionality For applications that store information or contain dynamic features, AIWA can plan the underlying functionality. This may include: * Data entities * Relationships * Authentication * Permissions * API behavior * Application state * Integrations * Business rules For example, a CRM might require relationships between: **Lead → Deal → Property → Agent** Planning these relationships before implementation can help avoid problems later. ### Implementation Tasks AIWA can break the approved specification into implementation tasks. These tasks give the build process a structured path from the specification to the working application. ## AIWA reviews the plan AIWA can also inspect the proposed plan for issues before implementation. This is where the planning process becomes particularly useful. A plan might initially overlook something important, such as: * Missing authentication checks * Undefined user permissions * Incomplete mobile behavior * Missing error states * Unclear data relationships * Inconsistent design rules * Missing API behavior AIWA can identify concerns and refine the specification before the build begins. AIWA Technical Plan Think of this as an internal product and engineering review. Instead of discovering every issue after implementation, AIWA can reason through many of the requirements beforehand. ## Review the plan yourself AIWA's plan is not something you have to accept blindly. Read through it before building. Ask yourself: **Does it understand the product?** Check that the Product Intent accurately describes what you're trying to create. **Are the important features included?** Look through the requirements and make sure nothing essential is missing. **Are the user roles correct?** If your application has customers, admins, team members, vendors, or other roles, verify what each one should be able to do. **Does the data model make sense?** Check that the information your application needs to store is represented. **Is anything being overbuilt?** AIWA may sometimes plan more functionality than you need for the first version. You can simplify the plan before implementation. ## Ask AIWA to change the plan If something isn't right, don't build yet. Tell AIWA what you want changed. For example: > Keep everything else in the plan, but remove the marketplace functionality. We don't need that in the first version. Or: > Customers should not be able to create projects. Only workspace Owners and Admins should have that permission. Update the plan accordingly. Or: > Properties should support multiple images. Update the data model and property management requirements before building. AIWA can revise the plan around your feedback. This creates a planning loop: **Request → Plan → Review → Refine → Approve** ## Answer AIWA's questions Sometimes AIWA may identify a product decision that can't be safely assumed. For example: > Should each lead's property interest be free text, or should it link to an existing Property record? Or: > Should deal stages be changed using drag-and-drop or a stage selector? These aren't necessarily technical problems. They're product decisions. Answering them gives AIWA clearer instructions before implementation. For example: > Link property interest to an existing Property record. Also allow the field to remain empty when the customer hasn't selected a property yet. The plan can then be updated around that decision. ## From Plan to Build Once you're satisfied with the specification, you're ready to implement it. The approved plan becomes the blueprint AIWA follows while building your application. At this point, move into Build Mode and have AIWA implement the approved plan. Explain the product or feature you want. AIWA turns the request into a structured specification. Check requirements, functionality, design, data, and implementation decisions. Answer questions and ask AIWA to correct or improve the plan. Once you're satisfied, let AIWA implement the approved specification. ## Planning changes to an existing application Plan Mode isn't only for new projects. It can be even more valuable when modifying something you've already built. For example: > I want to turn this single-user CRM into a multi-tenant SaaS application. Analyze the existing project and create a plan for adding workspaces, team invitations, roles, data isolation, and workspace switching. Preserve the existing CRM functionality. AIWA can reason about the existing application alongside the new requirements. This is useful because major changes often affect functionality that's already working. For significant changes to an existing application, clearly tell AIWA what existing behavior must be preserved. ## Plan Mode vs Build Mode The difference is simple: | | Plan Mode | Build Mode | | - | - | - | | Primary goal | Think and structure | Implement | | Changes application immediately | No | Yes | | Creates specification | Yes | Not the primary goal | | Best for complex work | Yes | After direction is clear | | Lets you review before implementation | Yes | - | | Best for quick changes | Usually unnecessary | Yes | You can use them together. **Plan the complex work → Build the approved plan.** ## Plan Mode example Imagine you're adding subscriptions to an existing SaaS application. Instead of immediately saying: > Add Stripe subscriptions. Start in Plan Mode: > We need to add subscription billing to this SaaS application. We want Free, Pro, and Business plans. Analyze the existing application and create a complete plan covering Stripe integration, checkout, subscription status, feature access by plan, upgrades, downgrades, cancellations, billing portal access, webhook handling, and required database changes. Don't implement anything yet. Review the resulting specification. If everything looks correct, you can move to Build Mode and implement it. This gives you far more visibility into a significant product change before AIWA touches the application. ## When you probably don't need Plan Mode Planning everything can slow you down unnecessarily. You probably don't need a full plan for: > Change this headline. > Add another FAQ item. > Make this section mobile responsive. > Add a button linking to the pricing page. > Change the card layout from three columns to four. For focused, low-risk changes, Build Mode is usually the better choice. ## The principle Plan Mode exists because good software isn't only about writing code. It requires understanding: **what should be built, why it should work that way, how different parts interact, and what could go wrong.** Plan Mode gives your AI product team space to reason through those decisions before implementation. ## Next: Build Mode You've planned and reviewed what needs to happen. Next, learn how Build Mode turns those requirements into a working application. Turn an approved plan into a working application. # Project Memory Source: https://docs.aiwa.codes/building/project-memory See how AIWA maintains context about your project so new prompts build on existing pages, data, and design instead of starting over. As your application grows, AIWA needs to understand more than your latest prompt. Project Memory helps AIWA maintain context about the application you're building, so you can continue developing the same product without explaining everything from scratch every time. It allows your conversations with AIWA to build on the work that has already happened. **Your project has context. Your next prompt doesn't start from zero.** ## Why Project Memory matters Imagine you've spent several days building a CRM. You've already created: * Authentication * Team workspaces * Leads * Customers * A sales pipeline * Tasks * User roles * A dashboard Now you ask: > Add an activity timeline to each lead. Without project context, an AI would need you to explain what a lead is, how your application is structured, how users work with leads, and how the new feature should fit into the existing product. AIWA works within the context of the project you're already building. That makes continued development much more natural. ## Your project is more than a conversation When you work inside an AIWA project, AIWA isn't treating every prompt as an entirely new application. Your existing project provides important context for future work. This can include things such as: * Existing pages * Components * Features * Application structure * Data models * Existing functionality * Previous implementation decisions * Integrations * Design patterns * The current state of the application This helps AIWA understand how a new request relates to what already exists. ## Continue where you left off Suppose you initially ask: > Build a CRM for a real estate agency. Agents should be able to manage leads, properties, deals, and follow-ups. AIWA builds the initial product. Later, inside the same project, you can say: > Add a notes section to each lead. You don't necessarily need to repeat: > This is a real estate CRM and it has leads... The existing project gives AIWA context for understanding what you're referring to. Later, you might say: > Show the five most recent notes on the dashboard. AIWA can work with the existing application rather than treating the request as an unrelated feature. ## Project Memory helps your application evolve Project Memory becomes increasingly valuable as your application becomes more sophisticated. Your development process might look like this: > Build a client portal for a marketing agency. AIWA creates the initial product. > Add projects for each client. AIWA works within the existing portal. > Allow each project to have tasks, files, and comments. The new functionality builds on the existing project structure. > Notify clients by email when their project status changes. AIWA connects the new requirement to functionality you've already created. The product becomes richer over time without every request needing to redefine the entire application. ## Memory doesn't mean you should be vague Project context allows you to avoid unnecessary repetition, but clear instructions still matter. For example: > Fix the dashboard. is still ambiguous. AIWA may understand what dashboard you're referring to, but it doesn't necessarily know what you think is wrong. A better prompt would be: > The dashboard feels too crowded. Keep the existing metrics, but move recent activity below the project list and give upcoming deadlines more visual prominence. Project Memory provides context. Your prompt still provides intent. Both matter. ## Reference existing parts naturally When you're working inside an established project, you can refer to existing features directly. For example: > Add search to the Leads page. > Show the current user's avatar in the existing sidebar. > Add the new status to the same filters used on the Projects page. > Use the existing confirmation dialog when deleting a customer. > Add this metric beside the existing revenue KPI. These instructions tell AIWA how new work should relate to the product that already exists. ## Tell AIWA what should remain unchanged Context becomes particularly important when modifying mature applications. Suppose you say: > Redesign the customer detail page. That's a broad instruction. If parts of the page already work well, give AIWA boundaries: > Redesign the customer detail page to improve information hierarchy. Keep the existing customer fields, API behavior, editing functionality, and activity timeline unchanged. Only restructure the presentation. Now AIWA knows both: **What should change** and **what should be preserved.** As your application becomes more mature, explicitly protecting important existing behavior can help keep changes focused. ## Project Memory and design consistency Context also helps AIWA build new features that belong in the existing product. If your application already has: * A navigation system * Button styles * Forms * Cards * Tables * Empty states * Dialogs * Typography * Spacing conventions new features should generally work with those established patterns instead of creating an entirely different interface. For example: > Add an Invoices page. Follow the existing dashboard's visual system and reuse existing UI patterns wherever appropriate. This helps reinforce consistency as the application grows. ## Project Memory and your data model For dynamic applications, existing data structures are an important part of project context. Suppose your application already has: **Customers → Projects → Tasks** and you ask: > Add file attachments to tasks. AIWA should consider how the new functionality relates to the existing Task entity and application workflow. For more significant data changes, however, you should consider using Plan Mode. For example: > We need to allow a single task to belong to multiple projects. Analyze how this affects the existing data model and application before changing anything. That is a structural change where deeper planning can be valuable. ## Use the same project when evolving your application If you're continuing to build the same product, continue working inside the existing AIWA project. Don't create a new project simply because you're adding another feature. For example, if you've built a booking application and now want to add: * Customer accounts * Subscriptions * Notifications * Staff dashboards * Reporting those features should generally continue inside the same project. This allows AIWA to work with the application that already exists. Create a separate project when you're actually building a separate product or intentionally starting from a new foundation. ## When to remind AIWA Even with project context, there are situations where repeating an important requirement is useful. Especially when the requirement is critical to the change you're requesting. For example: > Add reporting to the admin dashboard. Remember that all data must remain isolated by workspace: an administrator must never see another workspace's data. Or: > Add image uploads to property listings. Preserve the existing Cloudinary integration rather than introducing another storage provider. Or: > Redesign the onboarding flow, but keep Google and email/password authentication exactly as they work now. You're not repeating the entire project. You're highlighting the context that matters most to the current task. ## When AIWA seems to misunderstand the project If AIWA's response suggests that it has misunderstood something important, correct the assumption explicitly. For example: > That's not how this project works. Deals always belong to a workspace and must also be linked to an existing lead. Keep that relationship and update your approach. For a larger misunderstanding, use Explore or Plan Mode to inspect the existing application before making changes. For example: > Before changing anything, analyze how Leads, Deals, and Workspaces currently relate to each other and explain the existing implementation. Then decide what should happen next. ## Project Memory and long-running applications As a product grows, your requests often become less about generating something new and more about evolving what already exists. You may move from: > Build a CRM. to: > Add team management. then: > Add reporting. then: > Add subscriptions. then: > Improve onboarding based on customer feedback. then: > Add an AI assistant that can summarize customer activity. The product changes, but it remains the same project. Project Memory helps AIWA work within that evolving context. ## Context + instruction + intent A useful mental model is: **Project Memory** What already exists. **Your prompt** What you want now. **AIWA's reasoning** How the new request should fit into the product. **=** **The next version of your application** This is what makes iterative development with AIWA possible. ## Best practices To get the most from Project Memory: * Continue working in the same project when evolving the same application. * Refer to existing pages and features by name. * Clearly explain what you want changed. * Tell AIWA what must remain unchanged when it matters. * Reinforce critical business rules in relevant prompts. * Use Plan Mode before major structural changes. * Correct important misunderstandings before allowing AIWA to continue building. You don't need to explain your entire application with every prompt. Give AIWA the new information and decisions that matter for the work you're doing now. ## Next: Iterating on Your App Project Memory allows AIWA to understand the application you're already building. Next, we'll look at how to use that context effectively to iterate on your app: improving designs, adding features, changing workflows, and evolving your product without starting over. Evolve your product through focused, follow-up changes. # The Brief and Clarifying Questions Source: https://docs.aiwa.codes/building/the-brief Let AIWA interview you about your idea and write a complete brief before it builds, and learn how AIWA asks quick questions when a request is too thin. The fastest way to waste credits is to build the wrong thing. AIWA has two ways to make sure it understands you before it starts: **the Brief**, which you ask for, and **clarifying questions**, which AIWA asks on its own when something important is missing. ## The Brief The Brief is a short interview. You describe your idea in a sentence or two, AIWA asks you what it needs to know, and then it writes a complete, well-structured request for you to build from. It's the right choice when you know roughly what you want but haven't thought through the details yet. ### Start a Brief There are two ways to start one: Type your idea into the prompt box. Once it's a little more than a few words long, a **Brief** button appears in the composer. Hover over it to see which details your idea doesn't cover yet, then click it. Start your message with `/brief`, followed by your idea, and press Enter. For example: > /brief a directory of coarse fishing venues in the UK Typing `/` at the start of the prompt box opens the command menu. It lists the Brief and the modes available on that screen, so you can switch to Build, Plan, Explore, or Debug without reaching for the mouse. ### What AIWA asks about The Brief checks your idea against the details that most often decide whether a first build lands: | Detail | Example | | - | - | | What it is | A directory, a booking site, an internal dashboard | | Who it's for | Anglers looking for a venue | | Key pages | Home, search, a venue page, contact | | Look and feel | Clean and outdoorsy, not corporate | | Anything to go on | A link or a screenshot | AIWA only asks about what's missing. If your idea already covers something, it won't ask again. ### Review the brief When you've answered, AIWA writes the brief into the prompt box. Read it, change anything you like, and send it in whichever mode you want, usually Build or Plan. Nothing is built until you send it. ### What the Brief costs | | Cost | | - | - | | Your first Brief each day | Free | | Each further Brief that day | 2 credits | | Answering the questions | Free | | Abandoning a Brief halfway | Free | You're only charged when AIWA writes a finished brief. This applies on every plan. A Brief costs far less than a build that goes the wrong way. If you're about to start a large project and aren't sure your request says enough, it's usually worth it. ## Clarifying questions Sometimes you'll skip the Brief and send a request directly, but the request is too thin to build well. For example: > Build me a website Instead of guessing, AIWA may pause and ask one or a few quick questions first. Each question comes with options to pick from, and you can usually type your own answer instead. * **Answering is free.** AIWA asks before it spends credits on the build. * **You can skip.** If you skip, AIWA uses the recommended option for each question and carries on. * **AIWA won't nag.** A question you've already answered or skipped won't be asked again for the same thing. ## When you mention a website If your request names a website, AIWA looks at it and asks how you mean it: > You mentioned example.com. Is that a site you already have, or a reference for how this one should look? | Answer | What AIWA does | | - | - | | **I already have it** | Works from that site as it is now, keeping its name, content, and sections | | **Just a reference** | Builds something new, taking cues from how that site looks | | **Neither, ignore it** | Follows the rest of your message and treats the link as background | AIWA shows a one-line summary of what it found on the site, so you can confirm it looked at the right one. If you skip the question, AIWA assumes it's your own site. That's the safer reading: it means AIWA won't invent a new name or brand for a business that already has one. ## Brief, clarifying questions, or Plan Mode? | Use | When | | - | - | | **The Brief** | You have an idea but haven't worked out the details | | **Clarifying questions** | Nothing to do. AIWA asks on its own when it needs to | | **Plan Mode** | You know what you want and the work is complex enough to review a full specification first | You can combine them: write a Brief, then send it in Plan Mode to get a detailed plan before anything is built. ## Next: Plan Mode Next, we'll take a closer look at Plan Mode, how AIWA turns complex requirements into a structured specification you can review before building. Review and approve a spec before AIWA builds. # Writing Effective Prompts Source: https://docs.aiwa.codes/building/writing-effective-prompts Learn how to describe products, users, flows, and design direction so AIWA builds closer to what you imagined the first time. The quality of what AIWA builds depends partly on how clearly you communicate what you want. You don't need to learn a special prompting language or write technical specifications. But giving AIWA the right context helps your AI product team understand your goals, make better decisions, and build closer to what you imagined. This guide shows you how to write effective prompts for websites, applications, features, design changes, and more complex product work. ## Think in outcomes, not code A good AIWA prompt starts with what you want the product to accomplish. You usually don't need to tell AIWA exactly how to implement it. Instead of: > Create a React component with a form containing five input fields and POST the data to an API endpoint. Try: > Add a quote request form to the construction website. Visitors should enter their name, email, phone number, project type, budget, and a short description of their project. Save each request so it can be viewed later from the admin dashboard. The second prompt gives AIWA something more valuable: the desired product behavior. AIWA can determine the implementation required to achieve it. ## The four parts of a strong prompt For larger requests, a useful structure is: **Context → Goal → Requirements → Direction** ### Context Tell AIWA what you're working on and who it's for. > I'm building a CRM for a real estate agency with a team of agents. ### Goal Explain what you want to accomplish. > I want agents to have one place to manage potential buyers and sellers. ### Requirements Describe the important things users should be able to do. > Agents should be able to create leads, assign leads to team members, change lead status, add notes, schedule follow-ups, and search or filter the lead list. ### Direction Add any important experience or design preferences. > Keep the interface professional and easy to scan. Use a clean table on desktop and cards on mobile. Combined: > I'm building a CRM for a real estate agency with a team of agents. I want agents to have one place to manage potential buyers and sellers. Agents should be able to create leads, assign leads to team members, change lead status, add notes, schedule follow-ups, and search or filter the lead list. Keep the interface professional and easy to scan. Use a clean table on desktop and cards on mobile. That's a strong AIWA prompt. ## Be specific where it matters More words don't automatically make a better prompt. The goal is to give AIWA useful information. **Too vague** > Build me a CRM. AIWA has to make many assumptions about what kind of CRM you need. **Better** > Build a CRM for a real estate agency. Agents should be able to manage leads, properties, deals, and follow-ups. Include a dashboard showing active leads, pipeline value, upcoming follow-ups, and recent activity. Now AIWA understands the industry, users, core resources, and dashboard requirements. ## Tell AIWA who the user is Knowing who will use the product can change how AIWA approaches the experience. Instead of: > Build an appointment booking system. Try: > Build an appointment booking system for a beauty salon. Customers should be able to choose a service, select a stylist, see available appointment times, and book online. Salon staff should have a dashboard for managing appointments. You've now identified two different users: * Customers * Salon staff That gives AIWA much more context for designing the application. ## Describe important user flows For applications, describe what should happen from the user's perspective. For example: > A new customer should be able to create an account, choose a subscription plan, complete payment, and then be taken to their dashboard. Or: > When an agent creates a new lead, they should be able to assign it to another team member and schedule a follow-up without leaving the lead page. User flows help AIWA understand how different parts of your application should work together. ## Give AIWA design direction You can describe how you want the application to feel without specifying every CSS property. For example: > Make the website feel premium, modern, and architectural. Use generous whitespace, strong typography, large professional construction photography, and subtle animations. Avoid making it feel like a generic template. Or: > Design the dashboard like a premium B2B SaaS product. Keep information dense but easy to scan, with clear hierarchy and minimal visual clutter. You can describe: * Visual style * Brand personality * Layout preferences * Colors * Typography * Density * Animation * Mobile behavior If you have specific brand colors, fonts, or design requirements, include them. AIWA doesn't need to guess when you already know what you want. ## Use references carefully You can describe products or design styles that communicate the direction you're looking for. For example: > I want the dashboard to feel polished and minimal like a modern enterprise SaaS product, with strong information hierarchy and generous spacing. The goal isn't necessarily to copy another product. References should help communicate qualities such as: *clean, editorial, playful, enterprise, minimal, luxurious, technical, bold, or approachable.* If a reference is a real website, AIWA can look at it. When you mention a site, AIWA asks whether it's your own site or just a reference, so it knows whether to keep its content or only take cues from its look. See [The Brief](/building/the-brief#when-you-mention-a-website). ## Attach images and documents You can attach files to a message so AIWA can see what you mean: a sketch, a screenshot of a design you like, your logo, or a written spec. | | Launchpad | Paid plans | | - | - | - | | Attachments per message | 5 | 10 | * **Images** (PNG, JPEG, GIF, WebP): up to 10 MB each * **Text documents** (.md, .markdown, .txt): up to 256 KB each Tell AIWA what each attachment is for: > Use the attached screenshot as the layout reference for the pricing page. Keep our own colors and copy. ## Break complex work into stages You don't need to build an entire sophisticated product in one instruction. For complex applications, working in stages often gives you more opportunities to review important decisions. For example: **Stage 1** > Build the core CRM with leads, contacts, and a dashboard. **Stage 2** > Now add a sales pipeline. Deals should move through Qualified, Proposal, Negotiation, Won, and Lost stages. **Stage 3** > Add team management. Workspace owners should be able to invite agents and assign leads and deals to them. **Stage 4** > Add reporting showing pipeline value, conversion rate, deals won this month, and performance by agent. You are evolving the product instead of trying to describe every future requirement at once. ## Tell AIWA what to keep When modifying an existing application, tell AIWA what shouldn't change when that's important. For example: > Redesign the hero section to make the headline and CTA more prominent. Keep the existing navigation, colors, typography, and the rest of the homepage unchanged. This gives AIWA clear boundaries. Another example: > Add search and filtering to the customer table. Don't change the existing table columns or customer creation flow. This is especially useful when your application is already close to what you want. ## Give feedback precisely If something doesn't look or work the way you expected, avoid simply saying: > I don't like this. Tell AIWA what needs to improve. For example: > The hero feels too crowded. Reduce the amount of text, give the headline more breathing room, make the primary CTA more prominent, and reduce the number of elements above the fold. Or: > The dashboard is difficult to scan. Make the four main KPIs more prominent, move recent activity lower on the page, and give the upcoming tasks section more visual priority. You don't necessarily need to know the solution. You can describe the problem you're experiencing, and AIWA can help determine the solution. Point at the exact thing you mean. In the preview, use **Select an element** to attach a specific button, card, or section to your message, or **Draw an annotation** to circle the area you want changed. ## Prompt for behavior, not just appearance When building applications, don't stop at describing what something should look like. Explain what should happen. Instead of: > Add a login page. Try: > Add authentication. Users should be able to create an account with email and password or sign in with Google. After signing in, take them to their dashboard. Signed-out users shouldn't be able to access dashboard pages. The second prompt describes the actual product behavior. ## Ask AIWA to think before changing complex features Some changes affect several parts of an application. For example: > I want to add multi-tenant workspaces so each company has separate users and data. Don't build this yet. First analyze the existing application and create a plan covering the database changes, authentication, permissions, migration risks, and pages that need to change. This is where Plan mode becomes particularly useful. We'll cover planning complex changes in detail in **Plan Mode**. ## Examples of effective prompts ### Website > Build a premium website for a commercial construction company serving businesses in Lagos. Include Home, About, Services, Projects, Safety, Careers, and Contact. The main conversion goal is quote requests. Use strong architectural photography, bold typography, generous whitespace, and a professional corporate feel. Make the site fully responsive. ### SaaS application > Build a SaaS application for agencies to manage clients and projects. Users should be able to create a workspace, invite team members, add clients, create projects for each client, assign tasks, track deadlines, and see recent activity from a dashboard. Each workspace's data must remain separate. ### Feature > Add a notification center to the existing application. Show unread notifications in the header with a badge. Users should be able to open the notification panel, mark individual notifications as read, or mark all as read. Keep the existing header design. ### Improvement > Improve the mobile experience of this page. Keep the desktop layout unchanged. On mobile, stack the cards vertically, make all primary actions full-width, ensure touch targets are easy to tap, and prevent the table from overflowing the viewport. ### Fix > The form currently submits but users receive no confirmation. After a successful submission, show a success message, clear the form, and disable the submit button while the request is processing. If submission fails, preserve the user's input and show a clear error message. ## A reusable prompt framework When you're unsure how to structure a complex request, use this: ```text theme={null} I'm building [PRODUCT] for [AUDIENCE]. The goal is [OUTCOME]. Users should be able to: - [REQUIREMENT] - [REQUIREMENT] - [REQUIREMENT] The experience should feel [DESIGN DIRECTION]. Important constraints: - [CONSTRAINT] - [CONSTRAINT] Keep [EXISTING THINGS THAT SHOULD NOT CHANGE]. ``` You don't need to fill every field. Use only the information relevant to what you're asking AIWA to do. ## The most important rule Tell AIWA what you're trying to achieve, not just what you want generated. AIWA works best when it understands: **Who is this for? → What problem are we solving? → What should users be able to do? → What should the experience feel like?** From there, your AI product team can make much better implementation decisions. ## Next: The four modes Now that you know how to communicate effectively with AIWA, learn how to choose the right way for AIWA to approach your request: **Build → Plan → Explore → Debug** Each mode is designed for a different kind of work. Choose the right way for AIWA to approach each request. # APIs and Server-Side Logic Source: https://docs.aiwa.codes/builds/apis-server-logic Describe how your product should behave and AIWA builds the APIs, permissions, validation, and business logic behind the interface. Behind every useful application are rules that determine what happens when users take action. When someone creates a booking, updates a customer, completes a payment, invites a team member, or changes a deal's status, your application needs logic to process that action. AIWA can build the APIs and server-side functionality required to power these experiences. You don't need to design every endpoint yourself. Describe what your application should do, and AIWA can build the logic behind it. **You define the behavior. AIWA builds the logic that makes it happen.** ## What is server-side logic? Your application has things users can see and things that happen behind the scenes. The interface might display a button: ```text theme={null} [Create Lead] ``` But clicking that button may need to: * Check that the user is signed in * Validate the information entered * Check the user's permissions * Save the lead to the database * Associate it with the correct workspace * Record the activity * Return the newly created lead * Update the interface The button is the visible part. The rules and operations behind it are part of the application's logic. ## Frontend vs backend A simple way to think about an application is: ```text theme={null} USER ↓ FRONTEND What the user sees and interacts with ↓ BACKEND Processes requests and applies rules ↓ DATABASE / SERVICES Stores data or communicates with other systems ``` The frontend might contain: * Buttons * Forms * Dashboards * Tables * Navigation * Modals * Charts The backend might handle: * Saving information * Retrieving information * Permissions * Calculations * Business rules * External integrations * Payment verification * Data validation AIWA can work across both. ## What is an API? An API provides a structured way for different parts of software to communicate. For example, your Leads page needs to retrieve leads from your application's backend. Conceptually: ```text theme={null} Leads Page ↓ "Give me the leads" ↓ API ↓ Database ↓ API ↓ Leads Page ``` When someone creates a lead: ```text theme={null} Create Lead Form ↓ API Request ↓ Validate Data ↓ Save to Database ↓ Return Lead ↓ Update Interface ``` The user doesn't need to see or understand these requests. They simply experience an application that works. ## AIWA can create APIs for your application When the application you're describing needs APIs, AIWA can create them as part of the implementation. Suppose you ask: > Build lead management. Users should be able to create, view, edit, search, filter, and delete leads. Behind that experience, the application may require operations for: * Get leads * Get a lead * Create a lead * Update a lead * Delete a lead A developer might think about these as API endpoints. As an AIWA user, you can start with the desired product behavior. ## You don't need to specify endpoint names Technical users may choose to provide explicit API requirements. For example: ```text theme={null} GET /api/leads POST /api/leads GET /api/leads/:id PATCH /api/leads/:id DELETE /api/leads/:id ``` But that's optional. You can simply say: > Users should be able to create, view, edit, and delete leads. AIWA can determine what application infrastructure is required. If you're a developer and need a specific API structure, naming convention, response format, or validation behavior, you can include those requirements directly in your prompt. ## Business Logic Server-side functionality becomes especially important when your application has rules. For example: > When a deal moves to Closed Won, record the closing date and include the deal value in won revenue. That's a business rule. Or: > Only workspace Owners and Admins can invite team members. Another business rule. Or: > A booking cannot be created if another confirmed booking already occupies the selected time slot. Another rule. AIWA can build application behavior around these requirements. ## Describe rules in normal language You don't need to convert business rules into code before giving them to AIWA. For example: > Users can cancel bookings until 24 hours before the appointment. After that, the Cancel button should no longer be available and the backend should reject cancellation attempts. This tells AIWA: * Who can perform the action * What action is allowed * Under what condition * What should happen when the condition isn't met That's enough to define meaningful product behavior. ## Don't rely only on the interface Suppose only administrators should be able to delete users. It isn't enough to simply hide: ```text theme={null} [Delete User] ``` from regular users. A user shouldn't be able to bypass the interface and perform the restricted operation anyway. The backend should also enforce the rule. Conceptually: ```text theme={null} Delete User Request ↓ Is requester authenticated? ↓ Is requester an Admin? ↙ ↘ Yes No ↓ ↓ Delete Reject ``` This is why server-side logic is important for permissions and sensitive operations. Critical permissions and data-access rules should be enforced server-side, not only by hiding buttons or pages in the user interface. ## Authentication and APIs Many APIs should only work for authenticated users. For example: > Only signed-in users should be able to create projects. The application needs to determine who is making the request before allowing it. Conceptually: ```text theme={null} Create Project ↓ API Request ↓ Is user signed in? ↙ ↘ Yes No ↓ ↓ Continue Reject ``` For team applications, there may be another check. ```text theme={null} Create Project ↓ Signed in? ↓ Workspace member? ↓ Has permission? ↓ Create project ``` This combines authentication with authorization and application logic. ## Workspace-scoped data Multi-tenant SaaS applications require particularly careful server-side logic. Imagine two companies use the same CRM: ```text theme={null} Acme Realty ├── Leads ├── Deals └── Properties Northstar Realty ├── Leads ├── Deals └── Properties ``` When someone from Acme Realty requests leads, the application should return Acme's leads, not every lead in the database. Conceptually: ```text theme={null} Authenticated User ↓ Determine Workspace ↓ Verify Membership ↓ Retrieve Records WHERE workspace = user's workspace ↓ Return Results ``` This isolation should happen on the backend. ## Server-side validation Forms can validate information in the interface, but important validation should also happen server-side. Suppose your application requires: > Every lead must have a name and either an email address or phone number. The frontend can help the user by showing validation errors immediately. But the server should also reject invalid requests. Why? Because the backend is ultimately responsible for protecting the integrity of your application's data. ## Working with your database APIs often sit between your application's interface and its Neon database. For example: ```text theme={null} Dashboard ↓ GET DATA ↓ Server ↓ Neon Postgres ↓ Server ↓ Dashboard ``` When information changes: ```text theme={null} Edit Customer ↓ Save ↓ Server validates request ↓ Neon Postgres updated ↓ Updated customer returned ↓ Interface refreshes ``` This separation helps keep database operations in the appropriate part of the application. ## Calculations and Aggregations Server-side logic can also calculate information from your stored data. Suppose your database contains hundreds of deals. You ask AIWA: > Show total pipeline value, active deal count, deals won this month, and average deal size on the dashboard. The application can calculate those metrics from the underlying records. For example: ```text theme={null} Deals ↓ Filter active deals ↓ Calculate total value ↓ Return metric ↓ Dashboard $4.2M Pipeline Value ``` The displayed number can come from real application data rather than hard-coded content. ## Date-based logic Applications frequently need logic based on time. For example: * Show all follow-ups due today. * Mark invoices as overdue after their due date. * Prevent users from booking dates in the past. * Show deals expected to close within the next seven days. * Allow cancellation until 24 hours before an appointment. These requirements can be implemented as application logic around your stored data. ## Connecting External Services Your backend can also communicate with external services. Suppose a customer completes a booking. Your workflow might be: ```text theme={null} Customer submits booking ↓ Server validates request ↓ Save booking to Neon ↓ Send confirmation through Resend ↓ Return success ↓ Show confirmation screen ``` Or a payment: ```text theme={null} Customer selects Pro ↓ Create Stripe checkout ↓ Customer pays ↓ Stripe confirms payment ↓ Server processes event ↓ Update subscription ↓ Unlock Pro features ``` AIWA can build the application logic that connects these systems. ## Webhooks Some external services need to tell your application when something happens. This is commonly done using a webhook. For example, after a Stripe payment: ```text theme={null} Your Application ↓ Stripe Checkout ↓ Payment ↓ Stripe Webhook ↓ Your Application ↓ Update Subscription ``` The customer may have already left the checkout page when Stripe sends this information. That's why reliable payment systems shouldn't depend only on what happens in the browser. ## You don't need to understand webhooks to request them You can describe the desired behavior. For example: > When Stripe confirms that a subscription has been successfully activated, update the user's plan in our database and unlock the features included in that plan. AIWA can determine the technical implementation required. Technical users can, of course, provide more specific webhook requirements when needed. ## Background Actions Some workflows involve actions that don't need to block the user's immediate experience. For example: > After a new customer registers, create their account and then send a welcome email. The important customer-facing action is account creation. The email is a follow-up action. Similarly: > When a lead is assigned to an agent, update the lead immediately and notify the agent. Your application can coordinate multiple actions around a single user event. ## Error Handling Server-side operations can fail. A database may reject a request. An external service may be unavailable. A payment may fail. A request may contain invalid information. A good application should handle these situations gracefully. For example: ```text theme={null} Create Booking ↓ Something fails ↓ Do NOT pretend booking succeeded ↓ Return error ↓ Show useful message ↓ Allow user to retry ``` You can explicitly tell AIWA how important failures should behave. For example: > If the booking cannot be saved, don't send the confirmation email. Show the customer an error and allow them to try again. ## Think about what happens when something fails Consider a workflow: ```text theme={null} Payment ↓ Create Order ↓ Send Email ``` What happens if payment succeeds but order creation fails? For critical workflows involving money, access, inventory, or important customer data, failure behavior deserves careful consideration. For these systems, using Plan Mode before implementation is often a good idea. ## Optimistic Updates Some applications can feel faster by updating the interface immediately while the server processes the change. For example, when moving a deal between pipeline stages: **Qualified → Negotiation** the card can visually move immediately. The application then saves the change. If saving fails, the interface can return the deal to its previous stage and tell the user something went wrong. This pattern is known as an optimistic update. You don't need to request it for every interaction, but it can improve the experience for highly interactive applications. ## Example: CRM workflow Suppose you tell AIWA: > When an agent moves a deal to Closed Won, save the new stage, record the closing date, add an activity entry, update dashboard revenue, and show a success notification. That one action involves several pieces: ```text theme={null} Agent moves deal ↓ Verify permission ↓ Update deal ↓ Record closing date ↓ Create activity ↓ Recalculate metrics ↓ Return success ↓ Update interface ``` You're describing product behavior. AIWA handles the implementation behind it. ## Example: Booking System Consider: > Customers can book appointments with a specific staff member. A time slot cannot be booked twice. After a booking is created, save it and send the customer a confirmation email. The server-side workflow might conceptually be: ```text theme={null} Booking Request ↓ Validate customer information ↓ Check availability ↓ Slot available? ↙ ↘ Yes No ↓ ↓ Create Reject Booking Request ↓ Send Confirmation ↓ Return Success ``` The customer simply experiences a booking system that works correctly. ## Example: SaaS Permissions Suppose your SaaS has: * Owner * Admin * Member You define: > Owners can manage billing and delete the workspace. Owners and Admins can invite users. Members can create and edit projects but cannot manage the team. AIWA can build those rules into the application's server-side behavior. The UI can also reflect the permissions, but the backend remains responsible for enforcing important restrictions. ## Use Plan Mode for complex logic Straightforward logic can often be built directly. For example: > When a task is marked complete, save the completion date. Build Mode may be sufficient. But consider: > Add usage-based billing where each workspace receives monthly credits, actions consume different numbers of credits, unused subscription credits expire at the end of the billing cycle, purchased top-up credits don't expire, and the system must consume monthly credits before top-up credits. That involves: * Billing * Credit balances * Consumption rules * Renewal behavior * Payment events * Database structure * Concurrency * Permissions * Failure cases That's a strong candidate for: **Plan + Max → Review → Build** ## Describe behavior precisely A good server-side prompt answers questions such as: * Who can perform the action? * What should happen? * Under what conditions? * What data should change? * What should happen afterward? * What happens if it fails? For example: > Workspace Owners and Admins can invite team members. The email must not already belong to a workspace member. Create a pending invitation and send the invitation email. If sending the email fails, keep the invitation pending and allow the administrator to resend it. That's much stronger than: > Add invitations. ## You can still specify technical requirements Developers aren't restricted to product-level prompting. You can tell AIWA: > Add a cursor-paginated API for activity records ordered newest first, with a maximum limit of 100 records per request. Or: > Validate the webhook signature server-side before processing Stripe events. Or: > Make this operation transactional so partial updates aren't committed if one step fails. AIWA allows you to work at the level of abstraction appropriate for your experience and requirements. ## The principle The frontend determines what users interact with. The database determines what information exists. Authentication determines who the user is. Server-side logic determines: **What is allowed to happen?** And APIs provide the communication paths that make those interactions possible. Together: ```text theme={null} USER ↓ INTERFACE ↓ API ↓ SERVER-SIDE LOGIC ↓ DATABASE + EXTERNAL SERVICES ``` AIWA can work across this entire flow. You focus on defining the product behavior. ## Next: Managing Your Project Data Your application now has a database, authenticated users, forms, integrations, APIs, and server-side logic. But once real users begin creating information, another question becomes important: **How do I work with the data my application creates?** Next, we'll cover Managing Your Project Data: understanding, viewing, changing, and safely working with the information stored by your application. Understand, view, and safely change the information stored by your app. # Authentication Source: https://docs.aiwa.codes/builds/authentication Add Google and email/password sign-in, protect areas of your app, and shape roles, permissions, and workspace-level access with AIWA. Many applications need to know who is using them. A customer portal needs to know which customer signed in. A SaaS application needs to know which account owns a project. A team workspace needs to know which user is an administrator and which is a team member. AIWA can add authentication to your application using **Google sign-in** and **email/password authentication**. You describe who should be able to access your product and what they should be able to do. AIWA can build the authentication experience around those requirements. > **Authentication answers one fundamental question: Who is using the application?** ## What is authentication? Authentication is the process of verifying a user's identity. You've used authentication whenever you've: * Created an account * Signed in with an email and password * Used "Continue with Google" * Signed out of an application * Returned to an application and remained signed in Once a user has authenticated, your application can identify them and provide an experience associated with their account. ## AIWA supports user accounts AIWA Authentication When your application requires user accounts, AIWA can build authentication into the product. AIWA supports: **Google authentication** **Email and password authentication** For example, you can tell AIWA: > Add authentication to this application. Users should be able to create an account with email and password or continue with Google. After signing in, take them to the dashboard. AIWA can build the authentication experience as part of the application. ## You don't need to build authentication first You don't have to begin your project by manually creating login infrastructure. You can describe the product. For example: > Build a client portal where customers can create an account, sign in, view their projects, download files, and send messages to their account manager. AIWA can recognize that the application requires user identity and authenticated areas. Authentication becomes part of the product architecture. You can explicitly mention authentication requirements when you want greater control over signup, login, redirects, protected pages, roles, or onboarding behavior. ## Sign up For applications that allow registration, new users need a way to create an account. A typical signup experience might include: ```text theme={null} Create your account Name Email Password [Create account] or [Continue with Google] ``` After signup, you can define what should happen next. For example: > After a user creates an account, take them through onboarding before they can access the dashboard. Or: > After signup, create their workspace automatically and redirect them to the dashboard. Authentication can be connected to the rest of your application's workflow. ## Sign in Returning users need a way to access their existing account. For example: ```text theme={null} Welcome back Email Password [Sign in] [Continue with Google] ``` Once authenticated, the application can identify the user and give them access to the appropriate experience. You can also describe where users should go afterward: > After successful sign-in, redirect users to /app. Or: > After sign-in, return the user to the page they originally tried to access. ## Google sign-in Google authentication can reduce friction by allowing users to access your application with their Google account. Instead of creating another password, users can choose: **Continue with Google** For products where quick onboarding matters, providing both Google and email/password authentication gives users more flexibility. ## Protected pages Not every page in your application should necessarily be publicly accessible. A SaaS application might have: **Public pages** * `/` * `/pricing` * `/features` * `/login` * `/signup` Anyone can visit these pages. **Protected pages** * `/app` * `/app/projects` * `/app/customers` * `/app/team` * `/app/settings` These pages require authentication. If a signed-out user attempts to access a protected area, the application should direct them to authenticate before continuing. ## Tell AIWA what should be protected You can describe access requirements in natural language. For example: > The marketing website should remain public, but users must sign in before accessing the dashboard, projects, team, or settings. Or: > Anyone can browse properties, but users must create an account before saving a property to their favorites. Or: > Customers must be signed in to view their orders. These are product requirements. AIWA can translate them into authentication behavior. ## Authentication and your database Authentication becomes especially useful when combined with your project's database. Suppose your database contains: **Projects** Each project might have an owner. Conceptually: ```text theme={null} User ↓ Project ``` When the user signs in, the application knows who they are. It can then retrieve the data associated with that account. For example: > Show users only the projects that belong to them. This combines: **Authentication → Who is this?** **Database → What projects exist?** **Application logic → Which projects should this user see?** ## Authentication is not authorization This distinction becomes important as applications become more sophisticated. **Authentication** determines who the user is. **Authorization** determines what that user is allowed to do. For example: Sarah signs into the application. Authentication tells the application: * This is Sarah. * Sarah is an Agent. Authorization might then determine: > Sarah can view and manage leads assigned to her, but she cannot access workspace billing. These are two different responsibilities. ## Roles and permissions Many applications need different types of users. For example, an agency platform might have: * Owner * Admin * Agent You could define their permissions as: **Owner** Can manage the entire workspace, team, billing, and application settings. **Admin** Can manage most workspace functionality and team operations. **Agent** Can work with the operational features they have permission to access. You can describe these requirements directly: > Add Owner, Admin, and Agent roles. Only Owners should access billing. Owners and Admins can invite team members. Agents can manage leads and deals but cannot change workspace settings. AIWA can build application behavior around those requirements. ## Protect actions, not just pages Authorization shouldn't only determine whether someone can open a page. It can also determine whether they can perform specific actions. For example: An Agent may be allowed to: * View leads * Create leads * Update leads but not: * Delete team members * Change billing * Delete the workspace You can tell AIWA: > Agents can create and update customers but only Owners and Admins can delete customer records. This creates more granular permissions within the application. ## Multi-user applications Authentication becomes particularly important when multiple people use the same product. Imagine you're building project management software. A company creates a workspace and invites five employees. Conceptually: ```text theme={null} Workspace │ ├── Owner ├── Admin ├── Member ├── Member └── Member ``` The users are authenticated individually but belong to the same workspace. Your application can then associate data with that workspace: ```text theme={null} Workspace │ ├── Users ├── Projects ├── Tasks ├── Files └── Activity ``` This allows multiple authenticated users to collaborate inside the same organization. ## Data isolation matters For multi-tenant SaaS applications, authentication alone isn't enough. Suppose: * Company A uses your CRM. * Company B also uses your CRM. Their information must remain separate. ```text theme={null} Company A ├── Users ├── Leads └── Deals Company B ├── Users ├── Leads └── Deals ``` A user from Company A should never receive Company B's private data simply because both use the same application. This requires appropriate authorization and data-scoping rules in addition to authentication. For example: > Every lead, deal, and customer must belong to a workspace. Users must only be able to access records belonging to workspaces where they are members. For applications handling private customer or business data, requirements like this are critical. For multi-tenant applications, don't rely only on hiding information in the interface. Access restrictions should also be enforced by the application's server-side logic. ## Authentication can drive personalization Knowing who is signed in also allows your application to personalize the experience. For example: > Good morning, Sarah. Or: ```text theme={null} Your Projects Website Redesign Mobile Application Marketing Dashboard ``` Or: > Tasks assigned to you You can ask AIWA: > Personalize the dashboard using the signed-in user's first name and show their assigned tasks. Authentication provides the user identity required to build these experiences. ## Authentication and onboarding Signing up doesn't necessarily mean a user should immediately land on the main dashboard. Some applications need onboarding first. For example: ```text theme={null} Create Account ↓ Create Workspace ↓ Choose Business Type ↓ Invite Team ↓ Dashboard ``` You can describe this workflow: > After registration, new users should create their workspace, enter their company name and industry, and then reach the dashboard. Team invitations can be skipped during onboarding. AIWA can connect authentication with the product's onboarding experience. ## Authentication and existing users As your application evolves, you may want to change what happens after users authenticate. For example: > Existing users should continue going directly to their dashboard. Only newly registered users should see the new onboarding flow. This is an important distinction. Whenever changing authentication or onboarding in an application with existing users, clearly explain what should happen to both new and existing accounts. ## Plan complex authentication changes first Some authentication changes have consequences throughout an application. For example: > Convert this single-user application into a multi-tenant SaaS where companies can create workspaces, invite users, assign roles, and keep all company data isolated. This can affect: * Authentication * Database structure * Authorization * APIs * Existing records * Navigation * User onboarding * Invitations * Application state For changes like this, use Plan Mode before implementation. Authentication changes become architectural changes when they alter how users, organizations, permissions, and application data relate to one another. ## Don't expose sensitive information Authentication systems deal with sensitive information. Passwords, authentication secrets, tokens, and private credentials should not be displayed in public interfaces or exposed in client-side code. You generally shouldn't ask AIWA to: > Put the authentication secret directly in this frontend file. Instead, sensitive values should remain in the appropriate secure server-side or configuration environment. The same principle applies to API keys, database credentials, and other secrets. ## Example prompts Here are some examples of authentication requirements you can give AIWA. **Simple SaaS** > Add Google and email/password authentication. The homepage and pricing page should remain public. Everything under /app should require authentication. **Customer portal** > Customers should create accounts before accessing the portal. After signing in, they should only see projects associated with their account. **Team application** > Add workspaces with Owner, Admin, and Member roles. Owners can manage billing and the entire team. Admins can invite members and manage projects. Members can only access projects assigned to them. **Marketplace** > Buyers can browse without signing in, but they must authenticate before purchasing or saving products. Sellers must authenticate before accessing the seller dashboard. **Internal tool** > There should be no public registration. Only invited users should be able to access the application. You describe the access model. AIWA builds the experience around it. ## Test authentication as different users If your application has multiple roles, don't test everything from one account. For example, if your application has: * Owner * Admin * Agent test each role. Check whether the Owner can access billing. Check whether the Admin has the correct team controls. Check whether the Agent is prevented from accessing restricted functionality. Also test what happens when you're signed out. Authentication and permissions are only working correctly if each user receives the experience they're supposed to have. ## A useful mental model Think about access in three layers: **1. Who are you?** Authentication. > This is Sarah. **2. Where do you belong?** Membership / ownership. > Sarah belongs to Acme Realty. **3. What can you do?** Authorization. > Sarah is an Agent and can manage leads but cannot access billing. Together: ```text theme={null} Identity ↓ Membership ↓ Permissions ↓ Application Access ``` This becomes increasingly important as your application grows beyond a single user. ## You describe the access model You don't need to start by designing an authentication architecture. Start with questions such as: * Who uses this application? * Do they need accounts? * What should be public? * What requires sign-in? * Are there different types of users? * What can each role do? * Which data should each user be allowed to access? Describe those requirements to AIWA. Your AI product team can help turn them into the application's authentication and authorization behavior. ## Next: Adding Forms, Uploads, Email & Payments Authentication identifies your users, and your database stores application data. But real products often need to interact with the outside world too. Next, we'll look at how you can ask AIWA to add functionality such as: **Forms → File Uploads → Email → Payments** and how AIWA can connect these capabilities to the workflows you're building. Add real-world functionality to your app by describing what should happen. # What AIWA Sets Up Automatically Source: https://docs.aiwa.codes/builds/automatic-setup See how AIWA builds the interface, database, authentication, APIs, and backend logic behind your project without manual configuration. When you ask AIWA to build an application, you're not limited to generating pages and user interfaces. AIWA can build the systems behind your application too. For applications that need users, stored data, forms, dashboards, APIs, or other dynamic functionality, AIWA can set up the required application infrastructure as part of the build. You describe what your product should do. AIWA handles much of the technical setup required to make it work. > **Describe the product. AIWA builds the application behind it.** ## From interface to working application There's an important difference between a website that looks functional and an application that actually works. Imagine you ask: > Build a CRM for a real estate agency where agents can create accounts, manage leads and properties, track deals, and schedule follow-ups. A visual prototype could create the dashboard, forms, tables, and buttons. But a working CRM needs much more. It needs somewhere to store leads. It needs to know which user is signed in. It needs to retrieve the correct records. It needs to save changes. It needs server-side logic. It needs to protect private information. AIWA is designed to build these underlying systems alongside the interface. AIWA Real Estate Crm ## What AIWA can handle Depending on what your application requires, AIWA can work across several layers of the product. ### User interface The pages and components your users interact with. This can include: * Landing pages * Dashboards * Forms * Tables * Navigation * Settings * Admin interfaces * Responsive layouts ### Database Applications that need persistent information can use a database to store and retrieve data. For example: A CRM might store: **Users → Leads → Properties → Deals → Follow-ups** An e-commerce application might store: **Customers → Products → Orders → Payments** AIWA can create the data structures required by the product you're describing. ### Authentication If your application requires user accounts, AIWA can add authentication. AIWA projects can support: * Google sign-in * Email and password authentication This allows applications to identify users and protect areas that shouldn't be publicly accessible. We'll cover authentication in detail later in this section. AIWA Authentication ### Backend functionality Many application actions require logic that shouldn't exist only in the browser. AIWA can build server-side functionality required by your product. For example: > When a customer submits this form, save the enquiry and show it in the admin dashboard. Or: > Only workspace administrators should be able to delete team members. Or: > Calculate the total value of all active deals and display it on the dashboard. AIWA can translate product requirements like these into application behavior. ### APIs Different parts of an application often need a structured way to communicate with each other. AIWA can create APIs when they're required by the application. For example, your dashboard may need to: * Retrieve customers * Create a lead * Update a project * Delete a task * Load dashboard statistics You don't necessarily need to design these endpoints yourself. Describe what the application should do and AIWA can determine the implementation. ## What "zero config" means Traditionally, building a full-stack application can require setting up several systems before you even begin building the product. You might need to: * Create a database * Configure credentials * Connect the application to the database * Create database tables * Configure authentication * Build backend endpoints * Connect the frontend to those endpoints * Configure deployment AIWA is designed to remove much of this initial setup. If your application needs a database or authentication, you can describe the product requirement instead of manually assembling the infrastructure first. For example: > Build a client portal where customers can create accounts, log in, view their projects, and send messages to their account manager. You shouldn't have to begin by telling AIWA: > First create a database connection, configure authentication, create user tables, build login endpoints... Your product requirement is the starting point. "Zero config" doesn't mean every external service requires no setup. Some integrations, such as payment, email, communications, or third-party APIs, may still require you to connect your own account or credentials. ## AIWA understands product requirements One of the ideas behind AIWA is that you shouldn't need to translate every product requirement into an engineering requirement yourself. Suppose you say: > Customers should be able to create an account and save properties to their favorites. From a product perspective, that's a relatively simple sentence. But implementing it may require: * Authentication * User records * Property records * A relationship between users and saved properties * Backend functionality * UI states for saved and unsaved properties AIWA can reason about those underlying requirements while building the feature. You focus on what users should be able to do. ## Example: Building a CRM Consider this prompt: > Build a CRM for a real estate agency. Agents should be able to sign in, create leads, manage properties, track deals through a sales pipeline, schedule follow-ups, and view sales metrics from a dashboard. AIWA can determine that this application requires more than a collection of pages. **Authentication** Agents need identities and protected access. **Database** The application needs persistent records for things such as: Leads Properties Deals Follow-ups Users **Relationships** A deal may connect: **Lead → Property → Agent** A follow-up might connect: **Lead → Agent → Due Date** **Backend logic** The application needs to create, retrieve, update, and manage those records. **Dashboard** Metrics need to be calculated from real application data. **Interface** Agents need pages and workflows for interacting with everything. AIWA can work across these layers as part of building the product. ## Your data persists A working application shouldn't lose important information every time the page refreshes. When your application uses a database, information can be stored persistently. For example, if a user creates a lead: > Sarah Chen, Budget: \$850,000, Status: Qualified the record can be stored in the application's database. When the user returns later, the application can retrieve that information again. This is what separates persistent application data from placeholder content that only exists in the interface. AIWA Data Persists ## Authentication protects your application Some pages should be public. Others shouldn't. For example, a SaaS application might have: **Public** * Homepage * Pricing * About * Sign in * Sign up and: **Protected** * Dashboard * Customers * Projects * Billing * Settings AIWA can build authenticated experiences where users must sign in before accessing protected areas. Applications can also use the authenticated user's identity when deciding what information they should see. ## You can keep extending the backend The infrastructure AIWA creates isn't limited to your first build. Suppose your original application only stores customers. Later you ask: > Add projects to each customer. Then: > Allow each project to have tasks. Then: > Add comments to tasks. Then: > Notify team members when they're assigned a task. Your application architecture can evolve alongside the product. This connects directly with the iterative development workflow we covered earlier. ## External services work differently Some functionality depends on services outside your AIWA project. Examples can include: * [Stripe for payments](/integrations/stripe) * [Resend for email](/integrations/resend) * [Twilio for communications](/integrations/twilio) * [Cloudinary for media](/integrations/cloudinary) * [AI model providers](/integrations/openai) * [Calendar services](/integrations/calendly) In these cases, you may need to connect the external service to AIWA. Once the required connector is configured, you can describe the functionality you want AIWA to build around it. For example: > Send the customer a confirmation email after they submit the booking form. Or: > Create a Stripe checkout flow for the Pro subscription. We'll cover these services in the Integrations (Connectors) section. ## You don't have to become a backend engineer AIWA gives technical users the ability to build sophisticated applications, but the product requirements can still be expressed in normal language. Instead of: > Create a POST endpoint that inserts a row into the leads table. you can say: > Allow agents to create leads. Instead of: > Add authorization middleware to this route. you can say: > Only administrators should be able to access this page and delete users. Instead of: > Create an aggregate query grouped by deal stage. you can say: > Show how much pipeline value we currently have at each deal stage. AIWA translates product intent into implementation. Developers can still provide detailed technical requirements when they want greater control. AIWA doesn't prevent technical prompting; it makes it optional for many workflows. ## Website or application? Not every project needs a database or authentication. For example: > Build a portfolio website for a photographer. may primarily require pages, content, images, navigation, and a contact experience. But: > Build a client portal for a photographer where customers can sign in, view their galleries, select favorite photos, download approved images, and see invoices. requires significantly more application functionality. AIWA can adapt the implementation to what you're actually building. The goal isn't to add infrastructure unnecessarily. It's to create the systems required by the product. A website with a contact or enquiry form doesn't get a database. Instead, AIWA sends each submission to you by email using [Resend](/integrations/resend), with clear success and error messages for your visitors. If Resend isn't connected yet, AIWA tells you on the build card. If you want submissions stored and shown in a dashboard, say so in your request and AIWA will add a database. ## What AIWA handles vs what you provide A useful way to think about the relationship is: | You provide | AIWA helps handle | | - | - | | Product idea | Application structure | | User requirements | UI implementation | | Features | Application logic | | Data requirements | Database structure | | Access requirements | Authentication behavior | | Workflows | Frontend + backend implementation | | Integration requirements | Connection logic | | Feedback | Continued iteration | For external services, you may still need to provide or connect the appropriate account and credentials. ## The result: a real application AIWA isn't designed only to make something that looks like software. It's designed to help you build software that works. That means thinking across: **Interface + Data + Authentication + Logic + APIs + Integrations + Deployment** You don't need to manually assemble each layer before you can begin. Start with the product. Tell AIWA what users should be able to accomplish. Your AI product team can help build the systems required to make that experience real. ## Next: Your Database We've talked about the application infrastructure AIWA can create automatically. Next, we'll look more closely at one of the most important parts of a dynamic application: **Your Database** We'll cover how AIWA stores project data, how your application uses that data, and what happens as your data model evolves. See how AIWA provisions Neon Postgres and evolves your data model. # Your Database Source: https://docs.aiwa.codes/builds/database AIWA provisions Neon Postgres per project and lets you describe the data your product needs in plain language instead of SQL. Most real applications need somewhere to store information. Customer accounts, leads, orders, bookings, projects, messages, subscriptions, settings, and other application data need to remain available after a user closes the browser or returns later. AIWA uses **Neon Postgres** to provide persistent database infrastructure for applications that need it. When your application requires stored data, AIWA can create and work with the database as part of building your product. > **You describe the data your product needs. AIWA helps turn those requirements into a working database-backed application.** ## What is a database? A database is where your application stores structured information. Imagine you're building a CRM. Your application might need to remember: * Leads * Customers * Team members * Deals * Follow-ups * Notes * Activities Without persistent storage, information entered into the application could disappear when the application reloads. A database allows your application to save that information and retrieve it again later. ## AIWA uses Neon Postgres AIWA uses Neon Postgres as the database infrastructure for your project. Postgres is a relational database, which means your application can store structured information and create relationships between different types of data. For example, a CRM might have: * Users * Leads * Properties * Deals * Follow-ups Those records can also relate to each other. ```text theme={null} Lead → Deal → Property ↓ Agent ``` This makes it possible to build applications where information is connected rather than stored as isolated pieces of content. ## Your project gets its own database When an AIWA project requires persistent application data, AIWA can provision the Neon database infrastructure for that project. This keeps the application's data associated with the project you're building. You don't need to begin by: * Creating a Neon project manually * Creating database tables yourself * Configuring a database server * Wiring the database into your application * Writing SQL before you can start building Instead, you can begin with the product requirement. For example: > Build a lead management system where agents can create leads, assign them to team members, update their status, add notes, and schedule follow-ups. AIWA can determine what data structures are needed to support that experience. AIWA handles the database infrastructure required by supported projects, allowing you to focus primarily on your application's data and behavior rather than initial database configuration. ### Only when your app needs one AIWA adds a database only when your request needs stored data, such as accounts, records, bookings, or a dashboard. A brochure website, a portfolio, or a landing page with a contact form doesn't get one. Form submissions on those sites are emailed to you instead. To keep submissions in a database, ask for it explicitly: > Save every enquiry to the database and show them in an admin dashboard. ## From your prompt to your database You don't need to describe your database using technical terminology. Suppose you tell AIWA: > Add lead management to the application. Each lead should have a name, email, phone number, source, status, assigned agent, budget, property interest, and notes. From that product requirement, AIWA can determine that the application needs a Lead data structure containing information similar to: ```text theme={null} Lead ├── Name ├── Email ├── Phone ├── Source ├── Status ├── Assigned Agent ├── Budget ├── Property Interest ├── Notes ├── Created Date └── Updated Date ``` AIWA can then build the application functionality around that data. The user sees a lead management experience. Behind the interface, the application has structured data it can save and retrieve. ## Data persists Database-backed information persists beyond the current page view. For example, imagine an agent creates: ```text theme={null} Name: Sarah Chen Email: sarah@example.com Status: Qualified Budget: $850,000 Source: Website ``` The application can save that information to its database. When the agent returns later, the application can retrieve Sarah's record again. The same principle applies to: * Customer profiles * Bookings * Orders * Tasks * Messages * Properties * Projects * Settings * Other dynamic application data This is what makes your application stateful rather than simply a collection of static screens. ## Tables organize your data Relational databases organize information into structures commonly called tables. For example, an agency application might have: * Customers * Projects * Tasks * Invoices A Customers table might contain information such as: ```text theme={null} Customer ├── Name ├── Email ├── Phone ├── Company ├── Status └── Created At ``` A Projects table might contain: ```text theme={null} Project ├── Name ├── Customer ├── Status ├── Budget ├── Start Date ├── Due Date └── Created At ``` You don't necessarily need to create these structures manually. Describe the information your application needs, and AIWA can build the appropriate data structures as part of the application. ## Your data can have relationships Real applications rarely contain completely isolated data. A project might belong to a customer. A task might belong to a project. An order might belong to a customer. A deal might connect a lead with a property. These are relationships. For example: ```text theme={null} Customer ↓ Project ↓ Task ``` One customer could have multiple projects, and each project could contain multiple tasks. Or in a real estate CRM: ```text theme={null} Lead ──────┐ ↓ Deal ↑ Property ──┘ │ ↓ Agent ``` Relationships allow different parts of your application to work together. ## Describe relationships naturally You don't have to say: > Create a foreign key between these database tables. You can describe the product behavior instead. For example: > Every project should belong to a customer, and a customer should be able to have multiple projects. Or: > Each deal should be connected to a lead, a property, and the agent responsible for the deal. Or: > A customer should be able to place multiple orders, and every order should show which customer placed it. These requirements tell AIWA how the information in your product relates. AIWA can translate that intent into the underlying implementation. ## Your database evolves with your application Your first database structure doesn't have to represent every feature you'll ever build. Suppose your first version has: * Customers * Projects Later, you tell AIWA: > Add tasks to projects. Your application now needs another type of data: ```text theme={null} Customers ↓ Projects ↓ Tasks ``` Later: > Allow users to comment on tasks. Now the application evolves again: ```text theme={null} Customers ↓ Projects ↓ Tasks ↓ Comments ``` Your data model can grow as your product grows. ## Adding fields later You can also extend existing data. Suppose your Lead records currently contain: * Name * Email * Phone * Status You later decide you need more information. You can tell AIWA: > Add source, budget, assigned agent, and property interest to leads. Update the create and edit forms and show the new information on the lead detail page. AIWA can update the application around the expanded data requirements. For significant database changes, consider using Plan Mode first so the impact can be reviewed before implementation. ## Changing existing data structures Some database changes are more significant than simply adding a field. For example: > Allow projects to belong to multiple customers instead of one customer. Or: > Convert the existing single-user data model into workspace-based data where every record belongs to an organization. These changes can affect: * Existing records * Relationships * APIs * Permissions * Application logic * User interfaces For changes like these, use Plan Mode, particularly if the application already contains important data. Be especially careful with structural changes to applications containing real production data. Ask AIWA to analyze the existing data model and plan the migration before making major changes. ## Your interface talks to your database The database usually works behind the scenes. Users interact with your application's interface. For example, when someone completes: ```text theme={null} Add Lead Name: Marcus Okonkwo Email: marcus@example.com Budget: $1,200,000 Status: New [Create Lead] ``` the application can send that information to the appropriate server-side functionality, which saves the record. When the Leads page opens, the application retrieves the relevant lead records and displays them. Conceptually: ```text theme={null} User ↓ Application Interface ↓ Server-Side Logic ↓ Neon Postgres ``` And when reading information: ```text theme={null} Neon Postgres ↓ Server-Side Logic ↓ Application Interface ↓ User ``` AIWA can build these pieces together. ## Database actions Most database-backed applications rely on four fundamental types of operations. **Create** Add new information. > Create a lead. **Read** Retrieve existing information. > Show all active leads. **Update** Change existing information. > Change this lead's status to Qualified. **Delete** Remove information. > Delete this lead. Developers often refer to these operations collectively as CRUD. You don't need to use that terminology when prompting AIWA. Simply describe what users should be able to do. ## Filtering and searching your data Once your application contains data, users often need ways to find the right records. For example: > Add search to the Leads page so users can search by name, email, or phone number. Or: > Allow agents to filter leads by status, source, and assigned agent. Or: > Show only bookings scheduled for today. AIWA can build interfaces and application logic around the information stored in your database. ## Dashboards can use real data Database-backed applications can calculate metrics from stored information. For example, a sales dashboard might show: ```text theme={null} Total Leads 1,248 Active Deals 37 Pipeline Value $4.2M Deals Won 18 ``` These figures can be derived from application data rather than being hard-coded placeholders. You can describe the metric you want: > Show the total value of all deals that haven't been won or lost. Or: > Show how many new leads were created this month compared with last month. AIWA can build the required data logic around the request. ## Keep private data private Database credentials and sensitive connection information should not be exposed in client-side interfaces or hard-coded into public application code. AIWA's application architecture should keep sensitive database operations in the appropriate server-side environment. Never paste database passwords, connection strings, or other private credentials into public-facing page content or expose them directly in frontend code. If a workflow requires credentials or secrets, use the appropriate secure configuration or connector flow provided by AIWA. ## Database vs authentication Your database and authentication solve different problems. **Database** Stores application information. Examples: * Customers * Projects * Orders * Bookings * Deals **Authentication** Determines who the user is. Examples: * Leon is signed in * Sarah is signed in * Marcus is signed in The two can work together. For example: > Show each user only the projects that belong to their account. Authentication tells the application who the user is. The database contains the projects and their ownership information. Application logic determines which records that user should be allowed to access. We'll cover authentication on the next page. ## Database vs application logic The database stores information, but it doesn't define the entire product experience. Suppose you have: ```text theme={null} Deal ├── Value ├── Stage └── Expected Closing Date ``` Your application logic might define: > When a deal moves to Closed Won, record the completion date and add its value to the won revenue metric. The database stores the information. The application logic determines what should happen. AIWA can work across both. ## You can be technical if you want AIWA allows you to describe requirements at the level you're comfortable with. A non-technical user might say: > Every customer should be able to have multiple projects. A developer might provide more explicit requirements about: * Data relationships * Field types * Validation * Indexes * Constraints * Queries * API behavior * Migration requirements Both approaches can be useful. You don't need to become a database engineer to build database-backed products with AIWA, but technical users can still provide detailed direction when needed. ## Example prompts Here are some examples of natural-language requests that require database functionality. **Booking application** > Customers should be able to book appointments. Store the customer, service, staff member, appointment date, time, and booking status. **CRM** > Add leads with name, email, phone, company, source, status, assigned agent, estimated value, and notes. **Project management** > Each workspace should have projects. Projects should contain tasks, and tasks can be assigned to workspace members. **E-commerce** > Store products, customers, orders, and order items. Customers should be able to view their previous orders after signing in. **Property platform** > Allow agents to create property listings with title, location, price, property type, bedrooms, bathrooms, description, and listing status. You describe the product requirement. AIWA handles the database-backed implementation required to support it. ## The principle You shouldn't have to start product development by designing database tables. Start with: > What information does my product need? Then: > How should that information relate? Then: > What should users be able to do with it? AIWA can help translate those answers into a working Neon-backed application. ## Next: Authentication Your database gives your application persistent information. But many applications also need to know: **Who is using the application?** Next, we'll look at Authentication: how AIWA can add Google and email/password sign-in, protect application areas, and build experiences around authenticated users. Add Google and email/password sign-in and protect application areas. # Adding Forms, Uploads, Email & Payments Source: https://docs.aiwa.codes/builds/forms-uploads-email-payments Describe the workflows behind forms, file uploads, email, and payments so AIWA connects your app to real, real-world outcomes. Modern applications do more than display information. They collect data, accept files, send messages, process payments, and trigger actions based on what users do. With AIWA, you can describe these workflows in natural language and have your AI product team build the functionality into your application. **Don't just describe the interface. Describe what should happen.** ## Build the workflow, not just the screen AIWA Form Consider this prompt: > Add a contact form with name, email, phone number, and message. That tells AIWA what the form should look like. But what should happen after someone submits it? A stronger request is: > Add a contact form with name, email, phone number, and message. Save every enquiry to the database, show it in the admin dashboard, send a confirmation email to the customer, and notify our team when a new enquiry arrives. On a simple website, a form without any further instructions emails each submission to you through Resend rather than storing it. Asking AIWA to save submissions, as in the stronger request above, gives your project a database. Now you're describing a complete workflow: ```text theme={null} Customer submits form ↓ Validate information ↓ Save enquiry ↓ Show in dashboard ↓ Send confirmation ↓ Notify team ``` AIWA can build the different pieces required to make that workflow work. ## Forms Forms allow users to send information into your application. They can be used for: * Contact enquiries * Lead capture * Customer onboarding * Booking requests * Account settings * Surveys * Applications * Checkout * Support requests * Creating and editing records You can describe the information you want to collect and what should happen afterward. ### Creating a form For example: > Add a lead capture form with name, work email, phone number, company name, company size, and message. Name and email are required. AIWA can create the appropriate fields, validation, and interface. But for a real application, you should also describe what should happen to the submission. For example: > Save every submission as a lead in the database and show new leads in the sales dashboard. Now the form is connected to your application. ### Form validation Validation determines what information is acceptable before a form is processed. For example: > Name and email are required. Validate that the email address is correctly formatted and show an inline error beneath invalid fields. Or: > Passwords must contain at least 8 characters. Or: > The booking date cannot be in the past. AIWA can implement validation around the requirements you describe. A useful prompt includes both: **What information is required** and **what makes that information valid.** ### Success and error states Don't forget what happens after submission. For example: > After successful submission, clear the form and show a success message saying "Thanks! We'll get back to you shortly." Also consider failure: > If submission fails, keep the user's entered information and show an error message with an option to try again. Good application experiences account for both outcomes. ## File Uploads Some applications need users to upload files. Examples include: * Profile photos * Property images * Documents * PDFs * Product images * Receipts * Attachments * Portfolio files You can describe the upload experience you want. For example: > Allow real estate agents to upload multiple images when creating a property listing. Display the images in a gallery on the property detail page. Or: > Allow customers to attach PDF, DOCX, JPG, and PNG files to support tickets. ### Describe upload restrictions For uploads, tell AIWA about any important restrictions. For example: > Allow up to 10 property images per listing. Accept JPG, PNG, and WebP files and limit each file to 10 MB. Or: > Only accept PDF documents up to 20 MB. This gives AIWA clearer requirements for validation and user feedback. ### File storage Files generally shouldn't be stored directly inside your application's relational database. Instead, applications commonly use dedicated media or file-storage services and store references to those files in the database. AIWA supports [connectors such as Cloudinary](/integrations/cloudinary) for workflows involving media storage and delivery. For example: ```text theme={null} User selects image ↓ Application validates file ↓ Image uploaded to Cloudinary ↓ File reference saved ↓ Image displayed in application ``` We'll cover Cloudinary setup in detail in the Integrations section. Some external functionality requires you to connect the appropriate service or credentials before AIWA can use it in your application. ## Email Applications frequently need to send emails based on user actions. Examples include: * Welcome emails * Booking confirmations * Contact-form notifications * Order confirmations * Team invitations * Password-related messages * Status updates * Transactional notifications AIWA can build email workflows using supported email integrations such as [Resend](/integrations/resend). ### Describe when an email should be sent Instead of simply saying: > Add email. Describe the event. For example: > When a customer successfully books an appointment, send them a confirmation email containing the service, staff member, date, time, and booking reference. That's much clearer. Conceptually: ```text theme={null} Booking created ↓ Save booking ↓ Send confirmation email ↓ Display success state ``` ### Send emails to your team Email isn't only for customers. For example: > When someone submits the demo request form, save the lead and email our sales team with the person's name, email, company, and message. Or: > Notify the assigned agent whenever a new lead is assigned to them. AIWA can connect application events to email workflows. ### [Connect Resend](/integrations/resend) For applications that send transactional emails, you can connect Resend through AIWA's supported integration flow. Once configured, you can focus your prompts on what should happen. For example: > Send a welcome email after registration. Rather than manually implementing the entire email delivery workflow yourself. We'll walk through connecting Resend later in the Integrations section. ## Payments You can also build payment experiences into your application. AIWA supports [Stripe](/integrations/stripe) for payment workflows. This allows you to build experiences such as: * One-time purchases * Subscription checkout * SaaS plans * Customer billing * Upgrades * Payment status * Billing portal access You describe how payments should fit into your product. ### One-time payments For example: > Customers should be able to purchase this digital course for \$99 using Stripe. After successful payment, give the customer access to the course dashboard. This involves more than displaying a payment button. Conceptually: ```text theme={null} Customer chooses product ↓ Stripe checkout ↓ Payment succeeds ↓ Application verifies payment ↓ Access granted ``` AIWA can build the application workflow around the payment process. ### Subscription payments For SaaS applications, you might need recurring subscriptions. For example: > Add three subscription plans: Starter at \$19/month, Pro at \$49/month, and Business at \$99/month. Users should choose a plan during checkout and their account should reflect their active subscription afterward. For more sophisticated billing systems, you may also need: * Upgrades * Downgrades * Cancellations * Failed payment handling * Subscription status * Billing history * Customer portal access * Feature restrictions For these cases, consider using Plan Mode before implementation. ### Payments are more than checkout A common mistake is thinking that adding Stripe means simply creating a checkout page. A real subscription workflow may look more like: ```text theme={null} User selects Pro ↓ Checkout created ↓ Stripe processes payment ↓ Payment confirmed ↓ Subscription recorded ↓ Pro features unlocked ↓ Dashboard updated ``` Your application needs to know what happened after the user leaves Stripe. That's why payment workflows often involve both Stripe and your application's backend. Don't unlock paid functionality simply because a user reached a success page. Payment status should be verified using the appropriate server-side Stripe workflow. ## Combine capabilities into workflows The real power comes from combining these capabilities. Imagine you're building a photography booking platform. You could tell AIWA: > Customers should complete a booking form, choose a photography package, upload reference images, pay a 30% deposit through Stripe, and receive a confirmation email after successful payment. Save the booking in the admin dashboard with a "Deposit Paid" status. That single product workflow involves: **Form** Collect booking details. ↓ **Upload** Store reference images. ↓ **Stripe** Collect the deposit. ↓ **Database** Save the booking and payment state. ↓ **Resend** Send confirmation. ↓ **Dashboard** Show the booking to the photographer. You're describing the customer experience. AIWA can help build the systems behind it. ## Another example: Lead qualification Suppose you're building an agency website. You could ask: > Create a "Request a Proposal" form. Ask for name, company, email, website, monthly marketing budget, services needed, and project description. Save submissions as leads. If the budget is above \$5,000, mark the lead as High Priority and notify the sales team by email. Conceptually: ```text theme={null} Proposal submitted ↓ Save lead ↓ Check budget ↓ Above $5,000? ↙ ↘ Yes No ↓ ↓ High Priority Standard ↓ Notify sales ``` This is application logic created around a form. ## Describe the complete outcome When prompting AIWA, think beyond the visible component. Instead of: > Add an application form. Try: > Add an application form collecting name, email, LinkedIn profile, years of experience, role, and CV. CV should accept PDF files only. Save applications in the database and show them in the admin dashboard. Send the applicant a confirmation email after successful submission. Instead of: > Add a Buy button. Try: > Add a Buy button that starts Stripe checkout. After successful payment, record the purchase and unlock the customer's download inside their account. The more clearly you describe the outcome, the better AIWA can understand the complete workflow. ## External services require connectors AIWA can build the application logic around external services, but those services still belong to their respective providers. For example: | Capability | Service | | - | - | | Payments | [Stripe](/integrations/stripe) | | Transactional email | [Resend](/integrations/resend) | | Communications | [Twilio](/integrations/twilio) | | Media | [Cloudinary](/integrations/cloudinary) | You'll generally need to connect the appropriate account or credentials before the application can use that external service. AIWA's Connectors make this process easier. We'll cover each supported connector individually later. ## Keep credentials secure External integrations frequently require API keys or other credentials. These values should be treated as secrets. Never expose Stripe secret keys, Resend API keys, Cloudinary secrets, or other private credentials directly in public frontend code. Use AIWA's supported connector or secure configuration flows when adding credentials. Once connected, your prompts can focus on the product behavior rather than repeatedly supplying credentials. ## Choose the right mode Simple workflows can often go directly to Build Mode. For example: > Add a contact form and save submissions to the database. Build + Min may be sufficient. More complex workflows deserve planning. For example: > Add subscriptions with three plans, feature limits, upgrades, downgrades, cancellations, failed-payment handling, and a customer billing portal. Consider: **Plan + Max → Review → Build** This allows AIWA to reason through the complete billing architecture before implementation. ## Example prompts **Contact form** > Create a contact form with name, email, company, and message. Save submissions and show a success message afterward. **Upload** > Allow users to upload a profile image. Accept JPG, PNG, and WebP and show the uploaded image on their profile. **Email** > Send customers an email confirmation after successfully booking an appointment. **Payment** > Add Stripe checkout for the Pro plan at \$49/month and update the user's subscription after successful payment. **Complete workflow** > Build a consultation booking flow. Customers should choose a service, select an available date and time, enter their contact details, pay the consultation fee through Stripe, and receive an email confirmation. Save the booking and payment status in the database. ## Think in outcomes You don't need to tell AIWA every technical step required to implement a workflow. Start with: > What should the user be able to do? Then: > What should happen when they do it? And finally: > What information should the application remember? For example: * A customer books an appointment. * The booking should be saved. * Payment should be collected. * The customer should receive confirmation. * The business should see the booking in its dashboard. That's a product workflow. AIWA can help turn it into working software. ## Next: APIs and Server-Side Logic Forms collect information. Databases store it. Integrations connect your application to external services. But something still needs to determine what happens when users perform actions. Next, we'll look at APIs and Server-Side Logic: the functionality behind your application's buttons, workflows, permissions, calculations, and integrations. See how AIWA builds the logic behind buttons, workflows, and integrations. # Managing Your Project Data Source: https://docs.aiwa.codes/builds/managing-project-data Organize, search, filter, and safely change the data your users create with the interfaces and rules AIWA builds around your database. Once people begin using your application, they create data. Customers sign up. Leads are added. Orders are placed. Appointments are booked. Projects are created. Deals move through pipelines. AIWA helps you build applications that don't just collect this information. They can organize, retrieve, update, filter, analyze, and protect it. **Your application's data is part of your product. AIWA helps you build the experiences that make that data useful.** ## What is project data? Project data is the information created and used by your application. For a CRM, this might include: * Leads * Contacts * Deals * Follow-ups * Notes * Activities * Team members For a booking application: * Customers * Services * Staff * Appointments * Availability * Payments For an e-commerce application: * Customers * Products * Orders * Order items * Addresses * Payments This information is stored in your project's database and used throughout the application. ## Data vs content It's useful to distinguish between application data and normal website content. A homepage headline such as: > Build your dream home with confidence. is primarily website content. A customer record such as: ```text theme={null} Name: Sarah Chen Email: sarah@example.com Plan: Pro Status: Active ``` is application data. Application data is usually dynamic. It changes as people use your product. ## AIWA can build interfaces for your data Your users shouldn't need to interact directly with a database. Instead, AIWA can create interfaces that allow them to work with the information stored by your application. For example, a Leads page might provide: * Search * Filters * Sorting * Pagination * Create Lead * Edit Lead * Delete Lead * Status changes * Assigned agents The interface becomes the user's way of working with the underlying data. Conceptually: ```text theme={null} USER ↓ APPLICATION INTERFACE ↓ SERVER-SIDE LOGIC ↓ NEON POSTGRES ``` ## Creating data You can tell AIWA how users should create records. For example: > Add a Create Lead button. The form should collect name, email, phone, source, status, assigned agent, budget, and notes. When the user submits the form, the application can validate the information and save the new lead. The user doesn't need to know anything about the underlying database operation. ## Viewing data Once information exists, users need useful ways to view it. For example: > Create a Customers page showing name, company, email, plan, account status, and signup date. Or: > Show all properties in a card grid with image, property name, location, price, type, and listing status. Different data may need different presentations. AIWA can build: * Tables * Cards * Lists * Detail pages * Kanban boards * Calendars * Dashboards * Charts based on how users need to interact with the information. ## Searching and filtering Applications become harder to use as the amount of data grows. Imagine a CRM with 10 leads. A simple list may be enough. Now imagine it has 10,000. Users need ways to find what matters. You could ask: > Add search to the Leads page. Users should be able to search by name, email, phone number, or company. Then: > Add filters for lead status, source, assigned agent, and date created. Or: > Allow users to show only deals expected to close this month. AIWA can build these data-management experiences into your application. ## Sorting Users may also need to control how records are ordered. For example: > Allow the customer table to be sorted by name, signup date, and total revenue. Or: > Sort upcoming appointments by date and time, with the earliest appointment first. Or: > Show the highest-value deals first. Describe the experience you want rather than worrying about how the database query should be written. ## Pagination Loading thousands of records at once can create unnecessary performance problems. Applications commonly divide large collections into smaller sets of results. For example: ```text theme={null} Showing 1-25 of 2,418 leads ← Previous 1 2 3 4 5 Next → ``` This is called pagination. For larger datasets, AIWA can build appropriate pagination or incremental-loading behavior. Technical users can also specify exactly how they want pagination implemented. ## Detail Pages Lists help users find records. Detail pages help them understand individual records. For example, selecting a lead might open: ```text theme={null} Sarah Chen Status Qualified Budget $850,000 Assigned Agent Marcus Property Interest 3-bedroom home Follow-ups 3 Recent Activity ... ``` You can ask AIWA: > Create a lead detail page showing contact information, status, assigned agent, budget, notes, follow-ups, associated deals, and recent activity. AIWA can retrieve and combine the appropriate project data for that experience. ## Editing data Most applications need users to update existing records. For example: > Allow agents to edit a lead's contact information, status, budget, assigned agent, and notes. Or: > Customers should be able to update their billing address from Account Settings. When the user saves the changes, the application can update the corresponding data in Neon. ## Think about who can edit what Not every authenticated user should necessarily be allowed to change every record. For example: > Agents can update leads assigned to them. Admins can update any lead in the workspace. Or: > Customers can update their own profile but cannot edit another customer's information. This is where project data, authentication, and authorization work together. ## Deleting Data Deletion deserves special consideration because it can be destructive. A simple application might allow: > Delete this note. But deleting a customer could affect: ```text theme={null} Customer ↓ Projects ↓ Tasks ↓ Comments ``` What should happen to all the related information? That decision should be intentional. ## Define deletion behavior For important records, tell AIWA what should happen. For example: > Users can delete draft invoices, but paid invoices should never be permanently deleted. Or: > When an administrator deletes a project, delete its tasks and comments as well, but don't delete the customer. Or: > Don't permanently delete customers. Archive them instead. These are product decisions, not merely database decisions. Be careful when changing deletion behavior in an application containing real customer or production data. Destructive database operations may be irreversible. ## Consider archiving instead Sometimes information shouldn't be permanently deleted. You may prefer: **Active → Archived** rather than: **Record → Permanently Deleted** For example: > Allow users to archive completed projects. Archived projects should disappear from the default Projects view but remain accessible through an Archived filter. This preserves historical information while keeping the main interface clean. ## Data Relationships Your application's data often becomes more useful when different records are connected. For example: ```text theme={null} CUSTOMER ↓ PROJECT ↓ TASK ↓ COMMENT ``` Or: ```text theme={null} LEAD ↓ DEAL ↙ ↘ AGENT PROPERTY ``` These relationships allow AIWA to create richer experiences. For example: > On the customer detail page, show all projects belonging to that customer. Or: > On the property detail page, show all deals associated with the property. Or: > Show every task assigned to the currently signed-in user. ## Don't duplicate information unnecessarily Suppose a project belongs to a customer. Instead of storing the customer's full details separately inside every project, the application can connect the project to the existing customer record. Conceptually: ```text theme={null} Customer ID: 124 ↓ Project Customer: 124 ``` This makes it easier to maintain consistent information as your application grows. AIWA can design these relationships based on your product requirements. ## Dashboard Data Project data can also power dashboards and reports. For example: > Show total customers, active subscriptions, MRR, new customers this month, and churned customers. Or: > Show total pipeline value grouped by deal stage. Or: > Show appointments today and compare this week's bookings with last week. Conceptually: ```text theme={null} APPLICATION DATA ↓ Filter + Calculate ↓ METRICS ↓ DASHBOARD ``` Your dashboard becomes a representation of real application activity. ## Keep metrics dynamic When building a real application, make it clear when dashboard numbers should come from the database. For example: > Replace the placeholder dashboard metrics with live values calculated from the current workspace's data. This prevents a production dashboard from continuing to display decorative sample numbers. ## Empty States Your application also needs to work when there is no data yet. Imagine a new customer creates an account and reaches: ```text theme={null} Total Leads: 0 Deals: 0 Pipeline: $0 ``` Simply displaying an empty table isn't always the best experience. Instead: > You don't have any leads yet. > > Add your first lead to start building your pipeline. > > \[Add your first lead] This is called an empty state. You can ask AIWA to create useful empty states throughout the application. ## Design for the first user When building data-heavy applications, test what happens before any records exist. Ask: * What does the dashboard show? * What does an empty table look like? * Is there a clear next action? * Does the user understand what to do? * Are charts empty or broken? For example: > Add designed empty states to Leads, Properties, Deals, and Follow-ups. Each empty state should explain the feature and provide a clear CTA for creating the first record. This improves the experience for new users. ## Loading States Data isn't always available instantly. While your application retrieves information, users should understand that something is happening. Instead of briefly showing: ```text theme={null} 0 Leads ``` before the actual data appears, the application might show a loading state. For example: ```text theme={null} ████████████ ████████ ██████████████ ``` Skeletons, progress indicators, or other loading patterns can help make data-driven interfaces feel more polished. ## Error States Sometimes data can't be loaded. A useful application should communicate this clearly. For example: > We couldn't load your leads. > > \[Try again] Rather than showing a broken page. You can ask AIWA: > Add loading, empty, and error states to the customer table. If loading fails, show an inline error with a Retry button. ## Working with production data Once real users are using your application, database changes deserve more care. Adding a new field is very different from deleting a table containing customer information. Before significant structural changes, tell AIWA that the application contains real data. For example: > This application is now in production and contains customer data. We need to change the relationship between customers and organizations. Analyze the existing database and create a safe migration plan before making any changes. This is a good use case for Plan + Max. Treat production database changes differently from changes to a new prototype. Preserve existing data unless you intentionally want it removed. ## Test with realistic data Sample data can help you understand how an application behaves before real customers arrive. For example, a CRM might include realistic examples across: * Different statuses * Different agents * Different deal values * Different dates * Completed and overdue follow-ups This allows you to test filters, dashboards, tables, charts, and workflows more realistically. But sample data should be clearly distinguishable from real production information. ## Ask AIWA questions about your data model You can also use AIWA to help understand the application you're building. For example: > Explain how customers, projects, tasks, and users currently relate in this application. Don't make any changes. Or: > Analyze the current database structure and identify whether anything would prevent a customer from having multiple projects. This can be particularly useful before making significant changes. Explore or Plan Mode can help when you want analysis before implementation. ## Data Security Your application's data may include private customer or business information. The application should therefore enforce appropriate access rules. For example: > Users must only be able to access data belonging to their workspace. Or: > Customers should only see orders associated with their own account. Or: > Only administrators should be able to access the complete customer directory. These rules should be enforced in the application's backend, not only through the visible interface. ## Think in ownership For private application data, ask: **Who owns this record?** For example: ```text theme={null} Workspace ↓ Project ``` or: ```text theme={null} Customer ↓ Order ``` or: ```text theme={null} User ↓ Private Document ``` Then define who should be able to access it. This becomes particularly important for multi-tenant applications. ## Example: Managing CRM Data Suppose you're building a real estate CRM. Your application contains: ```text theme={null} Workspace │ ├── Agents ├── Leads ├── Properties ├── Deals └── Follow-ups ``` You might tell AIWA: > Every CRM record must belong to a workspace. Users should only see data belonging to workspaces where they're members. Then: > Add search, filters, sorting, and pagination to Leads. Then: > Allow agents to archive lost leads instead of permanently deleting them. Then: > Show pipeline value by deal stage on the dashboard. Then: > Add an activity history to each lead showing important changes. You're progressively turning raw stored information into a complete data-management experience. ## Example: Customer Portal Imagine a customer portal containing: ```text theme={null} Customer │ ├── Projects ├── Files ├── Invoices └── Messages ``` You could define: > After signing in, customers should only see records associated with their own account. Then: > Show active projects first and allow completed projects to be viewed through an archive. Then: > Allow customers to search their files by filename and project. Then: > Show unpaid invoices at the top of the Billing page. The database provides the information. AIWA builds the experience around it. ## A useful data checklist When building a data-driven feature, think about: **What information exists?** Leads, customers, bookings, orders... **How is it created?** Form, import, payment, automated process... **Who can see it?** Owner, team, customer, administrator... **Who can change it?** Everyone, assigned users, admins only... **How is it organized?** Search, filters, sorting, pagination... **What is it connected to?** Customer → Project → Task **What happens when it's deleted?** Permanent deletion, archive, cascade... **What happens when there is no data?** Empty state. **What happens while loading?** Loading state. **What happens when loading fails?** Error state. These questions help turn a database-backed feature into a complete product experience. ## You manage the product, not the database server AIWA's goal isn't to require every founder, marketer, designer, or business owner to become a database administrator. You define: * What information your product needs. * How users should interact with it. * Who should have access. * What rules should apply. AIWA helps translate those decisions into the application. And because AIWA uses Neon Postgres, your dynamic application can have a real relational database behind the experiences you're building. ## What AIWA Builds, in summary You now understand the major systems AIWA can build behind your application: **Database** Persistent application data powered by Neon Postgres. **Authentication** Google and email/password user identity. **Forms & Uploads** Ways for users to provide information and files. **Email & Payments** External workflows powered through integrations. **APIs & Server-Side Logic** The rules and functionality behind your application. **Project Data** The information your users create and how your product works with it. Together, these systems allow AIWA to go beyond generating interfaces and help you build full-stack applications. ## Next: Integrations (Connectors) Some capabilities depend on services outside AIWA. Payments need Stripe or PayPal. Transactional email can use Resend. Communications can use Twilio. Media can use Cloudinary. AI features can connect to providers such as OpenAI, Anthropic, Google, and xAI. In the next section, we'll cover AIWA Connectors, starting with what connectors are, how they work, and how AIWA handles the credentials required to connect external services. Learn what AIWA connectors are and how your keys are stored. # Create Your First Project Source: https://docs.aiwa.codes/getting-started/create-your-first-project Start a new AIWA project from the dashboard by describing what you want to build, and open your workspace to keep iterating. Your AIWA project is the workspace where your application is built, improved, and managed. You can start a new project directly from the AIWA dashboard by describing what you want to create. ## Start from the dashboard When you sign in to AIWA, you'll see the main project dashboard. The large prompt box is where new projects begin. AIWA Dashboard From here, you can describe the product you want AIWA to create. You can build things like: * Business websites * SaaS applications * Customer portals * Internal tools * Dashboards * Marketplaces * Booking platforms * AI-powered applications * Custom web applications You don't need to create files, configure a development environment, or choose a technical architecture before getting started. ## Describe what you want to build Enter a description of your project into the prompt box. For example: > Build a world-class construction website. The website should have all the navigations a construction website should have. Use professional and very clean images. AIWA Create Project AIWA uses your description to understand the product you want to create and determine how to approach the build. Don't worry about writing the perfect prompt yet. A clear description of what you want to build is enough to get started. We'll cover writing effective prompts in the next guide. ## Choose your AI model Before starting the project, you can choose the AIWA model you want to work with. Depending on your account and available options, you'll see AIWA's model selector beside the prompt box. Different models are designed for different levels of speed and reasoning. For most projects, you can start with the default selection. We'll explain **AIWA Min and AIWA Max** and when to use each later in the documentation. ## Choose Build or Plan You can also choose how AIWA should approach your request. **Build** is designed for when you want AIWA to move from your request into implementation. **Plan** is useful when you want AIWA to structure and review the approach before building. AIWA Plan & Build Modes For your first project, you can leave Build selected. ## Start the project Once you're happy with your prompt, click the arrow button to submit it. AIWA will create the project and begin working on your request. Depending on the complexity of what you're building, AIWA may analyze requirements, create or modify files, set up functionality, and prepare the application for preview. You can follow the progress from inside the project workspace. ## Your project workspace Once your project is created, AIWA opens the project workspace. This is where you'll continue working with AIWA. AIWA Live Preview From here, you can: * Preview your application * Continue chatting with AIWA * Request changes * Add features * Review generated work * Work with your project files * Test your application * Publish when you're ready You don't need to create a new project every time you want to change something. Continue working inside the existing project and tell AIWA what you want to do next. ## Keep building Your initial project is only the starting point. After AIWA creates the first version, you might say: > Add a page showing our completed construction projects. Then: > Add a quote request form to the Contact page. Then: > Create an admin dashboard where we can manage quote requests. Each request continues evolving the same application. AIWA is designed around continuous product development. Keep working with the same project as your application grows rather than starting over for every new feature. ## Next: Your first prompt You've created your first project. Next, learn what information to include in your first prompt so AIWA can better understand what you want to build. Learn how to write a prompt AIWA can build from confidently. # How AIWA Works Source: https://docs.aiwa.codes/getting-started/how-aiwa-works Understand the plan, build, review, and iterate loop that AIWA uses to turn your ideas into working, publishable software. AIWA turns your ideas into working software through an AI-powered product development workflow. Instead of generating an application in a single step and leaving you with the result, AIWA works through a continuous process of understanding what you want, planning the implementation, building it, and helping you improve it. At its simplest, the workflow looks like this: > **Plan → Build → Review → Iterate** ## 1. Tell AIWA what you want to create Everything starts with a conversation. Describe the website, application, feature, or change you want AIWA to create. For example: > Build a world-class construction website. The website should have all the navigations a construction website should have. Use professional and very clean images. AIWA Create Project You don't need to describe every technical detail. AIWA interprets your request and determines what needs to be created. Your first prompt doesn't have to be perfect. You can continue refining your application as you build. ## 2. Plan For more complex builds, AIWA can plan the product before writing the implementation. The planning process turns your request into a structured specification that AIWA can use to understand what it needs to build. Depending on the project, this can include: * Product intent * Pages and features * User flows * Data requirements * Backend functionality * Technical requirements * Integrations AIWA can also audit and refine the plan before implementation. AIWA Project Plan This gives you visibility into what AIWA intends to create before the full build begins. You can use **Plan mode** when you want to review the approach before AIWA makes changes. We'll cover Plan mode in detail later in this documentation. ## 3. Build Once the direction is clear, AIWA turns the plan into a working application. AIWA handles the implementation across the product, including the interface, application logic, pages, data requirements, and other functionality required by your project. You can watch the application take shape inside the AIWA workspace and preview the result as it develops. AIWA Live Preview You don't need to manually translate the plan into code. AIWA handles the implementation for you. ## 4. Review When AIWA completes a build, you can review the result directly in the workspace. Check the application visually and interact with it just like a user would. You might discover that you want to: * Change part of the design * Adjust some content * Add another page * Change how a feature works * Add functionality * Fix an issue You don't need to start over. Simply tell AIWA what you want changed. ## 5. Iterate This is where AIWA becomes more than a one-time app generator. Your project remains something you can continue working on. For example, you might start with: > Build a booking website for a fitness studio. Then later ask: > Add customer accounts and allow users to manage their bookings. And later: > Add monthly memberships with online payments and an admin dashboard. AIWA continues working on the same product as your requirements evolve. Your first build is the beginning, not the finished product. ## The AIWA development loop AIWA understands your idea and determines what needs to be built. AIWA turns the plan into a working application. Preview and test what AIWA created. Tell AIWA what you want changed, improved, fixed, or added. You can repeat this loop as many times as necessary: **Plan → Build → Review → Iterate → Build → Review → Iterate** This is how an initial idea can gradually become a complete product. ## You stay in control AIWA handles much of the technical implementation, but you remain in control of the product. You decide what to build, review what AIWA creates, provide feedback, and determine what happens next. For quick changes, you can ask AIWA to build immediately. For larger changes, you can plan them first and review the approach before implementation begins. This lets you move quickly when the task is simple while taking a more structured approach when the product becomes complex. ## From idea to live product Building is only part of the AIWA workflow. Once your application is ready, AIWA can publish it to a live URL so other people can use it. And publishing doesn't end development. You can return to the project, continue making changes with AIWA, and publish improved versions as your product evolves. We'll walk through creating and publishing a project step-by-step in the next few guides. ## Next: Create your first project Now that you understand how AIWA works, let's create your first project and see the workflow in action. Start building with AIWA in a few minutes. # Publish Your First Project Source: https://docs.aiwa.codes/getting-started/publish-your-first-project Deploy your AIWA application to a live URL, test it in production, and keep improving it with continuous updates. Once you're happy with your application, you can publish it directly from AIWA and make it accessible on the web. AIWA handles the hosting and deployment process for you, so you don't need to configure a server or external hosting provider to get your first project online. In this guide, you'll publish your first project and open the live version. ## Before you publish Before publishing, take a moment to review your application in the AIWA preview. Check the important parts of your project, including: * Navigation and links * Page content * Forms and buttons * Mobile responsiveness * Authentication, if your app uses it * Important application workflows You don't need your application to be perfect before publishing. You can continue making changes and publish updated versions later. Publishing doesn't end your AIWA project. You can continue building, improving, and republishing your application after it goes live. ## 1. Click Publish When you're ready, click **Publish** in the top-right area of your AIWA project workspace. This opens the publishing window for your project. AIWA Publish Settings AIWA will prepare the latest version of your application for deployment. ## 2. Review your publishing options Before deployment begins, review the information shown in the publishing window. Depending on your project and account, AIWA may display information about your deployment and live project URL. When you're ready, confirm the publish action. You don't need to purchase or configure a domain to publish your first project. AIWA provides hosting for published projects and gives your project a live URL. ## 3. Wait for deployment AIWA will now deploy your application. During this process, the application is prepared and made available in the live environment. You don't need to configure a server or manually upload your project files. Keep the project open while AIWA completes the deployment. ## 4. Your project is live When publishing is complete, AIWA will confirm that your application is live. AIWA Published App You can now open your application using its live URL. For example, your published project will have an AIWA-hosted URL similar to: ```text theme={null} your-project.aiwacodes.com ``` Your exact URL will depend on the project. ## 5. Open your live application Open the live URL and test the application outside the AIWA workspace. AIWA Published Preview This is the version visitors and users can access. Test the important parts of your application again in the live environment, especially: * Navigation * Forms * Authentication * Database-powered features * External integrations * Mobile layouts If you find something you'd like to change, return to AIWA and continue working on the project. ## Making changes after publishing Publishing doesn't lock your application. You can return to the project and tell AIWA what you want to improve. For example: > Add a testimonials section below the projects section. Or: > Change the Contact button in the navigation to Request a Quote. Or: > Improve the mobile layout of the Services section. AIWA can make the changes to your existing project. Once you're happy with the new version, publish again to update the live application. This creates a continuous development cycle: **Build → Preview → Publish → Learn → Improve → Publish again** ## Using your own domain Your AIWA URL is enough to get your application online, but you may eventually want to use your own domain. For example: ```text theme={null} www.yourcompany.com ``` [Custom domains](/publishing/custom-domains) are available on supported AIWA plans. Once connected, visitors can access your AIWA-hosted application through your own domain while AIWA continues to host the project. We'll cover domain setup step-by-step in **Publishing & Domains → Custom Domains**. ## Want to host the project yourself? AIWA provides hosting for your published projects, but you're not limited to AIWA hosting. If you need to manage your own infrastructure, you can export your project and deploy it elsewhere. For example, you may choose to: * Export your project code * Export your project to GitHub * Deploy the exported application to your own infrastructure or VPS Self-hosting requires you to manage the external hosting environment and deployment process yourself. ## You just shipped with AIWA 🎉 You've now gone from an idea to a live application. You told AIWA what you wanted to create. AIWA helped turn your idea into a working application. You previewed and refined the result. AIWA deployed your application to a live URL. And you're not finished. Return to your project whenever you want to add features, improve the experience, or continue evolving your product. ## What's next? You've completed the Getting Started section. Next, we'll go deeper into how to work effectively with your AI product team. Learn writing effective prompts, the four modes, AIWA Min vs Max, Project Memory, and iterating on your app. # Understanding the Interface Source: https://docs.aiwa.codes/getting-started/understanding-the-interface Tour the AIWA workspace, the chat area, preview, connectors, and settings you'll use to build, review, and manage your project. The AIWA interface brings everything you need to build, preview, manage, and publish your application into one workspace. This guide introduces the main areas you'll use while working on a project. Some options may vary depending on your AIWA plan or the features enabled for your account. ## The AIWA dashboard When you sign in to AIWA, you'll arrive at your dashboard. This is where you can start a new project, access existing projects, and continue working on applications you've already created. AIWA Dashboard The prompt box is the fastest way to start something new. Simply describe what you want to build and submit your prompt. The sidebar gives you quick access to the rest of AIWA: | Sidebar item | What it opens | | - | - | | **Home** | The prompt box and your recent projects | | **Search** | Find a project by name | | **Templates** | Finished apps you can open and remix as a starting point | | **Connectors** | The services you can connect, such as Stripe or Resend | | **All projects**, **Created by me**, **Shared with me** | Your project lists | If you're on the Agency plan, you'll also see **Agency console**, where you manage clients and your team. See [Agency console](/agency/console-overview). Look for the **Tutorial** or **Watch how** button on the home page, the Connectors pages, and the Domains section. It opens a short video walkthrough of that screen. ## The project workspace After creating or opening a project, you'll enter the AIWA project workspace. This is where most of your building happens. AIWA Live To Product The workspace is designed to let you communicate with AIWA while seeing the application you're building. As AIWA makes changes, you can review the result and continue giving instructions without leaving the project. ## Chat with your AI product team The conversation area is where you work with AIWA. You can use it to request new features, make changes, fix problems, or ask AIWA to improve something it has already created. For example: > Change the hero section to use a darker background and make the headline more prominent. Or: > Add a project gallery with filters for residential and commercial projects. Or: > Add a contact form that saves enquiries to the database. You don't need to create a new project for each request. Continue the conversation inside your existing project. ## Build and Plan Near the prompt area, you can choose how AIWA should approach your request. **Build** is used when you want AIWA to implement your request. **Plan** is used when you want AIWA to think through and structure the work before implementation. This is only an introduction. We'll cover AIWA's different working modes and when to use each one in **Building with AIWA**. ## AIWA Min and AIWA Max AIWA also lets you choose between different levels of AI reasoning for your work. **AIWA Min** is designed for faster work and straightforward tasks. **AIWA Max** is designed for tasks that benefit from deeper reasoning and more complex problem solving. For example, a simple text or design change may not require the same level of reasoning as architecting a multi-user SaaS application. You don't need to worry about choosing perfectly when you're getting started. We'll explain AIWA Min vs AIWA Max in detail later. ## Preview your application The preview lets you see what AIWA is building. Instead of waiting until the end of development, you can inspect your application as it evolves. AIWA Live To Product Use the preview to check things such as: * Page layout * Navigation * Content * Responsive behavior * Forms and interactions * Application workflows If something isn't how you want it, return to the conversation and tell AIWA what you'd like changed. This creates a simple loop: **Request → Build → Preview → Improve** ## Working with your project Your project contains the files and application structure AIWA creates as it builds. Depending on the workspace view and available tools, you can inspect the project while continuing to work with AIWA. For most users, you don't need to manually edit files to build successfully. You can simply describe the changes you want. Developers, however, can use the additional project controls when they want more visibility into the underlying application. ## Connectors Connectors allow your application to work with external services. Depending on what you're building, you may connect services for things like: * Payments * Email * SMS * AI models * File and image storage * Calendars * Other external services AIWA Connectors For example, if your application needs payments, you can connect Stripe and then ask AIWA to build the required payment experience. Each supported connector has its own setup guide in the [Integrations (Connectors)](/integrations/overview)section of these docs. ## The Control Panel Each project has a **Control Panel** for everything that isn't building: who can see the project, what's live, and how it's configured. AIWA Publish Settings | Section | What you do there | | - | - | | **Overview** | See the project's status and live address at a glance | | **Comments** | Read and resolve feedback left on the project | | **Releases** | See every deployment and roll the live site back | | **People** | Invite people to the project and manage access | | **Assets** | Review the images used in the project | | **Domains** | Connect a custom domain | | **SEO** | Set the title, description, and social sharing details | | **Analytics** | See visits to your published site | | **Connectors** | See which services the project uses | Some sections depend on your plan or role. You generally won't need to change anything here when creating your first application. ## Account settings Your account settings, available from the workspace menu, are separate from any one project: * **Account**: your name, email, and sign-in details * **Appearance**: zoom, reduced motion, a sound when a build finishes, documentation tips, and whether opening a project in a new tab goes to the live site or the preview * **Plan & usage**: your plan, credit balance, upgrades, and billing * **Team**: invite teammates to your workspace * **Telegram**: link Telegram to build by chat, on the Agency plan (see [Telegram](/agency/telegram)) ## Publish When your application is ready, the Publish control takes it from your workspace to a live environment. Publishing gives you a live version of the application that can be accessed outside AIWA. We won't publish just yet, that's what we'll do on the next page. ## You don't need to learn everything at once The AIWA workspace contains tools for simple websites as well as more sophisticated applications. You don't need to understand every control before you start. For your first project, remember these four things: Tell AIWA what you want to create or change. Let AIWA work on your application. Review and interact with what AIWA created. Give AIWA your next instruction and keep improving the product. As you build more advanced applications, the rest of the interface will become increasingly useful. ## Next: Publish your first project You've created a project, written your first prompt, and learned your way around the AIWA workspace. Next, let's put your application online with Publish Your First Project. Take your application from the workspace to a live URL. # What is AIWA? Source: https://docs.aiwa.codes/getting-started/what-is-aiwa AIWA is an AI product team that helps you build, launch, and evolve websites and applications by describing what you want in natural language. AIWA is an AI product team that helps you build, launch, and evolve your websites, web applications, and software products by describing what you want to create. Instead of manually writing every line of code, designing every screen, configuring your backend, and handling deployment separately, you work with AIWA through natural language. Tell AIWA what you want to build, and it helps you plan, design, build, refine, and publish your product. > Think of AIWA as an AI-powered product team, available whenever you're ready to build. AIWA Dashboard ## What can you build with AIWA? AIWA can build much more than simple landing pages. You can use it to create: * Business websites and landing pages * SaaS applications * Dashboards and admin panels * CRM systems * Client portals * Marketplaces * Booking and scheduling applications * Membership platforms * Internal business tools * AI-powered applications * Custom web applications Whether you're launching your own product or building for a client, you can take an idea from a simple prompt to a working application inside AIWA. ## How AIWA works Building starts with a prompt. For example: > Build a world-class construction website. The website should have all the navigations a construction website should have. Use professional and very clean images. From there, AIWA can analyze your request, plan the product, create the interface and functionality, and give you a working application you can continue refining through conversation. The basic workflow is: Tell AIWA what you want to build in plain language. You don't need to write a technical specification before getting started. For more complex projects, AIWA can create and audit a product plan before writing the application. This gives you an opportunity to review the proposed structure and requirements before building. AIWA turns the requirements into a working product, creating the necessary pages, components, functionality, and application logic. Continue talking to AIWA to make changes. For example: > Add a testimonials section to the homepage. or: > Create an admin dashboard where I can manage customer enquiries. AIWA works with the existing project rather than requiring you to start over. When you're ready, publish your project directly from AIWA. Your application receives a live AIWA URL, and supported plans can connect a custom domain. ## AIWA is your AI product team Building software has traditionally required a team of specialists. A typical product team includes: * **Product managers** who define requirements * **Designers** who create user experiences * **Frontend developers** who build interfaces * **Backend developers** who create functionality * **Engineers** who connect systems and deploy applications AIWA brings these capabilities together into one AI-powered workspace. Instead of managing multiple tools and teams, you can collaborate with AIWA throughout the entire product development process. ## From idea to evolving product AIWA doesn't just generate your first version and stop. Your application can continue evolving as your ideas change. You can ask AIWA to: * Add new features * Improve user experiences * Create new pages * Connect external services * Modify existing workflows * Add databases and functionality * Fix issues and refine your application Your first prompt is only the beginning. AIWA helps you continuously improve your product as you learn from users and discover new opportunities. ## Your application grows with you Traditional development often requires returning to developers every time you want to make a change. With AIWA, your application becomes something you can continuously build on. For example: Build a booking website for a fitness studio. AIWA creates the first version. Add membership subscriptions, customer profiles, and an admin dashboard. AIWA evolves the application. Add AI recommendations and automated customer follow-ups. AIWA continues extending the product. Your application grows as your business grows. ## Why this matters AIWA is designed for the future of software development. The future is not just generating code faster. The future is having an intelligent partner that understands your product, helps you make decisions, and accelerates every stage of building software. ## Frontend and backend AIWA isn't limited to generating the visual interface of your application. It can help build applications that require: Pages, layouts, navigation, forms, dashboards, responsive interfaces, animations, and other user-facing experiences. Authentication, databases, APIs, application logic, data storage, and other functionality required by dynamic applications. This allows you to build products where users can sign in, create and retrieve data, interact with dashboards, submit information, and perform real application workflows. ## Connect your favorite services AIWA can also build applications that work with external services. Supported connectors and integrations include services for: * AI models * Payments * Email * SMS * File and image uploads * Calendars and scheduling * Databases * Other APIs For example, you could ask AIWA to build a SaaS application that accepts payments through Stripe, sends transactional emails through Resend, and uses an AI model for an AI-powered feature. You provide the required credentials, and AIWA writes the application code needed to work with the service. ## Build Mode and Plan Mode AIWA gives you two ways to approach a project. Use Build Mode when you want AIWA to start building immediately. This works well for straightforward projects or when you already know what you want. Use Plan Mode when you want AIWA to think through the product before implementation. AIWA creates a structured product plan that can be reviewed and refined before development begins. Plan Mode is especially useful for larger applications with multiple pages, features, database requirements, user roles, or complex workflows. ## Who is AIWA for? AIWA is designed for both technical and non-technical builders. Turn product ideas into working applications and test new concepts faster. Build websites and applications for clients while dramatically reducing development time. Use AI to accelerate development instead of manually implementing every component and workflow. Build internal tools, customer portals, dashboards, and custom applications around your workflows. ## You remain in control AIWA doesn't lock you into a completely closed development environment. Projects can be exported when you need greater control over the code or deployment. This makes it possible to start quickly with AIWA while retaining the flexibility to continue working with your project outside the platform when necessary. ## From idea to live product The simplest way to understand AIWA is to build something. You don't need the perfect prompt. Start by describing: > what you're building + who it's for + what it should do. For example: > Build a CRM for a real estate agency. Agents should be able to add leads, manage properties, track deals, schedule follow-ups, and view their sales pipeline from a dashboard. AIWA Live To Product AIWA can take it from there. ## Next: How AIWA Works Now that you know what AIWA is, learn how the AIWA workflow takes your idea through prompt, plan, build, refine, and publish. See the full AIWA workflow from prompt to published product. # Your First Prompt Source: https://docs.aiwa.codes/getting-started/your-first-prompt Learn how to describe your idea in plain language so AIWA understands what to build, who it's for, and what users should be able to do. Every AIWA project starts with a prompt. A prompt is simply a description of what you want AIWA to build, change, or help you accomplish. You don't need to know how to code, write technical specifications, or describe the architecture of your application. Start by explaining your idea in your own words. ## Start with what you want to build A simple prompt can be enough to get started. For example: > Build a world-class construction website. The website should have all the navigations a construction website should have. Use professional and very clean images. AIWA takes your request and determines how to turn it into a working product. AIWA Create Project Your first prompt doesn't have to describe every detail of your application. You can continue adding requirements and making changes after AIWA creates the first version. ## A simple formula for your first prompt If you're not sure what to write, start with three things: **What you're building + who it's for + what it should do** For example: > Build a CRM for a real estate agency. Agents should be able to manage leads, properties, deals, and customer follow-ups. Or: > Build a booking website for a beauty salon. Customers should be able to view services, choose a stylist, select an available time, and book an appointment. Or: > Build a client portal for a digital marketing agency. Clients should be able to log in, view their projects, download reports, and send messages to their account manager. That's enough information for AIWA to understand the direction of the product. ## Add more context when you have it You can give AIWA more information when you already know what you want. Useful details can include: * The type of product you're building * Who will use it * Important pages * Features you need * How users should interact with it * Your preferred design direction * Examples of products or experiences you like For example, instead of: > Build a restaurant website. You could say: > Build a premium Italian restaurant website. Include Home, Menu, About, Reservations, Gallery, and Contact pages. The design should feel elegant and modern with large food photography. Make it fully responsive. Both prompts can work. The second simply gives AIWA more direction. ## You don't need to describe the code Focus primarily on the product you want, not how you think AIWA should implement it. You usually don't need to start with instructions such as: > Create a React application with PostgreSQL and build five API endpoints... Instead, you can say: > Build a customer portal where customers can create accounts, log in, submit support requests, and track the status of their requests. AIWA can determine the implementation requirements from the product you're describing. If you're a developer and have specific technical requirements, you can absolutely include them. They just aren't required to start building with AIWA. ## Talk to AIWA like a product team A useful way to think about prompting AIWA is to imagine you're explaining the project to a product team. Instead of trying to find the perfect AI command, describe: **What are we building?** A SaaS application for freelancers. **Who is it for?** Freelancers who manage multiple clients. **What problem does it solve?** They need one place to manage clients, projects, invoices, and deadlines. **What should users be able to do?** Create clients, create projects, assign tasks, track invoices, and see upcoming deadlines from a dashboard. Put together, your prompt becomes: > Build a SaaS application for freelancers who manage multiple clients. They need one place to manage clients, projects, invoices, and deadlines. Users should be able to create clients, create projects and tasks, track invoices, and see upcoming deadlines from a dashboard. Make the interface clean, modern, and professional. That's a strong starting prompt. ## Don't try to build everything in one prompt For larger applications, you don't have to describe every future feature before you begin. Start with the core product. Then continue working with AIWA. For example: **First prompt** > Build a CRM for a real estate agency where agents can manage leads and properties. **After the first build:** > Add a deal pipeline where agents can move deals through different sales stages. **Then:** > Add follow-up reminders for each lead. **Then:** > Create a dashboard showing leads, active deals, upcoming follow-ups, and total pipeline value. This keeps the development process focused and gives you opportunities to review the product as it evolves. ## What happens after you submit your prompt? Once you submit your prompt, AIWA analyzes your request and begins working with you on the product. Depending on the mode you've selected, AIWA can either help structure the plan first or move into building. You can then review the result and continue the conversation. Your prompt isn't a one-time instruction. It's the beginning of your collaboration with AIWA. ## Your first prompt checklist Before submitting your first prompt, ask yourself: * What am I building? * Who is it for? * What should users be able to do? * Are there any important features I already know I need? * Do I have a preferred design direction? You don't need an answer to every question. If AIWA understands the product, audience, and main goal, you have enough to start. ## Next: Understanding the interface Now that you know how to start a conversation with AIWA, let's take a closer look at the workspace and the tools you'll use while building. Tour the AIWA workspace and the tools you'll use while building. # Anthropic (Claude) Source: https://docs.aiwa.codes/integrations/anthropic Connect Anthropic to power reasoning-heavy AI features with Claude: document analysis, extraction, drafting, and assistants. The Anthropic connector lets applications you build with AIWA use Claude models for AI-powered features. You can use Claude inside your application for experiences such as: * AI assistants * Long-form analysis * Summarization * Content generation * Document understanding * Classification * Structured extraction * Research-style workflows * Customer support * AI-powered product features Once Anthropic is connected, tell AIWA what you want Claude to do inside your product. **Connect Anthropic. Define the AI experience. AIWA builds the workflow around Claude.** ## AIWA vs Claude AIWA and Claude play different roles. You use AIWA to build and evolve your product. Claude can then become one of the AI capabilities inside the application you build. For example: > Build a legal document review platform where users can upload contracts and receive a structured analysis. AIWA builds the application. Claude can power the analysis step. Conceptually: ```text theme={null} You ↓ AIWA ↓ Builds the product ↓ User uploads document ↓ Application ↓ Claude ↓ Analysis returned ↓ Application displays result ``` ## Before You Start You'll need an Anthropic account and the credentials required by AIWA's Anthropic connector. API usage may incur charges based on your Anthropic account, model selection, and usage. Model availability, pricing, and rate limits are controlled by Anthropic and may change over time. ## Connect Anthropic to AIWA Open your AIWA project and go to Connectors. Find Anthropic and select it. AIWA Anthropic Claude Follow the connection flow and provide the information AIWA requests. AIWA Claude Config Once connected, Claude becomes available to use inside the application you're building. Keep your Anthropic API key private. Configure it through AIWA's connector experience rather than exposing it in frontend code or public repositories. ## Build Your First Claude Feature Suppose you're building a document analysis application. You could tell AIWA: > Add a Contract Summary feature using Claude. Users should upload a contract and receive an executive summary, key obligations, important dates, risks, and questions they should review. The workflow might look like: ```text theme={null} Upload Contract ↓ Extract relevant content ↓ Send to Claude ↓ Receive analysis ↓ Structure results ↓ Display to user ``` Claude becomes one component in the overall application workflow. ## Define the Input Tell AIWA what information Claude should receive. For example: > Use the contract text and the user's selected review goal. Or: > Use the support ticket and the previous five messages in the conversation. Or: > Use the lead enquiry, budget, timeline, and recent activity. The model should receive the context it actually needs to perform the task. ## Define the Output Be clear about what you expect back. For example: > Return: > > * Executive summary > * Key obligations > * Important dates > * Potential risks > * Recommended questions Or: > Return sentiment, category, urgency, and a suggested next action. Structured expectations make it easier for AIWA to build a useful product experience around the model. ## Example: Document Analysis Claude can be useful in applications that need to process longer or more detailed material. For example: > Add an AI document review feature. Users should upload a document and receive a concise summary, key decisions, action items, and important dates. You might then add: > Let users ask follow-up questions about the uploaded document. Now the experience evolves from one-time generation into an AI-powered document workspace. ## Example: Support Assistant For a customer support application: > Add a Draft Reply button using Claude. Use the current support ticket and recent conversation history to generate a suggested response. Show the draft in the reply editor for the agent to review before sending. Conceptually: ```text theme={null} Ticket ↓ Claude ↓ Draft response ↓ Agent reviews ↓ Agent sends ``` The model assists the support agent rather than automatically speaking to the customer. ## Example: Knowledge Assistant Suppose your application contains company knowledge or project documentation. You could ask AIWA: > Add an AI assistant that helps team members understand project documentation. Use the relevant project context to answer questions and cite the source sections used for the answer. The application can combine stored information with Claude to create a more contextual assistant. ## Example: Structured Extraction Imagine users submit detailed business enquiries. You could ask: > Use Claude to extract company name, requested service, budget, timeline, pain points, and decision-maker information from each enquiry. Save the structured result to the lead record. This turns unstructured text into data your application can use. ## Use Claude for Product Workflows Avoid thinking only in terms of: > Ask Claude a question. Instead, think: **Where does AI improve this workflow?** For example: ```text theme={null} Customer submits enquiry ↓ Save enquiry ↓ Claude analyzes it ↓ Structured qualification ↓ Save result ↓ Sales rep sees summary ``` That is an AI-powered product workflow. ## Human Review For important actions, consider keeping a person in the loop. For example: > Use Claude to draft a project proposal, but require the account manager to review and approve it before it can be sent. Conceptually: ```text theme={null} Claude generates ↓ Human reviews ↓ Human approves ↓ Action happens ``` This is especially useful when AI output affects: * Customer communication * Business decisions * Financial actions * Sensitive content * Important recommendations ## Saving Claude Responses Decide whether generated output should become permanent application data. For example: > Save approved contract summaries to the document record. Or: > Don't save generated drafts until the user clicks Save. Or: > Regenerate the summary only when the user explicitly requests it. This affects both product behavior and API usage. ## Sensitive Information Before sending application data to Claude, consider what information the feature actually needs. Don't send unnecessary private information simply because it's available. Never send passwords, API keys, authentication secrets, or private credentials to Claude as prompt context. For applications handling sensitive customer or business data, make sure your use of an external AI provider fits your privacy and compliance requirements. ## Model Choice Anthropic may provide multiple Claude models with different characteristics. Some may prioritize: * Speed * Cost * Context capacity * Reasoning quality * Complex analysis If your feature requires a particular model, tell AIWA which one to use. Otherwise, describe the product requirement. For example: > This feature analyzes long documents, so quality and context handling are more important than very fast responses. Or: > This feature performs thousands of simple classifications, so prioritize speed and cost efficiency. Check Anthropic for current model availability, capabilities, and API pricing. ## Control Output Length AI responses don't always need to be long. For example: > Return a maximum 5-bullet executive summary. Or: > Keep suggested support replies under 150 words. Or: > Return only the structured fields required by the application. Limiting unnecessary output can improve the user experience and help control API usage. ## Handle Loading States AI generation can take time. Your application should clearly show when Claude is working. For example: > Analyzing document... You can ask AIWA: > Show a loading state while Claude processes the document and disable the Analyze button until the current request completes. ## Handle Failed Requests AI requests can fail. For example: ```text theme={null} Analyze ↓ Claude request ↓ Error ↓ Show useful message ↓ Retry ``` Tell AIWA: > If analysis fails, preserve the uploaded document and let the user retry without uploading it again. The main workflow shouldn't lose the user's work simply because one AI request failed. ## Avoid Unnecessary Requests Don't regenerate expensive AI output every time a page loads unless that's actually required. For example: > Save the generated document summary and display the stored version whenever the user returns. Only call Claude again when the user clicks Regenerate. This can improve speed and reduce API usage. ## Common Problems ### Claude feature doesn't respond Check whether: * The Anthropic connector is configured * The server request is being made * Anthropic returns an error * The application receives the response * The interface correctly displays it Use Debug Mode with the specific behavior you observe. ### Output quality is poor The issue may be the instructions or context sent to Claude rather than the connection itself. For example: > The contract analysis is too generic. Improve the prompt so it explicitly identifies obligations, termination clauses, payment terms, deadlines, and unusual risks. ### Output format changes If your application depends on a specific structure, require and validate structured results. For example: > Ensure the classifier always returns category, urgency, sentiment, and recommendedAction in a predictable structured format before saving it. ### Response is slow Ask AIWA to inspect: * Model choice * Input size * Requested output length * Number of calls * Application workflow Long input and complex output can naturally require more processing. ### Usage is high Check whether Claude is being invoked unnecessarily. For example: > Audit the document detail page and make sure the AI analysis isn't being regenerated every time the page loads. ## Debugging Anthropic A good Debug Mode request could be: > Expected: When the user clicks Analyze, Claude should return a document summary and key risks. > > Actual: The loading state appears, then disappears without showing any result. > > The uploaded document is available and loads correctly. > > Error: \[PASTE ERROR IF AVAILABLE] > > Debug the Anthropic analysis workflow without changing the document upload feature. Don't include your API key in the prompt. ## Test Your Claude Feature Before publishing, test: * Normal input * Very short input * Large input * Missing input * Loading state * Failed generation * Retry behavior * Output structure * Saved results * Regeneration * User permissions * Unexpected user input * API usage behavior For important AI-assisted actions, also test the human review workflow. ## A Good Claude Prompt for AIWA When asking AIWA to build a Claude-powered feature, define: **Purpose** What should Claude accomplish? **Input** What information does it receive? **Output** What format should it return? **User experience** How does the user interact with the result? **Persistence** Should the output be saved? **Permissions** Who can use it? For example: > Add a Contract Review feature using Claude. Authorized users should upload a contract and click Analyze. Use the document content to return an executive summary, important obligations, payment terms, deadlines, termination conditions, and potential risks. Display the result in structured sections. Save the approved analysis to the document record and let users regenerate it manually if needed. ## OpenAI or Claude? You don't necessarily need both providers in every application. The right provider depends on your product requirements, preferred models, cost considerations, and the type of AI experience you're building. You can even design an application that supports multiple providers when there's a clear product reason to do so. The key principle remains the same: **Choose the provider that best supports the experience you're trying to build.** ## Next: Google (Gemini) Next, we'll look at Google Gemini and how to connect Google's AI models to applications built with AIWA. We'll focus on: * Connecting Gemini * Building AI features * Example workflows * Provider selection * Troubleshooting Connect Gemini and use Google's AI models inside your AIWA app. # Calendly Source: https://docs.aiwa.codes/integrations/calendly Connect Calendly to add demo, consultation, and onboarding scheduling into the customer workflows you build with AIWA. The Calendly connector lets you integrate scheduling experiences into applications you build with AIWA. You can use Calendly for: * Sales calls * Product demos * Consultations * Discovery calls * Customer onboarding * Interviews * Coaching sessions * Client meetings * Appointment scheduling Instead of building an entire scheduling system from scratch, your application can use Calendly as part of the customer journey. **Connect Calendly. Define when users should schedule. AIWA builds it into your workflow.** ## What You Can Build Calendly can become part of many different application workflows. **Demo booking** > Let qualified leads schedule a product demo after submitting the enquiry form. **Consultation booking** > Add a Book a Consultation button to the customer portal. **Customer onboarding** > After a customer purchases the Pro plan, invite them to schedule their onboarding call. **Sales qualification** > If a lead meets our qualification criteria, show them the option to book a discovery call. **Account management** > Add a Schedule a Call button to the customer dashboard so customers can book time with their account manager. The scheduling experience becomes part of the product rather than an isolated link. ## Before You Start You'll need a Calendly account with the event types and availability you intend to use. For example, you might create: ```text theme={null} 15-Minute Discovery Call 30-Minute Product Demo 60-Minute Strategy Session ``` Configure your availability, meeting duration, and other scheduling preferences in Calendly. Then AIWA can use that scheduling experience inside your application. ## Connect Calendly to AIWA Open your AIWA project and navigate to Connectors. Find Calendly and select it. AIWA Calendly Follow the connection flow and provide the authorization or information requested by AIWA. AIWA Calendly Config Once connected, you can ask AIWA to incorporate Calendly into your application workflows. Calendly controls your underlying event types, availability, scheduling rules, and connected calendars. Your AIWA application determines where and how scheduling fits into the user experience. ## Build Your First Scheduling Experience Suppose you're building a marketing agency website. Tell AIWA: > Add a Book a Strategy Call button to the homepage. When clicked, allow visitors to schedule our 30-minute Strategy Call through Calendly. The experience might look like: ```text theme={null} Website Visitor ↓ Book a Strategy Call ↓ Calendly ↓ Select Available Time ↓ Enter Details ↓ Booking Confirmed ``` That's the simplest Calendly workflow. But you can go much further. ## Put Scheduling in the Right Place Don't automatically place scheduling everywhere. Think about when a user should be encouraged to book. For example: ```text theme={null} Landing Page ↓ Learn About Product ↓ View Pricing ↓ Still Have Questions? ↓ Book a Demo ``` Or: ```text theme={null} Lead Form ↓ Qualification ↓ Qualified? ↙ ↘ Yes No ↓ ↓ Book Call Thank You ``` The scheduling step should support the customer journey. ## Example: Product Demo Suppose you're building a SaaS website. You could tell AIWA: > Add a Book a Demo CTA to the navigation and pricing page. Use our Calendly Product Demo event. After someone schedules, show a confirmation page explaining what to expect during the demo. This gives the customer context before and after scheduling. ## Example: Qualified Lead Booking Calendly becomes more powerful when combined with application logic. Imagine your enquiry form asks: * Name * Company * Company Size * Budget * Timeline * Requirements You could tell AIWA: > After someone submits the enquiry form, save the lead to the CRM. If their budget is \$5,000 or higher, show them the option to schedule a strategy call through Calendly. Otherwise, show the standard confirmation page. Conceptually: ```text theme={null} Lead Submitted ↓ Save to Neon ↓ Check Qualification ↙ ↘ Qualified Standard ↓ ↓ Calendly Thank You ``` Now scheduling is part of a business workflow. ## Example: Paid Consultation Calendly can also work alongside Stripe. Suppose you sell \$250 consultations. The desired experience might be: ```text theme={null} Choose Consultation ↓ Stripe Checkout ↓ Payment Confirmed ↓ Schedule Session ↓ Calendly ``` You could tell AIWA: > Sell a Strategy Consultation for \$250 through Stripe. Only after payment has been successfully confirmed should the customer receive access to schedule the consultation through Calendly. This combines two connectors into one experience. Don't rely only on a frontend success page to determine whether someone paid. Access to paid scheduling should be based on the confirmed payment workflow. ## Example: Customer Onboarding Suppose your SaaS includes onboarding calls for higher-tier customers. You could ask: > After a customer subscribes to the Pro plan, show an onboarding checklist in their dashboard. The first step should allow them to schedule their onboarding call through Calendly. The workflow becomes: ```text theme={null} Agency Subscription ↓ Account Activated ↓ Onboarding ↓ Schedule Call ↓ Calendly ``` Scheduling is now part of the product's onboarding experience. ## Example: Client Portal You might want existing customers to schedule calls from inside their account. For example: > Add a Schedule a Meeting option to the client portal. Customers should be able to book time with their assigned account manager. You could display it alongside: ```text theme={null} Account Manager Sarah Johnson [Send Message] [Schedule Meeting] ``` This creates a more complete client experience. ## Prefill Customer Information If your application already knows who the customer is, you may not want them to repeatedly enter the same information. Where supported by your scheduling implementation, you can ask AIWA to prefill relevant information. For example: > When a logged-in customer opens the scheduling experience, use their saved name and email where possible. This reduces friction. ## Save Booking Information Sometimes simply allowing the customer to schedule is enough. Other applications may need to know that a meeting was booked. For example, your CRM might display: ```text theme={null} Lead Acme Ltd. Status Demo Scheduled Meeting September 15, 2:00 PM ``` If your integration supports the required scheduling data, AIWA can incorporate it into the application's workflow. For example: > When a qualified lead schedules a demo, update the lead status to Demo Scheduled and show the meeting information on the lead record. ## Scheduling and Your CRM Calendly can become particularly useful inside CRM applications. Conceptually: ```text theme={null} Lead ↓ Qualified ↓ Calendly Booking ↓ Meeting Scheduled ↓ CRM Updated ↓ Sales Pipeline ``` Instead of sales representatives manually updating the lead after every booking, the scheduling event can participate in the workflow where the integration supports it. ## Scheduling + Email You can also combine Calendly with Resend. For example: > After a customer schedules their onboarding call, send them a welcome email containing the onboarding checklist and instructions for preparing for the call. The workflow becomes: ```text theme={null} Calendly Booking ↓ Application ↓ Resend ↓ Onboarding Email ``` Different connectors can work together around a single customer event. ## Scheduling + SMS You might also combine Calendly with Twilio. For example: > Send the customer an SMS reminder before their scheduled consultation. Conceptually: ```text theme={null} Scheduled Meeting ↓ Reminder Time ↓ Twilio ↓ Customer ``` Make sure any automated messaging workflow follows the applicable consent and messaging requirements. ## Event Types Your business may have several Calendly event types. For example: ```text theme={null} Discovery Call 15 minutes Product Demo 30 minutes Strategy Consultation 60 minutes Customer Onboarding 45 minutes ``` Tell AIWA which scheduling experience belongs in each part of your application. For example: > Use the 30-minute Product Demo event on the public website and the 45-minute Customer Onboarding event inside the Agency customer dashboard. This prevents different scheduling experiences from being mixed together. ## Don't Confuse Calendly with Google Calendar These connectors solve different problems. **Calendly** is primarily a scheduling experience. It helps people choose from available meeting times and book an appointment. **Google Calendar** lets applications interact more directly with calendar data and events. For example: ```text theme={null} Need customers to choose an available meeting time? → Calendly ``` Whereas: ```text theme={null} Need your application to create, read, or manage calendar events? → Google Calendar ``` We'll cover Google Calendar on the next page. ## Handle Cancellations and Rescheduling Meetings don't always happen as originally planned. Customers may: * Cancel * Reschedule * Choose another time Your application should account for this if it stores scheduling information. For example: > If a scheduled demo is cancelled, update the CRM so the lead no longer appears as having an upcoming demo. Or: > If the meeting is rescheduled, display the new date and time on the lead record. The exact behavior depends on the scheduling functionality available through your integration. ## Time Zones Scheduling applications often involve users in different locations. Calendly can help manage scheduling across time zones, but your AIWA application should also display meeting information clearly. For example: ```text theme={null} September 15 2:00 PM WAT ``` or display the meeting in the user's local timezone where appropriate. Avoid showing ambiguous times such as: ```text theme={null} Meeting: 2:00 PM ``` when users may be in different regions. ## Common Problems ### Scheduling page doesn't open Check: * Calendly connection * Event configuration * Scheduling link or event reference * Application interaction Use Debug Mode if the AIWA interface isn't opening the expected scheduling experience. ### Wrong event type opens Tell AIWA: > The Book a Demo button currently opens our 15-minute Discovery Call. It should use the 30-minute Product Demo Calendly event. Fix the scheduling configuration without changing the CTA design. ### No available times appear This may be related to Calendly rather than your AIWA application. Check your: * Calendly availability * Connected calendar * Event configuration * Scheduling limits ### Booking works but CRM doesn't update Separate the two parts of the workflow. For example: > Calendly booking completes successfully, but the lead remains in Qualified instead of changing to Demo Scheduled. Debug the post-booking CRM update without changing the Calendly booking experience. ### Meeting time is incorrect Check whether the issue involves timezone conversion or how the application stores/displays the meeting time. Tell AIWA exactly where the correct and incorrect values appear. ## Debugging Calendly A useful Debug Mode request looks like: > Expected: After a qualified lead submits the form, they should be able to schedule our Product Demo. > > Actual: The lead is saved correctly, but clicking Schedule Demo doesn't open the Calendly scheduling experience. > > The CRM and qualification logic are working. > > Debug the Calendly portion without changing the existing lead form or qualification rules. This isolates the scheduling problem. ## Test Your Scheduling Workflow Before publishing, test: * Scheduling CTA * Correct event type * Available times * Booking confirmation * Mobile experience * Time zones * Logged-in users * CRM updates, if applicable * Cancellation behavior * Rescheduling * Paid booking restrictions, if applicable * Follow-up notifications Also test the complete journey as a customer rather than only checking whether the Calendly screen opens. ## A Good Calendly Prompt A strong scheduling request defines: * Who can schedule? * When can they schedule? * Which event should they book? * Where should scheduling appear? * What happens after booking? For example: > After a qualified lead submits our demo form, save them to the CRM and show the Calendly scheduling experience for our 30-minute Product Demo. After they schedule, show a confirmation page and update their CRM status to Demo Scheduled. Display their scheduled meeting on the lead record. That's much stronger than: > Add Calendly. ## Think in Scheduling Workflows A useful mental model is: ```text theme={null} TRIGGER ↓ ELIGIBILITY ↓ SCHEDULING ↓ BOOKING ↓ APPLICATION UPDATE ↓ FOLLOW-UP ``` Calendly handles scheduling. Your AIWA application determines where scheduling belongs in the product and what happens around it. ## Next: Google Calendar Next, we'll look at Google Calendar. Unlike Calendly, Google Calendar can be useful when your application needs to work directly with calendar events. We'll cover examples such as: * Creating calendar events * Adding appointments to calendars * Managing event information * Connecting bookings to calendars * Building calendar-driven workflows Connect Google Calendar to create and manage events from your app. # Cloudinary Source: https://docs.aiwa.codes/integrations/cloudinary Connect Cloudinary to upload, store, transform, and deliver images and other media inside the applications you build with AIWA. Cloudinary lets applications you build with AIWA upload, store, manage, and deliver media such as images. You can use Cloudinary for: * Profile photos * Product images * Property galleries * Portfolio images * Blog images * User-generated media * Listing photos * Thumbnails * Image galleries * Other media-driven experiences Once Cloudinary is connected, describe what users should upload and how that media should be used inside your application. **Connect Cloudinary. Describe the media experience. AIWA builds the upload workflow.** ## Why Use Cloudinary? Imagine you're building a real estate platform. Each property might have: * Property Name * Price * Location * Description * Bedrooms * Bathrooms * Images Information such as the property name, price, and location belongs naturally in your application's database. The actual image files are different. A common architecture looks like: ```text theme={null} PROPERTY ↓ Neon Postgres Property information ↓ Cloudinary Property images ``` Your application connects the two. ## Database vs Media Storage This distinction is important. Suppose a customer uploads a profile photo. Cloudinary can store and deliver the image. Your database can store the information your application needs to associate that image with the customer. Conceptually: ```text theme={null} User uploads image ↓ Cloudinary ↓ Media reference ↓ Neon Postgres ↓ User Profile ↓ Image displayed ``` The user simply sees their profile picture. The application handles the systems behind it. ## Before You Start You'll need a Cloudinary account and the credentials required by AIWA's Cloudinary connector. Your Cloudinary account provides the configuration required for applications to communicate with the service. Cloudinary usage, storage, bandwidth, transformations, and other limits depend on your Cloudinary account and plan. ## Connect Cloudinary to AIWA Open your AIWA project and navigate to Connectors. Find Cloudinary and select it. AIWA Cloudinary Follow the connection flow and provide the Cloudinary information requested by AIWA. AIWA Cloudinary Config Once connected, you can ask AIWA to build media functionality into your application. Keep private Cloudinary credentials secure. Configure them through AIWA's connector experience rather than exposing secrets directly in frontend code. ## Build Your First Upload Suppose you're building a user profile. Tell AIWA: > Allow users to upload a profile photo from their Account Settings page. Upload the image through Cloudinary and display it on their profile after the upload succeeds. Conceptually: ```text theme={null} Select Photo ↓ Validate File ↓ Upload to Cloudinary ↓ Save Media Reference ↓ Update Profile ↓ Display Photo ``` The upload becomes part of the application's workflow. ## Define What Users Can Upload Don't simply say: > Add file upload. Describe what the upload is for. For example: > Allow users to upload a profile image. Or: > Allow agents to upload property photos when creating or editing a listing. Or: > Allow store administrators to upload product images. The context helps AIWA understand how the uploaded media should relate to the rest of the application. ## File Types You can define which types of files your application should accept. For example: > Accept JPG, PNG, and WebP images for property listings. This helps prevent users from uploading files your feature wasn't designed to handle. ## File Size Limits You may also want to restrict file size. For example: > Profile photos must be JPG, PNG, or WebP and no larger than 5 MB. Or: > Allow product images up to 10 MB each. The exact limits you choose should reflect your product requirements and the capabilities of your Cloudinary account. ## Single Image Uploads Some features need only one image. Examples include: ```text theme={null} User → Profile Photo Company → Logo Article → Cover Image Category → Thumbnail ``` A simple prompt could be: > Add a company logo uploader to Workspace Settings. Accept JPG, PNG, and WebP. After a successful upload, display the logo in the workspace header. ## Multiple Image Uploads Other features need galleries. Real estate is a good example. You could ask: > Allow agents to upload up to 20 images for each property listing. Show upload progress and display the uploaded images in a gallery. Agents should be able to remove images before saving the listing. Conceptually: ```text theme={null} Property Form ↓ Select Images ↓ Validate ↓ Upload to Cloudinary ↓ Save References ↓ Property Gallery ``` ## Example: Real Estate Gallery Suppose you're building a property marketplace. Each property can have multiple images. You could tell AIWA: > Add an image gallery to property listings. Agents should be able to upload up to 20 JPG, PNG, or WebP images. Let them choose a primary image that will be used on property cards and search results. Now the application needs to understand more than simply uploading files. It needs to know: * Which images belong to the property * Which image is primary * How images are displayed * How images are removed * How the gallery is ordered That's a complete media feature. ## Primary Images For galleries, it's often useful to define a primary or featured image. For example: ```text theme={null} Property ↓ 20 Images ↓ 1 Primary Image ↓ Search Result Card ``` You can ask: > Allow agents to set one property image as the primary image. Use that image on property cards throughout the application. ## Reordering Images Image order can matter. For example: > Allow agents to drag and reorder property images. Preserve that order when displaying the public property gallery. This turns a simple uploader into a proper media-management experience. ## Removing Images Users may also need to remove uploaded media. For example: > Allow users to remove their current profile photo and upload a replacement. Or: > Agents can remove individual images from a property gallery. Be careful when deleting media from applications already containing real user content. The application may need to update both the Cloudinary asset and the corresponding database reference. ## Replacing Images Sometimes replacing is better than treating every update as a new independent file. For example: > When a user uploads a new profile photo, replace the current profile image and update their account to use the new image. Your application's behavior should make it clear which image is currently active. ## Upload Progress Large images or multiple uploads may take time. Your interface should communicate what's happening. For example: ```text theme={null} Uploading 3 of 8... ████████████░░░░░ ``` You can ask AIWA: > Show upload progress while property images are being uploaded. Disable the Save Property button until required uploads are complete. This prevents users from wondering whether the application is working. ## Upload Success After an upload completes, the application should reflect the result. For example: > Show the uploaded profile photo immediately after the upload succeeds. Or: > Add successfully uploaded property images to the gallery preview. Users should receive clear feedback that their upload worked. ## Upload Failures Uploads can fail. For example: ```text theme={null} Upload ↓ Cloudinary ↓ Failed ↓ Show Error ↓ Retry ``` Don't leave users guessing. You could tell AIWA: > If an image upload fails, show which image failed and allow the user to retry without re-uploading the successful images. This becomes especially useful for multi-image uploads. ## Image Optimization Large images can make applications unnecessarily slow. Cloudinary provides capabilities for delivering optimized media. When building image-heavy experiences, ask AIWA to use appropriate image delivery and optimization behavior. For example: > Optimize property images for web delivery and use appropriately sized images for listing cards rather than loading the full-size originals everywhere. A listing card doesn't necessarily need the same image dimensions as a full-screen property gallery. ## Responsive Images Your application may be viewed on: * Phones * Tablets * Laptops * Large desktop displays The media experience should work across those screen sizes. For example: > Make the property gallery responsive and ensure listing images remain appropriately sized and cropped across mobile and desktop. ## Image Cropping Different interfaces may require different image shapes. For example: ```text theme={null} Profile 1:1 Property Card 4:3 Hero Image 16:9 ``` You can describe the visual result you want. For example: > Display profile photos as square images with consistent cropping. Or: > Use a consistent 4:3 aspect ratio for property cards without distorting the images. ## Example: E-commerce Product Images Suppose you're building an online store. Tell AIWA: > Allow administrators to upload up to 8 images per product using Cloudinary. One image should be marked as the primary product image. Allow images to be reordered and removed. Display the primary image on product cards and the complete gallery on the product page. The workflow becomes: ```text theme={null} Admin ↓ Create Product ↓ Upload Images ↓ Cloudinary ↓ Save Product + Media References ↓ Storefront ``` ## Example: User Avatars A simpler workflow might be: > Allow users to upload or replace their profile photo from Account Settings. Accept JPG, PNG, and WebP up to 5 MB. Display the image in the navigation avatar and on their profile. This connects one uploaded image to several parts of the application's interface. ## Example: Portfolio For a creative portfolio application: > Allow creators to upload images to projects. Each project can contain up to 15 images. Let creators reorder them and choose a cover image. Display the cover image on portfolio cards and the full collection on the project page. Again, Cloudinary handles the media while your application manages the product experience around it. ## Media and Your Database Your database may need to remember information about uploaded media. Conceptually: ```text theme={null} PROPERTY ID: 104 ↓ PROPERTY IMAGE Property: 104 URL: ... Primary: true Position: 1 ``` This allows your application to understand: * Which record owns the image * Where the image is located * Whether it's the primary image * Where it appears in the gallery Cloudinary and Neon work together rather than replacing one another. ## Protect Upload Permissions Not every user should necessarily be allowed to upload or modify every image. For example: > Only agents who can edit a property should be able to upload, reorder, or delete its images. Or: > Users can change their own profile photo but not another user's. These permissions should be enforced appropriately by the application. ## Don't Expose Sensitive Credentials Cloudinary functionality requiring private credentials should run through the appropriate secure application environment. The conceptual flow is: ```text theme={null} Application ↓ Secure Logic ↓ Cloudinary ``` rather than exposing sensitive credentials directly to every user's browser. ## Common Problems ### Images aren't uploading First determine whether the problem affects: * File selection * Validation * Cloudinary upload * Database update * Displaying the returned image Tell AIWA which part is failing. ### Upload succeeds but image doesn't appear The Cloudinary upload may be working while your application isn't correctly saving or displaying the resulting media reference. Tell AIWA: > The image uploads successfully to Cloudinary, but it doesn't appear on the property after saving. Debug how the uploaded image reference is being stored and retrieved. ### Image appears after upload but disappears after refresh This often suggests that the application is displaying temporary frontend state without correctly persisting the media reference. Tell AIWA: > The profile image appears immediately after upload but disappears after refreshing the page. Make sure the uploaded image reference is saved to the user's profile and loaded from the database. ### Images are too slow Large media files may be delivered at unnecessarily large sizes. Ask AIWA to inspect how images are being loaded and optimize the delivery for the contexts where they're displayed. ### Wrong image appears This may indicate an incorrect relationship between the uploaded media and its owning database record. Give AIWA the specific example and ask it to inspect the relationship. ## Debugging Cloudinary A useful Debug Mode request might look like: > Expected: When an agent uploads property images and saves the listing, the images should remain attached to the property. > > Actual: Images upload and appear in the preview, but disappear after refreshing the page. > > The property itself saves correctly. > > Debug the Cloudinary upload and database persistence workflow without changing the property form design. This separates the media problem from the rest of the application. ## Test Your Upload Experience Before publishing, test: * Supported file types * Unsupported file types * Maximum file size * Single uploads * Multiple uploads * Upload progress * Failed uploads * Retry behavior * Removing images * Replacing images * Image ordering * Primary images * Page refresh * Mobile layouts * User permissions Also test what happens when a user uploads a much larger image than expected. ## A Good Cloudinary Prompt A strong request defines: * What is being uploaded? * Who can upload it? * Which formats are accepted? * How many files are allowed? * What size limits apply? * Where should the media appear? * Can users replace, remove, or reorder it? For example: > Allow agents to upload up to 20 images for each property using Cloudinary. Accept JPG, PNG, and WebP up to 10 MB each. Allow images to be reordered and removed, and let the agent choose one primary image. Use the primary image on property cards and display the complete gallery on the property detail page. That's much stronger than: > Add image upload. ## Think in Media Workflows A useful mental model is: ```text theme={null} SELECT ↓ VALIDATE ↓ UPLOAD ↓ STORE REFERENCE ↓ DISPLAY ↓ MANAGE ``` Cloudinary handles the media infrastructure. Your AIWA application determines how that media fits into the product. ## Next: OpenAI We've connected payments, email, communications, and media. Now we move into AI integrations. Next is OpenAI, where we'll cover how to connect OpenAI to an AIWA project and build AI-powered features directly into your application. Examples include: * AI assistants * Content generation * Summarization * Classification * Data extraction * AI-powered workflows Connect OpenAI to add assistants, generation, and AI workflows. # Google Calendar Source: https://docs.aiwa.codes/integrations/google-calendar Connect Google Calendar to create, update, and cancel events from bookings, appointments, and CRM activity in your AIWA app. The Google Calendar connector lets applications you build with AIWA integrate calendar functionality into your product workflows. You can use Google Calendar for experiences such as: * Creating calendar events * Adding appointments to calendars * Scheduling meetings * Creating events from bookings * Adding attendees * Managing event details * Connecting CRM activities to calendars * Building calendar-driven workflows **Connect Google Calendar. Define the event. AIWA builds the calendar workflow.** ## Google Calendar vs Calendly Calendly and Google Calendar are related, but they solve different problems. **Calendly** Use Calendly when you want someone to choose an available time and schedule with you. For example: ```text theme={null} Visitor ↓ Book a Demo ↓ Choose Available Time ↓ Confirm Booking ``` **Google Calendar** Use Google Calendar when your application needs to create or work with calendar events. For example: ```text theme={null} Booking Confirmed ↓ Create Calendar Event ↓ Add Customer ↓ Event Appears on Calendar ``` In some applications, you may use both. ## Before You Start You'll need a Google account with the calendar you want to use, and access to the Google Cloud console. Your app connects to Google Calendar as a service account: a robot identity with its own email address, ending in .iam.gserviceaccount.com. It can only use calendars that you've explicitly shared with that address. There's no Google sign-in step. Share only the calendar your application actually needs. A calendar you haven't shared with the service account stays invisible to your app. ## Connect Google Calendar to AIWA Open your AIWA project and navigate to Connectors. Find Google Calendar and select it. AIWA Google Calender The connector page walks you through these steps: 1. In the Google Cloud console, pick or create a project and enable the Google Calendar API. 2. Under Credentials, create a service account, add a JSON key to it, and download the key file. 3. Paste the entire contents of the key file into the Service account key (JSON) field. 4. In Google Calendar, open your calendar's settings, share it with the service account's email address, and choose "Make changes to events". 5. Copy the Calendar ID from the same settings page and paste it into the Calendar ID field. AIWA Google Calemder Config You can also set a Timezone for new events, or leave it empty to use the calendar's own timezone. The connector page then checks that your app can reach the calendar. If it can't, the calendar most likely hasn't been shared with the service account yet. Google Calendar has no test mode. The preview of your app reads and writes your real calendar. Once connected, you can begin asking AIWA to build calendar functionality into your application. ## Create Your First Calendar Event Suppose you're building a consultation booking application. You could tell AIWA: > After a consultation is successfully confirmed, create a Google Calendar event containing the customer's name, consultation type, date, time, and contact information. Conceptually: ```text theme={null} Consultation Confirmed ↓ Save Booking ↓ Google Calendar ↓ Create Event ↓ Calendar Updated ``` The customer completes a normal workflow while your application handles the calendar action behind it. ## Define the Event Details Be clear about what should appear in the calendar event. For example: > Create a 60-minute calendar event titled "Strategy Consultation: Sarah Chen." Include the customer's email, phone number, booking reference, and notes in the event details. Useful event information may include: * Event title * Start date and time * End date and time * Description * Attendees * Location * Meeting information * Customer details * Internal reference Think about what someone viewing the calendar will actually need. ## Example: Appointment Booking Suppose you're building an appointment system for a salon. A customer chooses: ```text theme={null} Service Hair Consultation Stylist Jessica Date September 15 Time 2:00 PM ``` After the booking is confirmed: ```text theme={null} Booking ↓ Neon ↓ Google Calendar ↓ Jessica's Calendar ``` You could ask AIWA: > When a Hair Consultation is confirmed with Jessica, create the corresponding event on the connected Google Calendar. Include the customer's name, email, phone number, service, and booking reference. Now your internal calendar can reflect activity happening inside the application. ## Example: CRM Follow-Up Calendar functionality isn't limited to customer appointments. Imagine a salesperson is working with a lead. You could build: > Add a Schedule Follow-Up action to each lead. The sales representative should choose a date and time, add notes, and create the follow-up as a Google Calendar event. The workflow becomes: ```text theme={null} Lead ↓ Schedule Follow-Up ↓ Choose Date & Time ↓ Google Calendar ↓ Event Created ``` This connects CRM activity with the salesperson's actual calendar. ## Example: Customer Onboarding Suppose a new customer needs an onboarding meeting. You could ask: > When an Agency customer schedules their onboarding session, create a calendar event containing their company name, primary contact, plan, and onboarding notes. The account manager now sees the onboarding session directly in their calendar. ## Add Attendees Some events need participants. For example: > Create the consultation event and add the customer's email address as an attendee. Or: > Add the customer, account manager, and implementation specialist to the onboarding meeting. Conceptually: ```text theme={null} Application ↓ Create Event ↓ Customer Account Manager Implementation Specialist ``` Adding attendees needs a Google Workspace account with domain-wide delegation set up for the service account. Without it, your app creates the event without attendees and can share the event details with each person another way, for example by email. ## Use Application Data Calendar events can use information already stored in your application. Suppose your CRM knows: ```text theme={null} Lead Sarah Chen Company Acme Ltd. Email sarah@... Deal $15,000 Owner Michael ``` Instead of making the salesperson re-enter everything, you could tell AIWA: > When creating a meeting from a lead record, automatically include the lead's name, company, email, deal value, and assigned sales representative. Your database becomes context for the calendar workflow. ## Keep Calendar and Application Data Connected Creating an event is only part of the workflow. Your application may also need to remember the relationship between the event and the corresponding record. Conceptually: ```text theme={null} CRM Lead ↕ Meeting Record ↕ Google Calendar Event ``` This can help your application understand which calendar event belongs to which booking, customer, lead, or project. For example, a lead page might show: ```text theme={null} Upcoming Meeting Product Demo September 15 · 2:00 PM [View Meeting] ``` ## Updating Events Plans change. Suppose an appointment moves from: ```text theme={null} September 15 at 2:00 PM ``` to: ```text theme={null} September 16 at 4:00 PM ``` If your application supports changing the booking, the corresponding calendar event may also need to change. You could tell AIWA: > When an appointment is rescheduled, update the existing Google Calendar event rather than creating another event. Conceptually: ```text theme={null} Booking Updated ↓ Find Existing Event ↓ Update Date & Time ↓ Google Calendar ``` This helps prevent duplicate events. ## Cancelling Events The same principle applies to cancellations. For example: > When a confirmed consultation is cancelled, cancel or remove the corresponding Google Calendar event and update the booking status. Your systems should remain synchronized. ```text theme={null} Booking Cancelled ↓ Application Updated ↓ Calendar Updated ``` Otherwise, staff could see meetings on their calendar that no longer exist in the application. ## Avoid Duplicate Events One confirmed booking should generally create one calendar event. Refreshing a page or reopening a booking shouldn't create another one. For example: ```text theme={null} Booking #10482 ↓ Calendar Event ✓ ``` not: ```text theme={null} Booking #10482 ↓ Event Event Event Event ``` Tie calendar creation to the actual business event, such as booking confirmed, rather than a page load. ## Time Zones Time zones are especially important with calendars. Imagine: ```text theme={null} Customer New York Consultant Lagos ``` A meeting must still represent the same moment for both people. Your application should store and process time information consistently and display it appropriately for the user. Don't treat a date and time such as "September 15 at 2:00 PM" as complete scheduling information when your application serves users across multiple time zones. When debugging calendar issues, always check whether the underlying problem is actually a timezone conversion problem. ## Google Calendar + Google Meet Google Calendar can also work alongside the Google Meet connector. For example: ```text theme={null} Meeting Scheduled ↓ Create Google Meet ↓ Create Calendar Event ↓ Add Meeting Link ↓ Invite Attendees ``` You could tell AIWA: > When a customer schedules a remote consultation, create a Google Meet meeting and add it to the corresponding Google Calendar event. We'll cover Google Meet on the next page. ## Google Calendar + Resend You can also create follow-up communication around calendar workflows. For example: ```text theme={null} Appointment Confirmed ↓ Create Calendar Event ↓ Resend ↓ Confirmation Email ``` You could ask: > After a consultation is confirmed, create the Google Calendar event and send the customer a confirmation email through Resend containing the appointment details. This is where connectors become especially powerful: multiple services can participate in one application workflow. ## Google Calendar + Twilio For appointment-driven products: > Create the appointment on Google Calendar and send the customer an SMS reminder 24 hours before the meeting. Conceptually: ```text theme={null} Appointment ↓ Google Calendar ↓ Reminder Time ↓ Twilio ↓ Customer ``` Again, your application coordinates the workflow. ## Permissions Calendar access can involve sensitive information. Your app can only use the calendars you've shared with its service account, with the permission you chose when sharing. For example, there's a difference between an application that needs to: > Create calendar events and one that needs to: > Read and manage existing calendar information. Share only what your application actually needs. To remove your app's access, stop sharing the calendar with the service account, or delete its key in the Google Cloud console. The service account key is a secret. It stays on your app's server. Never paste it into a prompt. ## Common Problems ### Calendar event isn't created First check whether the main application action succeeds. For example: > The booking is saved successfully, but no Google Calendar event appears. That isolates the issue to the calendar portion of the workflow. ### Event appears at the wrong time This is often worth checking as a timezone issue. Tell AIWA: > The booking shows 2:00 PM WAT correctly in the application, but the Google Calendar event appears one hour later. Debug the timezone handling without changing the booking time itself. ### Duplicate events appear Tell AIWA: > One confirmed appointment sometimes creates multiple Google Calendar events. Audit the event creation trigger and ensure each booking maps to only one calendar event. ### Event doesn't update after rescheduling Tell AIWA: > Rescheduling updates the booking correctly, but the original Google Calendar event remains unchanged. Update the existing calendar event when the booking is rescheduled rather than creating another event. ### The calendar can't be reached Check whether: * The Google Calendar API is enabled in your Google Cloud project * The calendar is shared with the service account's email address * The sharing permission is "Make changes to events" * The Calendar ID is correct * The service account key still exists in the Google Cloud console If Google returns an error, provide the error to AIWA's Debug Mode without sharing your service account key. ## Debugging Google Calendar A good Debug Mode request could look like: > Expected: After a consultation is confirmed, a Google Calendar event should be created for the appointment. > > Actual: The booking saves correctly in the application, but no calendar event appears. > > The booking date and time are stored correctly. > > Error: \[PASTE ERROR IF AVAILABLE] > > Debug the Google Calendar portion of the workflow without changing the booking functionality. This gives AIWA a specific integration boundary to investigate. ## Test Your Calendar Workflow Before publishing, test: * Event creation * Event title * Start and end time * Time zones * Description * Attendees * Rescheduling * Cancellation * Duplicate prevention * Application-to-calendar relationship * Authorization failures * Mobile experience * Different user roles For booking applications, test the complete lifecycle: ```text theme={null} CREATE ↓ RESCHEDULE ↓ CANCEL ``` Not just event creation. ## A Good Google Calendar Prompt A strong request defines: * **Trigger:** When should the event be created? * **Calendar:** Where should it go? * **Details:** What should it contain? * **Attendees:** Who should participate? * **Updates:** What happens if the source record changes? * **Cancellation:** What happens if it's cancelled? For example: > When a consultation booking is confirmed, create a Google Calendar event using the booking's start and end time. Title it with the consultation type and customer's name. Include their contact information and booking reference in the description and add the customer as an attendee. If the booking is rescheduled, update the existing event. If it's cancelled, cancel the corresponding calendar event. Ensure one booking cannot create duplicate events. That's significantly stronger than: > Add Google Calendar. ## Think in Calendar Workflows A useful mental model is: ```text theme={null} APPLICATION EVENT ↓ CALENDAR ACTION ↓ SAVE RELATIONSHIP ↓ KEEP IN SYNC ↓ UPDATE / CANCEL ``` Google Calendar handles the calendar. AIWA builds the product logic around it. ## Next: Google Meet Next, we'll add Google Meet. We'll cover how AIWA-built applications can incorporate video meetings into workflows such as: * Sales demos * Consultations * Interviews * Customer onboarding * Team meetings * Virtual appointments We'll also show how Google Meet + Google Calendar can work together to create a complete meeting experience. Connect Google Meet to add video meetings to your AIWA app workflows. # Google Drive Source: https://docs.aiwa.codes/integrations/google-drive Connect Google Drive to bring project files, client documents, and shared resources into workflows you build with AIWA. The Google Drive connector lets applications you build with AIWA work with files and documents stored in Google Drive. You can use Google Drive for experiences such as: * Client file access * Project documents * Shared resources * Internal team files * Document workflows * Linking application records to Drive files * File organization * Document-driven product features **Connect Google Drive. Define how files should be used. AIWA builds the workflow around them.** ## What You Can Build Google Drive can become part of many application workflows. **Client portals** > Show customers the files and documents associated with their projects. **Project management** > Link project records to folders or documents stored in Google Drive. **Internal tools** > Give team members access to approved company documents from inside the application. **Onboarding** > Show new customers the onboarding documents associated with their account. **Document workflows** > Allow users to choose a Drive document and use it as input for another application workflow. The application determines how the files fit into the user experience. ## Before You Start You'll need a Google account with Google Drive, and access to the Google Cloud console. Your app connects to Google Drive as a service account: a robot identity with its own email address, ending in .iam.gserviceaccount.com. It works inside one folder that you share with that address. There's no Google sign-in step. A service account has no Drive storage of its own, so the shared folder is required. Uploads work most reliably when the folder is on a Google Workspace shared drive. ## Connect Google Drive to AIWA Open your AIWA project and navigate to Connectors. Find Google Drive and select it. AIWA Google Drive The connector page walks you through these steps: 1. In the Google Cloud console, pick or create a project and enable the Google Drive API. 2. Under Credentials, create a service account, add a JSON key to it, and download the key file. 3. Paste the entire contents of the key file into the Service account key (JSON) field. 4. In Google Drive, create a folder for this app, share it with the service account's email address, and give it Editor access. 5. Open the folder, copy the ID from its address (the part after /folders/), and paste it into the Target folder ID field. AIWA Google Drive Config Once connected, you can begin asking AIWA to build Drive-powered functionality into your application. Google Drive has no test mode. The preview of your app uploads to, and reads from, your real folder. ## Build Your First Drive Workflow Suppose you're building a client portal. Tell AIWA: > Add a Files section to each client project. Allow the application to display the Google Drive files associated with that project. Conceptually: ```text theme={null} Client Project ↓ Google Drive ↓ Project Files ↓ Client Portal ``` The customer interacts with your portal while Google Drive provides the underlying file source. ## Application Records and Drive Files A useful application usually needs to understand which files belong to which records. For example: ```text theme={null} Customer ↓ Project ↓ Drive Folder ↓ Project Files ``` You might tell AIWA: > Each project should have an associated Google Drive folder. Show the folder's approved documents inside the project detail page. This connects application data with external file storage. ## Example: Agency Client Portal Imagine an agency manages multiple customers. Each customer has projects, and each project has files. You could ask: > Add a Files tab to the client portal. Show Google Drive files associated with the customer's projects and group them by project. Customers should only see files belonging to their own account. This combines: * Authentication * Authorization * Project data * Google Drive Conceptually: ```text theme={null} Signed-In Customer ↓ Verify Project Access ↓ Find Associated Drive Files ↓ Display Approved Files ``` ## Example: Project Resources For a project management application: > Add a Resources section to each project where team members can access documents stored in the project's connected Google Drive folder. You might display: ```text theme={null} Project Resources Brand Guidelines.pdf Campaign Brief.docx Product Images Research Notes ``` The application becomes a more convenient interface for accessing project resources. ## Example: Customer Onboarding Suppose new customers need onboarding documents. You could ask: > After a customer completes onboarding, show the Welcome Guide, Implementation Checklist, and Training Resources from the connected Google Drive folder inside their dashboard. Now Drive participates in the onboarding experience. ## Example: Document Review Google Drive can also provide files for AI-powered workflows. For example: > Allow authorized users to select a Google Drive document and generate an executive summary using Claude. Conceptually: ```text theme={null} Google Drive ↓ Select Document ↓ Retrieve Content ↓ Claude ↓ Summary ↓ AIWA Application ``` This combines Google Drive with an AI provider. ## Example: Proposal Workflow Imagine you're building sales software. You could create: ```text theme={null} Opportunity ↓ Proposal ↓ Google Drive Document ``` Tell AIWA: > Allow sales representatives to attach an existing Google Drive proposal to an opportunity. Show the proposal from the deal detail page. Now the CRM and file system are connected. ## Folder Organization For applications with many records, folder organization can matter. For example: ```text theme={null} Clients ├── Acme Ltd │ ├── Website Redesign │ └── SEO Campaign │ ├── Northstar │ ├── Branding │ └── Ads ``` You can describe how your application's records should relate to those folders. For example: > Each client project should be associated with one Google Drive folder. Don't expose files from folders belonging to another customer. ## Permissions Matter A user being authenticated in your application doesn't automatically mean they should see every file in the shared Google Drive folder. Your application still needs authorization rules. For example: > Customers should only see Drive files associated with projects belonging to their account. Internal team members can see all files within their assigned workspace. Don't use the Google Drive connection as a substitute for application-level access control. Your application should still decide which users are allowed to see which files. ## Public vs Private Files Some files may be intended for: * Everyone * Signed-in users * Specific customers * Specific project members * Internal staff only Tell AIWA what access model you want. For example: > Marketing resources can be viewed by all authenticated customers, but project documents should only be visible to users associated with that project. This gives AIWA clearer requirements for the file experience. ## File Metadata Your application may want to display information such as: * Filename * File type * Updated date * Owner * Project * Folder * Link For example: ```text theme={null} Campaign Brief.pdf PDF · Updated Aug 24 [Open] ``` You can ask AIWA to display the metadata that matters for your product. ## Searching Files If a project contains many files, users may need search. For example: > Add search to the project Files section so users can search documents by filename. Or: > Add filters for PDF, document, spreadsheet, and image files. The exact functionality depends on what information the Drive integration makes available. ## Uploading Files If the connector supports the required upload workflow, you may want users to add files to Drive through your application. For example: > Allow project managers to upload approved documents to the project's connected Google Drive folder from inside the application. You should also define: * Who can upload * Which folder receives the file * Accepted file types * Maximum file size * Whether customers can upload * What happens after upload The available upload behavior depends on the Google Drive capabilities supported by your AIWA connector. ## Deleting Files File deletion is potentially destructive. If your application allows it, define the permission rules carefully. For example: > Customers can download files but cannot delete them. Only workspace Owners and Admins can remove Drive files from the project. You may also want a confirmation step before destructive actions. ## Updating Files Google Drive files may change outside your AIWA application. For example, someone might update a document directly in Drive. Your application should ideally use the current Drive information rather than maintaining stale duplicate copies where appropriate. Think carefully about whether your application needs to: > Reference the Drive file or > Copy its contents into your own database. Those are different architectures. ## Google Drive vs Cloudinary Google Drive and Cloudinary serve different use cases. **Cloudinary** Best suited to application media workflows such as: * Profile photos * Product images * Property galleries * Image optimization * Media delivery **Google Drive** Better suited to file and document workflows such as: * Client documents * Project resources * Internal files * Shared documents * Drive-based business workflows For example: ```text theme={null} Property Photo → Cloudinary ``` while: ```text theme={null} Signed Property Contract → Google Drive ``` The right connector depends on the type of content and how your product needs to use it. ## Google Drive + AI Drive becomes particularly interesting when combined with AI models. For example: ```text theme={null} Drive Document ↓ OpenAI / Claude / Gemini ↓ Summarize ↓ Extract ↓ Classify ↓ AIWA Application ``` You could ask: > Allow users to select a document from Google Drive and generate a structured summary containing key points, decisions, deadlines, and action items. Or: > Analyze a selected proposal and extract the customer, price, scope, and delivery timeline into the CRM. This turns files into usable application workflows. ## Google Drive + Client Portal A strong combined workflow could be: ```text theme={null} Agency Uploads File ↓ Google Drive ↓ Project Record ↓ Client Portal ↓ Customer Opens File ``` You could then add: > Notify the customer through Resend whenever a new approved project file becomes available. Now another connector joins the workflow. ## Google Drive + Resend For example: > When a project manager adds a new approved document to a customer's project, email the customer and include a link back to the Files section of their portal. Conceptually: ```text theme={null} New Project File ↓ Application ↓ Resend ↓ Customer Notification ``` ## Common Problems ### Files don't appear First determine whether: * Google Drive is connected * The folder is shared with the service account * The expected folder/file exists * The application is using the correct reference * The signed-in user has permission to see it ### Wrong customer's files appear This is a serious authorization issue. Tell AIWA: > Customer A can see Google Drive files belonging to Customer B. Audit the file authorization and project-to-folder relationship immediately. Ensure users can only access files associated with projects they are authorized to view. ### File link doesn't work Check whether the file still exists and whether the user's access model allows them to open it. ### Files are outdated Determine whether your application is storing stale metadata rather than retrieving the current Drive information where appropriate. ### The folder can't be reached Check: * The Google Drive API is enabled in your Google Cloud project * The folder is shared with the service account's email address, with Editor access * The Target folder ID is correct * The service account key still exists in the Google Cloud console Provide any Google error message to Debug Mode without sharing your service account key. ## Debugging Google Drive A good Debug Mode prompt might look like: > Expected: When a customer opens the Files tab, they should see documents associated with their projects. > > Actual: The project loads correctly, but the Files tab is empty. > > The Google Drive folder contains documents. > > Other project functionality works normally. > > Error: \[PASTE ERROR IF AVAILABLE] > > Debug the Google Drive integration and project-to-folder relationship without changing the rest of the portal. This helps isolate the file workflow. ## Test Your Drive Workflow Before publishing, test: * Shared folder access * Correct folder * File listing * File links * Customer authorization * Team authorization * Multiple customers * Multiple projects * Empty folders * Missing files * Renamed files * Updated files * Uploads, if supported * Deletion permissions, if supported * Mobile experience Most importantly, test data isolation using different user accounts, not only your administrator account. ## A Good Google Drive Prompt Define: * What files are involved? * Which application record owns them? * Who can access them? * Where should they appear? * What actions can users perform? For example: > Add a Files tab to each client project. Associate each project with its Google Drive folder and show the files from that folder inside the project. Customers should only see files belonging to projects associated with their account. Internal workspace members can see files for projects they have access to. Display filename, file type, and last updated date, and provide an Open action. Customers must not be able to delete files. That's much stronger than: > Connect Google Drive. ## Think in File Workflows A useful mental model is: ```text theme={null} APPLICATION RECORD ↓ DRIVE FILE / FOLDER ↓ ACCESS CONTROL ↓ USER EXPERIENCE ↓ OPTIONAL AUTOMATION ``` Google Drive stores and manages the files. AIWA builds the application experience around them. ## Next: Request a Connector You've now seen every connector currently available in AIWA: * Stripe * PayPal * Resend * Twilio * Cloudinary * OpenAI * Anthropic * Google Gemini * xAI * Calendly * Google Calendar * Google Meet * Google Drive But your application may need another service. Next, we'll cover Request a Connector: what to do when the integration you need isn't currently available inside AIWA. Learn how to request a new integration when the one you need isn't available. # Google (Gemini) Source: https://docs.aiwa.codes/integrations/google-gemini Connect Google Gemini to power AI assistants, generation, extraction, and multimodal features inside apps you build with AIWA. The Google Gemini connector lets applications you build with AIWA use Gemini models for AI-powered features. You can use Gemini inside your application for experiences such as: * AI assistants * Content generation * Summarization * Classification * Data extraction * Document analysis * Multimodal workflows * Customer support * AI-powered automation * Structured generation Once Gemini is connected, tell AIWA what the AI feature should do inside your product. **Connect Gemini. Define the experience. AIWA builds the workflow around it.** ## AIWA vs Gemini AIWA is the product-building environment. Gemini is an AI provider your application can use as part of a feature. For example: > Build a customer insights dashboard with contacts, support history, recent activity, and account health. AIWA builds the application. Then: > Add an AI Summary button that analyzes the customer's recent activity and generates a concise account summary using Gemini. Gemini powers the AI step inside the product. ## Before You Start You'll need access to the Google AI service and the credentials required by AIWA's Gemini connector. API usage may incur charges according to your Google account, selected model, and request volume. Model availability, pricing, rate limits, and capabilities are controlled by Google and may change over time. ## Connect Gemini to AIWA Open your AIWA project and navigate to Connectors. Find Google Gemini and select it. AIWA Google Gemini Follow the setup flow and provide the information requested by AIWA. AIWA Google Gemini Config Once connected, Gemini becomes available for AI-powered features inside your application. Keep your Google AI credentials private. Configure them through AIWA's connector experience rather than exposing them in frontend code or public repositories. ## Build Your First Gemini Feature Suppose you're building an e-commerce management tool. You could tell AIWA: > Add an AI Product Assistant using Gemini. Users should provide a product name, features, audience, and tone. Generate a product description, five selling points, and three social media captions. The workflow might look like: ```text theme={null} Product Information ↓ Generate ↓ Server-Side Logic ↓ Gemini ↓ Structured Result ↓ Application ``` The user interacts with your product, not directly with the underlying model provider. ## Define the Input Tell AIWA what context the model needs. For example: > Use the product name, category, features, target audience, price point, and brand tone. Or: > Use the customer's latest enquiry and previous support messages. Or: > Use the document text and the user's selected analysis goal. The feature should provide Gemini only with the information relevant to the task. ## Define the Output Be clear about the result you want. For example: > Return a 100-word product description, five bullet-point benefits, and three short social posts. Or: > Return category, sentiment, urgency, and recommended next action. Or: > Return an executive summary, key decisions, important dates, and action items. This makes it easier for AIWA to build a structured experience around the response. ## Example: AI Content Assistant Suppose you're building a marketing platform. You could ask: > Add a Content Assistant using Gemini. Users should enter their business, offer, audience, platform, and tone. Generate five content ideas and let users expand any idea into a complete post. Now the experience becomes: ```text theme={null} Business Context ↓ Gemini ↓ 5 Ideas ↓ User Selects One ↓ Generate Full Post ↓ Edit / Save ``` That's a complete AI workflow rather than a single generation button. ## Example: Customer Support For a support application: > Add an AI Suggested Reply button using Gemini. Use the current ticket and recent conversation context to draft a concise response. Show the draft to the support agent for review before sending. This keeps a human in control of customer communication. ## Example: Structured Lead Analysis For a CRM: > When a new lead submits an enquiry, use Gemini to extract their likely service requirement, budget, urgency, industry, and purchase intent. Save the structured result to the lead record. Conceptually: ```text theme={null} Lead Enquiry ↓ Gemini ↓ Structured Fields ↓ Neon ↓ CRM ``` The AI result becomes usable application data. ## Example: Document Analysis Gemini can also be used in document-oriented workflows. For example: > Add a document analysis feature using Gemini. Return an executive summary, key themes, important dates, and action items. You can then expand the feature: > Let users ask follow-up questions about the analyzed document. That turns one-time analysis into a more interactive experience. ## Multimodal Use Cases Depending on the Gemini model and API capabilities available to your account, some Gemini workflows may be able to work with more than text. That can make Gemini useful for product experiences involving combinations of content types. For example, an application might analyze: * Text * Images * Documents * Other supported inputs Available multimodal capabilities depend on the Gemini model you're using. Check Google's current model documentation before designing a feature around a specific input type. ## Human Review For important actions, consider requiring a person to review AI output before anything external happens. For example: > Use Gemini to generate a proposal draft, but require the account manager to review and approve it before sending. Conceptually: ```text theme={null} Gemini Generates ↓ Human Reviews ↓ Human Approves ↓ Action Happens ``` This is especially useful for: * Customer communication * Financial decisions * Business recommendations * Sensitive content * High-impact workflows ## Save or Regenerate? Decide whether AI output should become permanent application data. For example: > Save approved AI summaries to the customer record. Or: > Don't save the result until the user clicks Save. Or: > Use the existing stored summary unless the user explicitly clicks Regenerate. This can improve both user experience and API efficiency. ## Model Selection Google may offer multiple Gemini models with different strengths. Your choice may depend on: * Speed * Cost * Reasoning quality * Context requirements * Supported input types * Output requirements Instead of automatically choosing the most powerful option, choose based on the product need. For example: > This feature performs thousands of short classifications, so prioritize speed and cost efficiency. Or: > This feature performs complex document analysis, so prioritize quality and deeper reasoning. ## Handle Loading and Errors AI generation can take time or fail. Your application should make both states clear. For loading: > Analyzing... For failure: ```text theme={null} We couldn't complete the analysis. [Try Again] ``` You can tell AIWA: > Preserve the user's original input if the Gemini request fails and allow them to retry without starting over. ## Avoid Unnecessary Requests Don't call Gemini repeatedly when the existing result is still valid. For example: > Don't regenerate the customer summary every time the page loads. Store the result and only regenerate when the user requests it or the underlying customer data changes significantly. This can reduce latency and unnecessary API usage. ## Sensitive Data Before sending application information to Gemini, consider whether the feature actually requires it. Avoid sending: * Passwords * API keys * Authentication secrets * Private credentials * Unnecessary sensitive information Never include secret credentials as Gemini prompt context. For applications handling sensitive business or customer information, make sure your use of the external model provider fits your privacy and compliance requirements. ## Common Problems ### Gemini feature doesn't respond Check whether: * The connector is configured correctly * The server request is being made * Google returns an error * The application receives the result * The interface displays it correctly Use Debug Mode with the specific behavior you observe. ### Output isn't useful The problem may be the prompt or context rather than the connector. For example: > The generated summaries are too generic. Improve the Gemini prompt so every summary includes the customer's problem, urgency, budget, objections, and recommended next step. ### Output structure is inconsistent If your application expects structured information, make that explicit. For example: > Ensure Gemini always returns category, urgency, sentiment, and recommendedAction in a predictable structured format. Validate the response before saving it. ### Responses are slow Ask AIWA to inspect: * Model choice * Input size * Output length * Number of calls * Application workflow ### API usage is unexpectedly high Check whether the feature is triggering unnecessarily. For example: > Audit the Gemini workflow and make sure customer summaries aren't regenerated every time the page loads. ## Debugging Gemini A good Debug Mode prompt could be: > Expected: Clicking Generate Insights should analyze the customer record and display a summary. > > Actual: The loading state appears, but no result is displayed. > > The customer data itself loads correctly. > > Error: \[PASTE ERROR IF AVAILABLE] > > Debug the Gemini request and response flow without changing the existing customer page. Don't include the API key. ## Test Your Gemini Feature Before publishing, test: * Normal inputs * Short inputs * Long inputs * Missing input * Loading states * Failed generation * Retry behavior * Structured output * Saved results * Regeneration * Permissions * Unexpected user input * API usage behavior If you're relying on multimodal capabilities, test each supported input type separately. ## A Good Gemini Prompt for AIWA Define: **Purpose** What should Gemini accomplish? **Input** What context does it receive? **Output** What should it return? **User experience** How does the user interact with the result? **Persistence** Should the result be stored? **Permissions** Who can use it? For example: > Add an AI Customer Insight feature using Gemini. Authorized account managers can click Generate Insight from a customer profile. Use the customer's profile, recent activity, support history, and active deals to generate a concise summary containing account health, key risks, opportunities, and recommended next actions. Display the result in structured sections and save the approved insight to the customer record. ## Choosing an AI Provider You don't need every AI provider in every application. You might choose between: * OpenAI * Anthropic * Google Gemini * xAI based on your preferred models, capabilities, cost, response characteristics, and the product experience you're building. AIWA gives you flexibility to build around the provider that fits your use case. ## Next: xAI (Grok) Connect xAI and use Grok inside your AIWA application. # Google Meet Source: https://docs.aiwa.codes/integrations/google-meet Connect Google Meet to create video meeting links for bookings, demos, consultations, and virtual appointments in your AIWA app. The Google Meet connector lets applications you build with AIWA create and use video meeting links as part of your product workflows. You can use Google Meet for: * Sales demos * Consultations * Customer onboarding * Interviews * Virtual appointments * Team meetings * Coaching sessions * Support calls Google Meet becomes especially useful when combined with Google Calendar. **Connect Google Meet. Define when a meeting should be created. AIWA builds it into the workflow.** ## Google Meet vs Google Calendar These connectors often work together, but they solve different parts of the experience. **Google Meet** provides the video meeting. **Google Calendar** manages the calendar event. For example: ```text theme={null} Consultation Confirmed ↓ Create Google Meet ↓ Create Google Calendar Event ↓ Add Meet Link ↓ Invite Customer ``` Together, they can create a complete remote-meeting workflow. ## Before You Start Google Meet links are created through the Google Calendar API, so this connector works like the Google Calendar connector: your app connects as a service account, using a key you create in the Google Cloud console, and adds the meeting to a calendar you've shared with it. There's no Google sign-in step. Depending on the workflow, you may also want to connect Google Calendar so your app can manage the calendar events themselves. Reliably creating Meet links needs a Google Workspace account with domain-wide delegation set up for the service account. On a personal Google account, creating a link usually fails, so your app lets you paste a meeting link by hand instead. ## Connect Google Meet to AIWA Open your AIWA project and go to Connectors. Find Google Meet and select it. AIWA Google Meet The connector page walks you through these steps: 1. In the Google Cloud console, pick or create a project and enable the Google Calendar API. 2. Under Credentials, create a service account, add a JSON key to it, and download the key file. 3. Paste the entire contents of the key file into the Service account key (JSON) field. 4. Share the calendar you want to use with the service account's email address, choosing "Make changes to events", and paste its Calendar ID into the Calendar ID field. AIWA Google Meet Config Once connected, you can ask AIWA to create meeting functionality inside your application. ## Create Your First Meeting Workflow Suppose you're building a consultation platform. Tell AIWA: > When a customer successfully books a virtual consultation, create a Google Meet link and attach it to the appointment. Show the meeting link on the customer's booking page. Conceptually: ```text theme={null} Booking Confirmed ↓ Google Meet ↓ Create Meeting ↓ Save Meeting Link ↓ Booking Page ``` The user books through your application and receives access to the meeting without you manually creating it. ## Example: Sales Demo For a SaaS sales workflow: > After a qualified lead schedules a product demo, create a Google Meet meeting and add the meeting link to the demo record. You could then combine it with Google Calendar: > Create the corresponding Google Calendar event, add the customer as an attendee, and include the Google Meet link. The workflow becomes: ```text theme={null} Lead Qualified ↓ Demo Scheduled ↓ Google Meet ↓ Google Calendar ↓ CRM Updated ``` ## Example: Customer Onboarding Suppose Agency customers receive an onboarding call. You could ask: > When an Agency customer schedules onboarding, create a Google Meet meeting, add it to the onboarding appointment, and show the meeting link in their dashboard. Then: > Send the customer an onboarding confirmation email through Resend containing the date, time, and meeting link. Now several connectors work together: ```text theme={null} Onboarding Scheduled ↓ Google Meet ↓ Google Calendar ↓ Resend ↓ Customer ``` ## Example: Virtual Appointment For a health, coaching, consulting, or professional-services application: > Allow customers to book either an in-person or virtual consultation. If they choose Virtual, create a Google Meet link and include it in the confirmed appointment. This adds conditional logic: ```text theme={null} Appointment Type ↓ Virtual? ↙ ↘ Yes No ↓ ↓ Create Physical Meet Location ``` AIWA can build the workflow around that product rule. ## Save the Meeting Link Your application may need to store the generated meeting information alongside the relevant record. For example: ```text theme={null} Appointment Customer: Sarah Chen Date: September 15 Time: 2:00 PM Meeting: meet.google.com/... ``` You could ask AIWA: > Save the generated Google Meet link to the appointment so both the customer and assigned team member can access it later. This prevents the meeting link from existing only temporarily. ## Control Who Can See the Link Meeting links should appear only where appropriate. For example: > Show the meeting link only to the customer who owns the booking and the team member assigned to the consultation. This combines meeting functionality with authentication and authorization. Don't expose private meeting details on public pages unless that's intentionally how your product is designed. ## Add Attendees When used alongside Google Calendar, you may want specific users invited. For example: > Add the customer and assigned account manager as attendees to the calendar event containing the Google Meet link. This creates a more complete meeting experience for both sides. ## Rescheduling If the meeting's date or time changes, your application should keep the surrounding workflow synchronized. For example: > If the consultation is rescheduled, update the Google Calendar event while preserving the existing Google Meet link where appropriate. The exact behavior depends on how you've designed the workflow. ## Cancellations If a meeting is cancelled: > Mark the appointment as cancelled, update or remove the associated Google Calendar event, and prevent the cancelled appointment from appearing in upcoming meetings. You may also choose to keep the meeting record for historical purposes. ## Avoid Duplicate Meetings A repeated page load should not create a new Meet link every time. Tie meeting creation to a real business event, such as: > Appointment confirmed rather than: > Booking page opened Conceptually: ```text theme={null} Booking #10482 ↓ One Meet Link ✓ ``` not multiple meeting links for the same appointment. ## Google Meet + Calendly You can also combine Google Meet with Calendly. For example: ```text theme={null} Customer ↓ Calendly ↓ Time Selected ↓ Google Meet ↓ Virtual Meeting ``` If your Calendly configuration already creates Google Meet links directly, avoid duplicating that functionality unnecessarily. The best implementation depends on where you want the meeting to be created and managed. ## Google Meet + Resend After creating a meeting, you can communicate the details. For example: > After the virtual consultation is confirmed, send the customer an email containing the appointment time and Google Meet link. The workflow becomes: ```text theme={null} Meeting Created ↓ Resend ↓ Confirmation Email ``` ## Google Meet + Twilio For reminders: > Send the customer an SMS reminder 30 minutes before the Google Meet consultation and include the meeting link. Be mindful of SMS length and applicable messaging requirements. ## Time Zones Virtual meetings often involve users in different locations. The Meet link itself isn't timezone-specific, but the surrounding event information is. Make sure the application clearly displays the meeting time in the appropriate timezone. For example: ```text theme={null} September 15 2:00 PM WAT ``` rather than simply: ```text theme={null} 2:00 PM ``` when participants may be in different regions. ## Common Problems ### Meeting link isn't created First determine whether the main appointment or booking succeeds. For example: > The booking is saved correctly, but no Google Meet link is generated. That isolates the issue to the Meet portion of the workflow. ### Meet link exists but isn't saved Tell AIWA: > Google Meet creates the meeting successfully, but the link disappears after refreshing the booking page. Save the meeting reference to the appointment record. ### Duplicate meeting links appear Tell AIWA: > One confirmed appointment is creating multiple Google Meet links. Audit the trigger and ensure one appointment maps to one meeting. ### Calendar event exists but has no Meet link If you're using Calendar + Meet together: > The Google Calendar event is created correctly, but it doesn't include the Google Meet link. Debug the meeting creation and event association without changing the appointment workflow. ### Google rejects the connection Check: * The Google Calendar API is enabled in your Google Cloud project * The calendar is shared with the service account's email address * The Calendar ID is correct * The service account key still exists in the Google Cloud console On a personal Google account, Google usually refuses to create Meet links even when everything else is set up: paste a meeting link by hand instead. Provide any Google error message to Debug Mode without exposing your service account key. ## Debugging Google Meet A good Debug Mode request looks like: > Expected: After a virtual consultation is confirmed, the application should create a Google Meet link and save it to the appointment. > > Actual: The appointment saves correctly, but no meeting link appears. > > Google Calendar event creation is working. > > Error: \[PASTE ERROR IF AVAILABLE] > > Debug the Google Meet portion of the workflow without changing the booking or calendar functionality. This gives AIWA a narrow problem to investigate. ## Test Your Meeting Workflow Before publishing, test: * Meeting creation * Saved meeting link * User access * Calendar association * Attendees * Rescheduling * Cancellation * Duplicate prevention * Time zones * Email confirmations * Mobile access * User permissions If your application supports both virtual and in-person appointments, test both paths. ## A Good Google Meet Prompt Define: * **Trigger:** When should the meeting be created? * **Participants:** Who attends? * **Storage:** Where should the link be saved? * **Visibility:** Who can access it? * **Calendar:** Should an event also be created? * **Notifications:** How should participants receive the link? For example: > When a customer confirms a virtual consultation, create a Google Meet meeting and save the link to the appointment. Create a matching Google Calendar event using the appointment date and time, add the customer and assigned consultant as attendees, and include the meeting link. Show the link in the customer's portal and consultant dashboard. Send the customer a confirmation email through Resend. If the appointment is cancelled, update the calendar and mark it cancelled in the application. That's a complete product workflow. ## Think in Meeting Workflows A useful model is: ```text theme={null} BOOKING ↓ MEETING CREATION ↓ CALENDAR ↓ PARTICIPANTS ↓ NOTIFICATIONS ↓ MEETING ``` Google Meet provides the video-meeting layer. AIWA builds everything around it into the product. ## Next: Google Drive Next, we'll look at Google Drive and how AIWA-built applications can work with files and documents stored in Google Drive. We'll cover use cases such as: * Client files * Shared documents * Project resources * File-driven workflows * Connecting application records to Drive content Connect Google Drive to work with files and documents in your AIWA app. # OpenAI Source: https://docs.aiwa.codes/integrations/openai Connect OpenAI to add AI assistants, generation, summarization, classification, and extraction to the apps you build with AIWA. The OpenAI connector lets you add AI-powered features to applications you build with AIWA. You can use OpenAI inside your application for experiences such as: * AI assistants * Content generation * Summarization * Classification * Information extraction * Customer support * Document analysis * Personalized recommendations * Structured data generation * AI-powered workflows Once OpenAI is connected, describe what you want the AI feature to do, what information it should receive, and what should happen with its response. **AIWA builds your product. OpenAI can power AI features inside it.** ## AIWA vs OpenAI It's important to understand the difference. You are already using AIWA to build and evolve your application. For example: > Build a customer support dashboard with tickets, customers, agents, and reporting. That's AIWA helping you create the product. But suppose the product itself needs an AI feature: > Add an AI assistant that reads a support ticket and drafts a suggested response for the support agent. That's where an AI provider such as OpenAI can become part of the application you're building. Conceptually: ```text theme={null} YOU ↓ AIWA ↓ Builds Your Application ↓ Your Customer Uses Application ↓ AI Feature ↓ OpenAI ↓ Response Returned to Application ``` The connector gives your application access to the external AI service. ## What You Can Build There are many ways to use OpenAI inside an AIWA application. **AI assistants** > Add an AI assistant that helps users understand their analytics. **Content generation** > Generate three product descriptions from the product information entered by the user. **Summarization** > Add a button that summarizes long customer conversations into key points. **Classification** > Automatically classify incoming support tickets as Billing, Technical, Account, or General. **Information extraction** > Extract the customer's name, company, budget, timeline, and requirements from their enquiry. **Recommendations** > Analyze the customer's preferences and suggest the most relevant products. **Workflow automation** > When a new sales lead arrives, generate a short qualification summary before displaying it in the CRM. These are AI capabilities inside your product. ## Before You Start You'll need an OpenAI account and the credentials required by AIWA's OpenAI connector. API usage through OpenAI may incur charges according to your OpenAI account, model selection, and usage. AIWA doesn't replace your OpenAI account when you're using the OpenAI connector inside an application. The connector allows the product you're building to communicate with the OpenAI service using your configured credentials. ## Connect OpenAI to AIWA Open your AIWA project and navigate to Connectors. Find OpenAI and select it. AIWA Openai Follow the connection flow and provide the information requested by AIWA. AIWA Openai Config Once connected, you can ask AIWA to build OpenAI-powered functionality into your application. Your OpenAI API key is sensitive. Configure it through AIWA's connector experience rather than placing it directly into frontend code. ## Build Your First AI Feature Let's create a simple content generator. Tell AIWA: > Add an AI Product Description Generator. Users should enter a product name, product features, target audience, and tone. When they click Generate, use OpenAI to create three different product descriptions. The experience might look like: ```text theme={null} Product Information ↓ Click Generate ↓ Server-Side Logic ↓ OpenAI ↓ AI Response ↓ Display 3 Descriptions ``` The user doesn't interact with OpenAI directly. They interact with the product you built. ## Define the Input AI features need context. Instead of: > Add an AI writer. Define what information the feature should receive. For example: > Users should provide a product name, description, key features, target customer, and desired tone. Now your application can collect structured information before sending the appropriate context to the AI model. Better input generally gives the feature a better chance of producing useful output. ## Define the Output Don't only tell AIWA what the model should receive. Tell it what you want back. For example: > Generate three product descriptions between 100 and 150 words each. Each description should include a headline and body copy. Or: > Return a short summary, sentiment, and recommended next action. Or: > Extract the customer's name, company, budget, timeline, and requested services. The clearer the expected result, the easier it is to design the feature around it. ## Structured AI Output Sometimes you don't want a paragraph. You want information your application can actually use. Imagine a CRM receives: > Hi, we're looking for a new website for our property company. Our budget is around \$15,000 and we'd like to launch within eight weeks. You might want OpenAI to extract: ```text theme={null} Service: Website Development Budget: $15,000 Timeline: 8 weeks Industry: Real Estate ``` Now your application can use those values elsewhere. For example: ```text theme={null} Customer Enquiry ↓ OpenAI ↓ Structured Information ↓ CRM Lead ↓ Qualification Rules ↓ Sales Pipeline ``` This turns AI output into application data. ## Example: Support Assistant Suppose you're building customer support software. You could ask AIWA: > Add an AI Draft Reply button to support tickets. When clicked, send the ticket message and recent conversation context to OpenAI and generate a suggested response. Show the draft in the reply editor but don't send it automatically. That last sentence matters. The workflow becomes: ```text theme={null} Support Ticket ↓ Draft with AI ↓ OpenAI ↓ Suggested Reply ↓ Agent Reviews ↓ Agent Edits ↓ Agent Sends ``` The AI assists the human rather than automatically communicating with the customer. ## Example: Lead Qualification OpenAI can also participate in automated workflows. For example: > When a new lead is submitted, use OpenAI to analyze their message and create a short qualification summary. Identify their likely service requirement, urgency, and purchase intent. Save the result to the lead record. Conceptually: ```text theme={null} Lead Submitted ↓ Save Lead ↓ OpenAI Analysis ↓ Qualification ↓ Save AI Result ↓ CRM ``` The sales team now receives additional context without manually analyzing every enquiry. ## Example: Document Summarization Suppose your application handles long documents. You could tell AIWA: > Add a Summarize button to uploaded documents. Use OpenAI to generate an executive summary, key points, and recommended actions. The result might be: ```text theme={null} Executive Summary Key Points • ... • ... • ... Recommended Actions • ... • ... ``` The application can present the AI response in a structured interface rather than simply showing raw text. ## Example: AI Content Generator Imagine you're building a marketing platform. Users enter: * Product * Audience * Offer * Tone * Platform Then: > Generate five social media posts based on this information. You could also add: > Let users regenerate individual posts without regenerating the entire set. Or: > Allow users to edit generated content before saving it. This creates a complete AI product experience rather than just a Generate button. ## AI Features Need Good UX An AI integration isn't complete simply because the model returns text. Think about the user's experience before, during, and after generation. For example: ```text theme={null} Input ↓ Generate ↓ Loading ↓ Result ↓ Edit ↓ Regenerate ↓ Save ``` Depending on the feature, users may need: * Generate * Stop * Retry * Regenerate * Edit * Copy * Save * Delete * Provide feedback Tell AIWA which interactions matter for your product. ## Loading States AI responses can take time. Your application should make it clear that generation is happening. For example: > Generating your analysis... rather than leaving the user wondering whether the button worked. You can ask: > Show a loading state while the AI response is being generated and prevent duplicate generation requests. ## Error States AI requests can fail. For example: ```text theme={null} Generate ↓ OpenAI Request ↓ Error ↓ Show Message ↓ Retry ``` Tell AIWA: > If generation fails, keep the user's original input and show a Retry button. Don't clear the form. Good failure handling is particularly important when users have spent time entering information. ## Saving AI Responses Decide whether generated results should disappear when the page is closed or become part of the application's permanent data. For example: > Save generated lead summaries to the lead record so sales agents don't need to regenerate them every time they open the lead. Or: > Don't save generated suggestions until the user clicks Save. This is a product decision. ## AI + Your Database AI becomes more useful when combined with application data. For example: ```text theme={null} Customer ↓ Orders ↓ Support History ↓ OpenAI ↓ Customer Summary ``` You might ask: > Add an AI-generated customer summary to the CRM. Use the customer's profile, recent deals, and support history to create a concise summary for the account manager. However, only send information that the feature actually needs. ## Give the AI Relevant Context An AI feature can only reason about information available to it. Suppose you ask: > Recommend which lead the sales agent should contact next. The AI may need context such as: * Lead status * Budget * Last contact date * Purchase intent * Recent activity Without that information, the feature may have little basis for the recommendation. Think about: **What information does the AI need to perform this task well?** Then design the workflow around providing that context. ## Don't Send Everything Automatically More context isn't always better. Avoid sending an entire database when the feature only needs a few relevant fields. For example, a product-description generator probably needs: * Product name * Features * Audience * Tone It probably doesn't need: * Customer database * Billing records * Internal team notes Send the information required for the task. ## Sensitive Data Be careful when designing AI features involving private or sensitive user information. Before sending application data to an external AI provider, consider: * What information is being sent * Whether the feature actually requires it * What your users expect * Your privacy obligations * The external provider's applicable policies and configuration Don't send passwords, API keys, authentication secrets, or other credentials to an AI model as application context. ## Control What the AI Does For important workflows, don't give AI output more authority than necessary. For example, there is a meaningful difference between: > AI recommends which leads should be prioritized. and: > AI automatically deletes leads it considers low quality. Likewise: > AI drafts a customer response for review. is different from: > AI automatically sends whatever response it generates. For actions affecting money, customer communication, permissions, deletion, or other important outcomes, consider whether human review or additional validation should be required. ## Example: Human-in-the-Loop A useful pattern is: ```text theme={null} AI Generates ↓ Human Reviews ↓ Human Approves ↓ Action Happens ``` For example: > Generate a personalized sales email using OpenAI. Show the email to the sales representative for editing and approval before sending it through Resend. Now two connectors can work together: ```text theme={null} CRM Data ↓ OpenAI ↓ Draft Email ↓ Sales Rep Reviews ↓ Resend ↓ Customer ``` This is a powerful example of AIWA building workflows across multiple services. ## AI Usage Has a Cost Requests made through the OpenAI connector can incur API usage charges on the connected OpenAI account. Usage depends on factors such as: * Model * Amount of input * Amount of output * Number of requests * Application usage This matters when building features used frequently by customers. For example: ```text theme={null} 10 users × 5 generations/day = 50 requests/day ``` is very different from: ```text theme={null} 100,000 users × 20 generations/day = 2,000,000 requests/day ``` Design AI features with usage in mind. ## Prevent Unnecessary Requests You may want to prevent users from accidentally generating the same thing repeatedly. For example: > Disable the Generate button while a generation is already in progress. Or: > Don't automatically regenerate the summary every time the user opens the page. Use the existing summary unless they request a new one. These decisions can improve both user experience and API efficiency. ## Model Selection Different OpenAI models may offer different capabilities, performance characteristics, and costs. If your feature requires a particular model, you can specify it. Otherwise, you can describe the task and let the implementation use an appropriate supported option. For example: > This feature prioritizes speed and low cost because it classifies thousands of short support messages. Or: > This feature performs more complex analysis where reasoning quality is more important than response speed. The model should fit the product requirement. Available OpenAI models and pricing can change over time. Refer to OpenAI for current model availability and API pricing. ## Common Problems ### AI feature doesn't respond Determine whether: * The button/action works * The server request is being made * OpenAI credentials are valid * OpenAI returns an error * The application fails to display the result Then give AIWA the specific behavior. ### Output quality is poor This isn't always a connector problem. The instructions or context sent to the model may need improvement. For example: > The AI-generated lead summaries are too generic. Analyze the current OpenAI prompt and improve it so summaries include the lead's requirement, budget, urgency, objections, and recommended next action. ### Output format is inconsistent If your application needs structured information, tell AIWA explicitly. For example: > The lead classifier sometimes returns paragraphs instead of the fields the application expects. Make the AI response structured and validate it before saving the result. ### Responses are too slow Ask AIWA to investigate: * Model selection * Amount of context * Output length * Number of requests * Application architecture Don't assume the interface itself is the cause. ### Usage is unexpectedly high Investigate whether requests are being triggered unnecessarily. For example: > OpenAI usage appears unusually high. Audit where AI requests are triggered and check whether the customer summary is being regenerated on every page load. ## Debugging OpenAI A useful Debug Mode request looks like: > Expected: Clicking Generate Summary should analyze the lead and display a short qualification summary. > > Actual: The loading state appears, but no result is displayed. > > The lead data itself loads correctly. > > Error: \[PASTE ERROR IF AVAILABLE] > > Debug the OpenAI generation workflow without changing the existing lead interface. Don't include your API key in the debugging prompt. ## Test Your AI Feature Before publishing, test: * Normal inputs * Very short inputs * Long inputs * Empty inputs * Invalid inputs * Loading states * Failed generations * Retry behavior * Output formatting * Saving results * Regeneration * User permissions * API usage behavior Also test whether the AI behaves reasonably when users provide unexpected instructions or unusual input. ## A Good OpenAI Prompt for AIWA When asking AIWA to build an AI feature, define: **Purpose** What should the AI accomplish? **Input** What information does it receive? **Output** What should it return? **Context** What application data does it need? **User experience** How does the user interact with the result? **Persistence** Should the result be saved? **Permissions** Who can use the feature? For example: > Add an AI Lead Summary feature using OpenAI. On each lead detail page, authorized sales users can click Generate Summary. Use the lead's enquiry, budget, source, status, and recent activity to generate a concise summary containing their requirement, purchase intent, urgency, and recommended next action. Show a loading state while generating and allow the user to regenerate. Save the approved summary to the lead record. That's a product specification, not merely: > Add ChatGPT. ## Think in AI Workflows A useful mental model is: ```text theme={null} USER / EVENT ↓ RELEVANT CONTEXT ↓ OPENAI ↓ STRUCTURED RESULT ↓ APPLICATION ↓ USER / NEXT ACTION ``` The OpenAI model is one component. Your application is the product. AIWA helps you build the complete experience around the model. ## Next: Anthropic (Claude) OpenAI is one AI provider available through AIWA connectors. Next, we'll look at Anthropic (Claude) and how you can use Claude-powered capabilities inside applications you build with AIWA. Because we've now covered the fundamentals of building AI features, the Claude page will focus primarily on: * Connecting Anthropic * Building with Claude * Choosing it for appropriate use cases * Example workflows * Troubleshooting rather than repeating all the AI architecture concepts covered here. Connect Anthropic and use Claude for reasoning-heavy AI features. # What Are Connectors? Source: https://docs.aiwa.codes/integrations/overview Connectors bridge your AIWA app to Stripe, Resend, Twilio, Cloudinary, AI providers, and more without exposing secret credentials. AIWA can build the database, authentication, interface, APIs, and server-side logic your application needs. But many products also need to communicate with services outside AIWA. You might want to: * Accept payments with Stripe or PayPal * Send transactional emails with Resend * Send SMS messages with Twilio * Store and deliver media with Cloudinary * Add AI features using OpenAI, Claude, Gemini, or Grok * Connect calendars and meetings * Access files from Google Drive Connectors allow your AIWA applications to work with these external services. > **Connect the services your product needs. Then tell AIWA what you want to build with them.** ## What is a connector? A connector is a bridge between your AIWA application and an external service. For example, imagine you're building a SaaS application and want customers to pay for subscriptions. AIWA can build: * Your pricing page * Plan selection * Checkout flow * Subscription logic * Billing interface * Feature restrictions But the actual payment processing can be handled by Stripe. The Stripe connector gives your application the connection it needs to work with Stripe. Conceptually: ```text theme={null} Your Application ↓ AIWA ↓ Stripe Connector ↓ Stripe ``` The same principle applies to other supported services. ## Why connectors are needed Some functionality belongs to your application. Other functionality depends on specialized external platforms. For example: | Your application needs | External service | | - | - | | Payment processing | Stripe, PayPal | | Transactional email | Resend | | SMS & communications | Twilio | | Media storage & delivery | Cloudinary | | AI capabilities | OpenAI, Anthropic, Google, xAI | | Scheduling | Calendly | | Calendar functionality | Google Calendar | | Meetings | Google Meet | | Files | Google Drive | Instead of trying to recreate these services, AIWA can connect them to the product you're building. ## Connect once, then build The connector workflow is designed to separate configuration from product development. For example, instead of repeatedly providing Stripe credentials whenever you want to change your billing system, you connect Stripe through AIWA's connector experience. Then you can focus on requests such as: > Add a Pro subscription for \$49/month. Later: > Add a billing page where customers can see their current plan and manage their subscription. Then: > Restrict the analytics dashboard to Pro subscribers. You're describing your product. The connector provides access to the external service required to power the experience. ## Connecting a service isn't the same as building with it This is an important distinction. Connecting Stripe doesn't automatically add payments to your application. Connecting Resend doesn't automatically start sending emails. Connecting OpenAI doesn't automatically add AI features. A connector makes the external service available for your application to use. You still tell AIWA what you want to build. For example: ```text theme={null} CONNECT STRIPE ↓ Stripe becomes available ↓ "Add monthly subscriptions" ↓ AIWA builds the billing workflow ↓ Test ↓ Publish ``` Think of connectors as giving your AI product team access to additional capabilities. ## Connecting a Service AIWA Connectors The exact information required depends on the service you're connecting. A service may require something such as: * API key * Secret key * Account authorization * Project identifier * Other service-specific credentials AIWA will guide you through the information required for the supported connector. Each connector has its own setup guide in this documentation. We'll show you where to obtain the required credentials and how to connect them to AIWA. ## API keys explained Many external services use an API key to identify and authorize your application. An API key may look something like: ```text theme={null} sk_•••••••••••••••••••••• ``` You can think of it like a credential that allows your application to communicate with a service. For example, Resend needs to know that your application is authorized to send email through your Resend account. The API key provides that authorization. ## API keys are sensitive Many API keys provide access to important functionality or account resources. Treat secret API keys like passwords. Never place secret API keys directly into public frontend code, screenshots, documentation, support messages, or other places where they could be exposed. Don't write prompts such as: > My Stripe secret key is sk\_live\_xxxxxxxxx. Put it directly into the checkout code. Instead, add credentials using the supported connector or secure configuration experience provided by AIWA. ## Public keys vs secret keys Not every key has the same security requirements. Some services provide both public and secret credentials. For example: **Publishable Key** Can be used where the service specifically allows client-side use. **Secret Key** Must remain private and should only be used in secure server-side environments. AIWA's connector-specific guides will explain which credentials are required. When in doubt, treat a credential as private. ## How AIWA Uses Connectors Once a service is connected, you can describe the functionality you want. For example, after connecting Resend: > When someone submits the contact form, send them a confirmation email and notify our sales team. AIWA can build the workflow around the connected service. Conceptually: ```text theme={null} Contact Form ↓ Submission ↓ Save to Neon ↓ Server-Side Logic ↓ Resend Connector ↓ Confirmation Email ``` The user experiences a contact form. Behind it, multiple systems work together. ## Example: Stripe Suppose you're building a SaaS application. First, connect Stripe. Then tell AIWA: > Add Starter, Pro, and Business subscriptions at \$19, \$49, and \$99 per month. Customers should be able to choose a plan from the pricing page and manage their subscription from Account Settings. AIWA can use the connected Stripe service while building the required billing workflow. Your product might eventually involve: ```text theme={null} Pricing Page ↓ Select Plan ↓ Stripe Checkout ↓ Payment ↓ Payment Confirmation ↓ Update Subscription ↓ Unlock Features ``` We'll cover the full Stripe setup on the next page. ## Example: Resend Connect your Resend account. Then: > Send a welcome email whenever a new user successfully creates an account. Or: > Send customers a confirmation email after their booking is created. Or: > Email the assigned sales representative whenever a new qualified lead enters the CRM. The connector handles access to the email service. Your prompt defines when and why it should be used. ## Example: AI Models You can also connect supported AI providers when your application needs AI functionality. For example, after connecting an AI provider: > Add an AI assistant to the customer support dashboard. It should help agents draft responses using the customer's conversation context. Or: > Add a product description generator. Users should provide a product name, features, target customer, and tone, then generate three descriptions. This lets you use AI capabilities inside the applications you build with AIWA. ## Connectors can work together Your product isn't limited to using one external service. Imagine you're building an AI sales platform. It might use: ```text theme={null} Neon ↓ Customer & lead data OpenAI ↓ Generate personalized outreach Resend ↓ Send emails Twilio ↓ Send SMS Stripe ↓ Manage customer subscriptions ``` AIWA can build workflows that combine multiple systems. For example: > When a new lead submits the consultation form, save the lead, use AI to generate a short qualification summary, show it in the CRM, and email the sales team. One user action can trigger a workflow involving several parts of your product. ## Credentials and Security Credentials used by connectors should be treated as sensitive application secrets. AIWA's connector experience is designed so that you can configure the credentials required by your application without intentionally placing secret values into public-facing application code. You should still follow good security practices: * Don't share secret keys with other users * Don't put secrets into frontend code * Don't publish keys in GitHub repositories * Don't include real keys in screenshots * Don't paste secrets into public documentation * Revoke credentials if you believe they've been exposed * Use test credentials while developing when the provider supports them If you accidentally expose an API key, don't simply delete it from the page or code. Revoke or rotate the compromised credential through the service provider. ## Test and production credentials Some services provide different environments for development and production. Stripe, for example, provides testing capabilities so you can build payment workflows without charging real customers. Where supported, a good workflow is: ```text theme={null} Connect Test Credentials ↓ Build ↓ Test ↓ Verify ↓ Configure Production ↓ Publish ``` Don't test critical payment functionality for the first time using real customer transactions. ## What happens if a connector stops working? An external integration can fail for several reasons. For example: * A key was revoked * A credential expired * The account configuration changed * The service rejected a request * Required permissions are missing * A provider is temporarily unavailable If functionality that depends on a connector stops working, first identify whether the issue is with: **Your application** or **the external service connection.** For example: > Booking records are being created correctly, but confirmation emails stopped sending. That suggests the booking workflow itself may be working while the email portion requires investigation. Use Debug Mode and describe exactly what is happening. ## Give AIWA useful debugging information For example: > Confirmation emails stopped sending through Resend. Bookings are still being saved successfully. Debug the email portion of the booking workflow without changing the existing booking functionality. If you have an error message, include it. But don't paste the secret credential itself. ## Removing or changing a connection You may eventually need to: * Replace an API key * Rotate a compromised credential * Change accounts * Move from test to production credentials * Stop using an integration Use the connector's configuration experience to update the connection. When changing an integration used by a live application, test the affected workflows afterward. For example, after changing Stripe configuration, test: **Checkout → Payment confirmation → Subscription update → Feature access** Don't assume that updating the credential automatically means the complete workflow still behaves correctly. ## Before connecting a service Ask yourself: **What does my application need the service to do?** > Send booking confirmations. **Which service provides that capability?** > Resend. **Do I have the required account?** > Yes. **What credentials or authorization does it require?** > Follow the connector-specific guide. **What should happen in my application?** > After a booking is successfully created, send the customer a confirmation. This keeps the integration tied to an actual product requirement. ## Supported Connectors The following connector guides are covered in this section: **Payments** * Stripe * PayPal **Communication** * Resend * Twilio **Media** * Cloudinary **AI** * OpenAI * Anthropic (Claude) * Google (Gemini) * xAI (Grok) **Scheduling & Productivity** * Calendly * Google Calendar * Google Meet * Google Drive We'll walk through each service individually. ## Need another connector? If the service you need isn't currently supported, AIWA may still be able to work with its API depending on your application and the service's requirements. We'll also cover how to request a new connector at the end of this section. ## Next: Stripe Now that you understand how connectors work, we'll start with one of the most common integrations: **Stripe** You'll learn how to connect Stripe to AIWA and use it to build: * One-time payments * Subscription billing * Checkout flows * Billing management * Payment-driven application workflows Connect Stripe and build one-time payments, subscriptions, and billing. # PayPal Source: https://docs.aiwa.codes/integrations/paypal Connect PayPal to accept PayPal, Pay Later, and card payments, and PayPal subscriptions, in the checkout flows you build with AIWA. The PayPal connector lets applications you build with AIWA accept payments through PayPal. You can use PayPal for: * A PayPal button at checkout * One-time payments for orders, bookings, and tickets * Pay Later, where the buyer is eligible * Card payments through the PayPal button * Monthly subscriptions * Testing everything with sandbox accounts before real money moves **Connect PayPal. Describe what customers pay for. AIWA builds the checkout.** ## PayPal vs Stripe Both connectors accept payments. Many products use one; some offer both. | You want to | Use | | - | - | | Let customers pay with their PayPal balance or Pay Later | PayPal | | A card checkout hosted by your payment provider | Stripe | | Offer customers a choice at checkout | Both | If you ask for payments without naming a provider, AIWA uses the payment connectors you've connected. To be sure, name PayPal in your request. ## Before You Start You'll need: * A PayPal account to sign in to the PayPal developer dashboard * A PayPal Business account when you're ready to accept real payments You can build and test everything with sandbox credentials first. ## Connect PayPal to AIWA Sign in at developer.paypal.com with your PayPal account. Open Apps & Credentials and make sure the Sandbox toggle is selected. Open the Default Application, or click "Create App" and name it after your project. Copy the Client ID and the Secret. Open your AIWA project, go to Connectors, and select PayPal. Paste the Client ID and the Secret, and set Mode to sandbox. You can also set a Currency. Use your PayPal account's main currency: a payment in another currency can wait in your PayPal account until you accept it by hand. If you leave it empty, prices are in US dollars (USD). Once connected, the connector page checks your credentials with PayPal. If they belong to the other mode, it tells you which Mode to choose. Your PayPal Secret is sensitive. Add it through the connector page, never in a prompt or in your application's frontend code. ## Test with Sandbox Accounts In sandbox mode, no real money moves. To pay in your preview, sign in to the PayPal window with a sandbox buyer account, not your real PayPal login. You'll find one in the PayPal developer dashboard under Testing Tools, then Sandbox Accounts. While your app runs in sandbox mode, its checkout says so, and tells you which login to use. ## Your First PayPal Checkout Suppose you sell tickets for an event. Tell AIWA: > Let visitors buy tickets for my event with PayPal. Show the ticket type and price, add a PayPal button, and email the buyer their ticket after payment. The workflow might look like: ```text theme={null} Visitor chooses ticket ↓ Order created ↓ PayPal button ↓ Buyer approves ↓ Payment captured on the server ↓ Order marked paid ``` The PayPal button shows PayPal, Pay Later, and card options, depending on what the buyer is eligible for. ## How Payment Is Confirmed An order is only marked paid when your app's server has captured the payment with PayPal and PayPal reports it as completed. Reaching a success page in the browser isn't proof of payment, so your app never relies on it. Your app doesn't need webhooks for this. The capture answers straight away, so the confirmation happens in the same request. If the buyer closes the page halfway through, your app can pick up the same order rather than creating a new one, so nobody pays twice. ## Subscriptions PayPal can also charge a monthly subscription. For example: > Charge a monthly PayPal subscription for the Pro plan at \$29. Only active subscribers can open the reports page. Conceptually: ```text theme={null} Choose plan ↓ PayPal subscription ↓ Buyer approves ↓ Status checked ↓ Access granted ``` Your app checks the subscription with PayPal before granting access, and again regularly afterwards: * Only an active subscription unlocks paid features. * A subscription cancelled or suspended in PayPal loses access, even if the customer never returns to your app. * If PayPal can't be reached, the customer is asked to try again rather than given access. ## Go Live When you're ready for real customers: 1. Switch the toggle in the PayPal developer dashboard to Live. This needs a PayPal Business account. 2. Copy the live Client ID and Secret. 3. Paste them on the PayPal connector page and set Mode to live. 4. Make a small real payment to confirm the whole flow. Refunds and disputes are handled in your PayPal account. ## Common Problems ### PayPal says the credentials belong to the other mode Sandbox and live credentials are different. Set Mode to match where you copied them from, or paste the credentials for the mode you want. ### PayPal rejects the Client ID and Secret Check that both were copied in full from the same app in the PayPal developer dashboard, and that the app hasn't been deleted. ### You can't log in to the PayPal window in your preview In sandbox mode, use a sandbox buyer account from Testing Tools, then Sandbox Accounts. Your real PayPal login only works in live mode. ### A payment is waiting in PayPal The payment was in a currency your PayPal account doesn't hold. Accept it in your PayPal account, and set the Currency on the connector page to your account's main currency. ### A subscriber lost access Check the subscription's status in your PayPal account. Only an active subscription unlocks paid features. ## Debugging PayPal A good Debug Mode request might look like: > Expected: After a buyer approves the PayPal payment, the order should be marked paid and the ticket emailed. > > Actual: The buyer approves the payment, but the order stays pending. > > PayPal shows as connected in sandbox mode. > > Error: \[PASTE ERROR IF AVAILABLE] > > Debug the PayPal capture without changing the ticket selection. Never paste your PayPal Secret into a prompt. ## Test Your PayPal Workflow Before publishing, test: * A successful payment with a sandbox buyer account * A cancelled payment * Refreshing the page during checkout * The order status after payment * Confirmation emails * Subscribing, cancelling, and losing access * The correct currency and amounts * The checkout on mobile ## A Good PayPal Prompt A strong request defines: * **Product:** What is the customer paying for? * **Price:** How much, and in which currency? * **Type:** One-time payment or subscription? * **After payment:** What should happen once it's confirmed? * **Access:** What does a paying customer unlock? For example: > Add a PayPal checkout to the booking page. Charge the price of the selected session in GBP, mark the booking paid only after the payment is captured, and email the customer a confirmation. If the payment is cancelled, keep the booking as unpaid and let the customer try again. That's significantly stronger than: > Add PayPal. ## Next: Resend PayPal handles payments. Next, we'll connect your application to Resend so it can communicate with users through transactional email. Connect Resend and send transactional email from your AIWA app. # Request a Connector Source: https://docs.aiwa.codes/integrations/request-a-connector Request a new AIWA connector: describe the service, use case, actions, authentication, and workflows you need to build. AIWA supports a growing set of connectors for payments, email, communications, media, AI providers, scheduling, calendars, meetings, and file workflows. But you may need a service that isn't currently available as a built-in connector. In that case, you can request a new connector. **Tell us which service you need, what you want to build with it, and why it matters to your workflow.** ## Before requesting a connector First, check whether AIWA already supports the capability you need through an existing connector. For example: | Need | Existing connector | | - | - | | Payments | Stripe, PayPal | | Transactional email | Resend | | SMS | Twilio | | Images & media | Cloudinary | | AI models | OpenAI, Anthropic, Gemini, xAI | | Scheduling | Calendly | | Calendar events | Google Calendar | | Video meetings | Google Meet | | Files & documents | Google Drive | Sometimes the service you want isn't necessary if another supported connector already solves the underlying product requirement. ## Request the capability, not just the brand When requesting a connector, tell us what you're trying to accomplish. Instead of: > Add HubSpot. Tell us: > We use HubSpot as our CRM and want AIWA applications to create contacts and deals when users submit forms. That's much more useful. Or instead of: > Add Dropbox. Tell us: > Our agency stores client documents in Dropbox and we want client portals built with AIWA to display files associated with each project. Understanding the use case helps us evaluate the integration properly. ## What to include in your request A useful connector request includes: **Service** Which product or API do you want AIWA to support? **Use case** What are you trying to build? **Actions** What should your AIWA application be able to do with the service? **Frequency** Is this needed for one project or something you use regularly? **Business impact** What does this integration unlock for you or your clients? For example: ```text theme={null} Service: HubSpot Use case: Agency lead management Actions: Create contacts, create deals, update deal stages, retrieve contact information Why: All of our clients currently use HubSpot and we want AIWA-generated websites and apps to feed leads directly into their existing CRM. ``` That's an excellent connector request. ## Example requests **CRM** > Please add HubSpot. We want lead forms built with AIWA to create contacts and deals inside our clients' HubSpot accounts. **Automation** > Please add Zapier. We want AIWA apps to trigger workflows that connect with tools not yet available as native connectors. **Accounting** > Please add QuickBooks. We want invoices generated in our AIWA application to sync with our accounting workflow. **Storage** > Please add Dropbox. We want customers to access files associated with their projects from inside an AIWA-built client portal. **Communication** > Please add WhatsApp messaging. We want booking confirmations and customer updates to be sent through WhatsApp. The more specific the workflow, the easier it is to understand what the connector needs to support. ## Can AIWA use an API without a connector? Sometimes a service may expose an API even when AIWA doesn't yet have a dedicated connector for it. Depending on the service and your application, AIWA may be able to build a custom API integration. For example: > This service has a REST API. Review its API requirements and determine whether we can connect it to the application without a native AIWA connector. For custom integrations, you may need to provide information such as: * API documentation * Authentication method * Required endpoints * Expected request and response formats * Webhook documentation * Rate limits * Required permissions A custom API integration and a native AIWA connector are not necessarily the same experience. Native connectors are designed to simplify configuration and reuse across AIWA workflows. ## Use Explore Mode first If you're unsure whether a custom integration is possible, use Explore Mode. For example: > We need to connect this application to HubSpot. We don't currently have a native HubSpot connector. Analyze what would be required to integrate with HubSpot's API. Don't build anything yet. AIWA can help you understand the integration surface before implementation. ## Plan complex integrations Some external services require more than one API request. For example, an accounting integration might involve: * Customers * Products * Invoices * Payments * Taxes * Webhooks * Authentication * Data synchronization For integrations like these, use: **Explore → Plan + Max → Review → Build** rather than immediately attempting implementation. ## Authentication requirements matter External APIs can use different authentication methods. For example: * API keys * OAuth * Access tokens * Client credentials * Service accounts If you're requesting a connector, include any relevant information about how the provider authorizes applications. Don't send secret credentials in the request itself. ## Webhooks may be required Some integrations need the external service to notify your application when something changes. For example: ```text theme={null} External Service ↓ Webhook ↓ AIWA Application ↓ Update Database ``` If your intended workflow relies on real-time updates, include that in the connector request. For example: > When a deal changes stage in HubSpot, we need the associated record in our AIWA application to update automatically. That's very different from only creating HubSpot contacts. ## Read vs write access Explain whether your application needs to: **Read** Show customer information from the external service. **Write** Create or update information in the external service. or both. For example: > We need to read products from Shopify and create orders from our AIWA-built sales portal. This helps define the connector requirements. ## One-way vs two-way synchronization Some integrations only need information to move in one direction. For example: ```text theme={null} AIWA Lead Form ↓ HubSpot ``` Others require two-way synchronization: ```text theme={null} AIWA ↕ HubSpot ``` Two-way synchronization is significantly more complex because the application needs to determine what happens when information changes in either system. If you need synchronization, mention it explicitly. ## Prioritizing connector requests Connector requests help us understand which services AIWA users need most. When submitting a request, clearly explaining the business use case can help us evaluate its usefulness. A connector requested by many agencies for a repeatable workflow may have broader value than an integration needed for one unusual project. That doesn't mean uncommon requests aren't useful. It simply helps us understand the impact. ## Requesting a connector Use the connector request option available inside AIWA or contact AIWA Support with: ```text theme={null} Connector: [Service name] Website: [Service website] What are you building? [Use case] What should the integration do? [Required actions] Who will use it? [Your team / customers / agency clients] How often would you use it? [Frequency] Anything else we should know? [Additional context] ``` Do not include passwords, private API keys, or secret credentials in the request. ## Security Any new integration should be designed with appropriate credential handling and access controls. When requesting a connector: * Don't send secret keys * Don't send passwords * Don't expose access tokens * Don't include customer credentials * Share documentation links rather than private configuration * Describe the permissions the integration requires Credentials should only be supplied through the appropriate secure configuration flow when the integration is actually being configured. ## Need help now? If the connector you need isn't currently available and it's blocking an active project, contact AIWA Support. Include: * The service * The project you're building * The workflow you're trying to implement * The required actions * A link to the service's API documentation if available We can then help determine whether: * An existing connector can solve the requirement, * A custom API integration may be possible, or * A new native connector is needed. ## Next: Publishing to a Live URL Publish your AIWA project to a live URL customers can visit. # Resend Source: https://docs.aiwa.codes/integrations/resend Connect Resend to send transactional email from your AIWA app: welcome, booking, order, invitation, and status notifications. Resend lets applications you build with AIWA send transactional emails. You can use Resend for: * Welcome emails * Email confirmations * Booking confirmations * Order receipts * Contact-form notifications * Team invitations * Account notifications * Status updates * Application-triggered emails Once Resend is connected, tell AIWA when an email should be sent, who should receive it, and what it should contain. **Connect Resend. Describe the event. AIWA builds the email workflow.** ## What is transactional email? Transactional emails are messages triggered by something happening inside your application. For example: ```text theme={null} Customer books appointment ↓ Booking saved ↓ Confirmation email sent ``` Or: ```text theme={null} User creates account ↓ Account created ↓ Welcome email sent ``` Or: ```text theme={null} New lead submits form ↓ Lead saved ↓ Sales team notified ``` Unlike a newsletter or promotional campaign, these emails are typically triggered by a specific application event. ## What you can build with Resend **Welcome emails** > Send new users a welcome email after they successfully create an account. **Booking confirmations** > Send customers a confirmation email containing their service, appointment date, time, and booking reference. **Internal notifications** > Email our sales team whenever a new demo request is submitted. **Team invitations** > When an administrator invites a team member, send the invited user an email containing the invitation. **Order confirmations** > After payment is successfully confirmed, email the customer their order details. **Status notifications** > Notify customers when their project status changes to Ready for Review. These emails can become part of the workflows AIWA builds for your application. ## Before You Start You'll need a Resend account and the credentials required to use Resend's email service. Depending on how you intend to send email, you may also need to configure and verify a sending domain with Resend. Your sending domain and email configuration are managed through Resend. AIWA uses your Resend connection to build email functionality into your application. ## Connect Resend to AIWA Open your AIWA project and navigate to Connectors. Find Resend and select it. AIWA Resend Follow the connection flow and provide the details requested by AIWA: | Field | What to enter | | - | - | | **API key** | Your Resend API key, starting with `re_` | | **Sender address** | The address every email from your app is sent from, such as `hello@yourdomain.com`. It must be on a domain you've verified in Resend | | **Notify address** (optional) | Where form submissions and owner notifications go, such as `you@yourbusiness.com` | AIWA Resend Config Every email your app sends goes from the sender address you set here. On a simple website, contact and enquiry form submissions are sent to your notify address. Once connected, you can begin asking AIWA to build email functionality into your project. Your Resend API key is sensitive. Add it through AIWA's supported connector experience rather than placing it directly into your application's frontend code. ## Your First Email Workflow Let's say you're building a booking application. You could tell AIWA: > When a customer successfully creates a booking, send them a confirmation email containing their name, service, appointment date, appointment time, and booking reference. The workflow might look like: ```text theme={null} Customer books ↓ Validate booking ↓ Save to Neon ↓ Booking confirmed ↓ Send through Resend ↓ Customer receives email ``` Notice that the email is connected to a successful application event. ## Define when the email should send Be specific about the trigger. Instead of: > Send a booking email. Try: > Send the customer a confirmation email only after the booking has been successfully saved. Or: > Notify the sales team when a new lead is successfully created from the Request a Demo form. The trigger tells AIWA when the email workflow should run. ## Define who receives it Tell AIWA who should receive the message. For example: > Send the confirmation to the email address provided by the customer during booking. Or: > Send new lead notifications to [sales@mycompany.com](mailto:sales@mycompany.com). Or: > Send the invitation to the email address entered by the workspace administrator. Some workflows may have multiple recipients. For example: > After a booking is confirmed, send the customer a confirmation and notify the assigned staff member about the new appointment. ## Define What the Email Contains AIWA can use application data to personalize emails. Suppose your database contains: ```text theme={null} Customer Sarah Chen Service Strategy Consultation Date September 15 Time 2:00 PM Booking Reference BK-10482 ``` Your email can use that information. For example: ```text theme={null} Hi Sarah, Your Strategy Consultation has been confirmed. Date: September 15 Time: 2:00 PM Booking: BK-10482 ``` You don't have to hard-code every customer's information. The application can use the data associated with the event. ## Use dynamic information You can tell AIWA: > Personalize the booking confirmation using the customer's first name and include the booking's service, date, time, and reference number. Or: > Include the project name, current status, and account manager in the project-update email. This allows one email workflow to work across many users and records. ## Customer and Internal Emails One event can trigger different emails for different audiences. Imagine a consultation request. **Customer** Receives: > Thanks, Sarah. We've received your consultation request and will be in touch shortly. **Sales team** Receives: > New consultation request from Sarah Chen at Acme Ltd. The workflow becomes: ```text theme={null} Form Submitted ↓ Save Lead ↓ ┌──┴──┐ ↓ ↓ Customer Sales Team Email Notification ``` You can describe both behaviors in the same request. ## Example: Contact Form Suppose your website has: ```text theme={null} Name Email Company Phone Message [Send Message] ``` You could tell AIWA: > When the contact form is successfully submitted, save the enquiry to the database, send the customer a confirmation email, and notify our sales team with the enquiry details. This combines: **Form → Database → Resend** rather than treating the form as an isolated component. ## Example: Welcome Email For a SaaS product: > After a new user successfully creates their account, send a welcome email using their first name. Include a button that takes them back to their dashboard. Conceptually: ```text theme={null} Account Created ↓ User Saved ↓ Send Welcome Email ↓ Dashboard CTA ``` ## Example: Team Invitation Suppose your application allows workspace Owners to invite team members. You might ask: > When an Owner invites a team member, create a pending invitation and email the invited user. Include the workspace name, who invited them, and a button to accept the invitation. This connects Resend with your application's authentication and team system. ## Example: Payment Confirmation Resend can also work alongside Stripe. For example: ```text theme={null} Stripe Payment ↓ Payment Confirmed ↓ Purchase Recorded ↓ Resend ↓ Receipt / Confirmation ``` You could tell AIWA: > After Stripe confirms the \$99 course purchase, record the purchase, grant access, and send the customer a purchase confirmation email. For payment-related emails, trigger the message from the confirmed payment workflow rather than simply when the customer reaches a success page. ## Example: Status Updates Emails can also be triggered by changes to your application data. For example: > When a project changes from In Progress to Ready for Review, email the customer and include a link to the project portal. Or: > When an order changes to Shipped, email the customer with their tracking information. Or: > When a support ticket receives a staff response, notify the customer by email. This turns application activity into communication. ## Sending Domain For production email, you'll generally want messages to come from your own domain. For example: * [hello@yourcompany.com](mailto:hello@yourcompany.com) * [support@yourcompany.com](mailto:support@yourcompany.com) * [notifications@yourcompany.com](mailto:notifications@yourcompany.com) Your sending-domain configuration is handled through Resend. Depending on the configuration, Resend may ask you to add DNS records to verify that you're authorized to send email for that domain. Follow Resend's domain verification process before relying on the address for production email. ## Use an appropriate From address Choose a sender that makes sense for the type of email. For example: ```text theme={null} Acme ``` or: ```text theme={null} Acme Support ``` or: ```text theme={null} Acme Notifications ``` Your app always sends from the **Sender address** set on the Resend connector. To use a different sender, change it on the connector page. ## Reply-To Sometimes the sending address and reply destination should be different. For example, notifications may be sent from: ```text theme={null} notifications@acme.com ``` but you want customer replies to go to: ```text theme={null} support@acme.com ``` Where appropriate, configure the email workflow so replies reach the right destination. ## Email Design Transactional emails don't have to be plain text. You can ask AIWA to create branded email experiences. For example: > Create a clean booking confirmation email using our brand name and styling. Include the booking details in a simple summary card and a button to manage the booking. Keep transactional emails focused. The user should immediately understand: * Why did I receive this? * What happened? * Is there anything I need to do? ## Build for Failure Email delivery can fail even when the main application action succeeds. Imagine: ```text theme={null} Booking Created ✓ Email Failed ✕ ``` Should the customer's booking disappear because the confirmation email failed? Usually, no. The booking and the notification are different operations. For example, you could specify: > If the booking is created successfully but the confirmation email fails, keep the booking and log the email failure. Don't tell the customer their booking failed. This distinction becomes important for reliable application workflows. ## Don't create duplicate emails Some actions can accidentally be triggered more than once. For important transactional workflows, make sure repeated requests don't create unnecessary duplicate messages. For example: > Don't send another welcome email every time an existing user signs in. The trigger should be: **Account created** not: **User authenticated** Likewise, payment confirmations should correspond to the appropriate confirmed transaction rather than every page load. ## Common Problems ### Emails aren't sending First determine whether the main application action works. For example: > Bookings are being saved successfully, but confirmation emails aren't being sent. This is much more useful than: > Booking doesn't work. Use Debug Mode and isolate the email portion of the workflow. ### Domain isn't verified If you're attempting to send from your own domain, check the domain status in your Resend account. Make sure the required DNS configuration has been added correctly. ### Wrong sender address Make sure the From address you're trying to use is permitted by your Resend configuration. ### Email sends but contains incorrect information This may be an application-data issue rather than a Resend connection problem. Tell AIWA: > Booking confirmation emails are sending successfully, but the appointment time shown in the email is incorrect. The dashboard shows the correct time. Debug how the booking time is being passed into the email template. ### Customers receive duplicate emails Tell AIWA: > Some customers are receiving two booking confirmation emails for one booking. Investigate the email trigger and ensure each confirmed booking sends only one confirmation. ## Debugging Resend Use Debug Mode when your email workflow isn't behaving correctly. For example: > Expected: After a booking is created, the customer should receive a confirmation email. > > Actual: The booking is saved correctly, but no email arrives. > > The booking functionality itself is working. > > Debug the Resend email workflow and identify why the confirmation isn't being sent. Preserve the existing booking functionality. This tells AIWA exactly where to focus. ## Keep Your API Key Secure Your Resend API key provides access to your Resend account's email functionality. Never expose your Resend API key in frontend code, public GitHub repositories, screenshots, documentation, or public support conversations. If you believe the key has been exposed, revoke or rotate it through Resend and update your AIWA connection. ## A Good Email Workflow Prompt A strong request usually defines: **Trigger** When should the email send? **Recipient** Who receives it? **Content** What information should it contain? **Action** Should the recipient be able to click somewhere? **Failure behavior** What happens if sending fails? For example: > After a customer successfully books an appointment, send a confirmation email to the customer's booking email address. Personalize it with their first name and include the service, staff member, date, time, and booking reference. Include a button linking to their booking. If email delivery fails, don't cancel the booking. That's significantly more useful than: > Send an email. ## Test Before Publishing Before launching an email workflow, test it. Check: * Is the email triggered at the correct time? * Does it go to the correct recipient? * Is the From address correct? * Is personalization correct? * Are dates and times correct? * Do links work? * Does it look acceptable on mobile? * What happens if sending fails? * Is the same email accidentally sent twice? For important workflows, test several scenarios rather than only the ideal path. ## Think in Events The easiest way to design email functionality is to think: **When X happens, send Y to Z.** For example: * When a user registers, send a welcome email to the user. * When a booking is confirmed, send booking details to the customer. * When a demo request arrives, send a lead notification to the sales team. * When an invoice becomes overdue, send a reminder to the customer. You define the event and outcome. AIWA builds the workflow around Resend. ## Next: Twilio Resend sends your app's email from your own domain. Email isn't always the best communication channel. Next, we'll look at Twilio, which can enable communication workflows such as SMS inside applications you build with AIWA. Connect Twilio to send SMS and other communications from your app. # Stripe Source: https://docs.aiwa.codes/integrations/stripe Connect Stripe to accept one-time payments, subscriptions, upgrades, and downgrades, and gate features by real subscription state. Stripe lets you accept payments and manage billing inside applications you build with AIWA. You can use Stripe to build: * One-time payments * Recurring subscriptions * SaaS pricing plans * Checkout experiences * Upgrades and downgrades * Customer billing management * Payment-driven access to features Once Stripe is connected, you can describe the payment experience you want and let AIWA build the application logic around it. **Connect Stripe. Describe your billing model. Let AIWA build the payment experience.** ## What you can build with Stripe Stripe can power many different types of payment workflows. **One-time purchases** For example: > Sell this course for \$99. Customers should receive access to the course after successful payment. **Subscriptions** For example: > Create Starter, Pro, and Business plans at \$0, \$29, and \$99 per month. AIWA Pricing **Paid bookings** For example: > Customers must pay a \$50 consultation fee before their appointment is confirmed. **Feature access** For example: > The Analytics feature should only be available to customers with an active Pro or Business subscription. **Billing management** For example: > Add a Billing page where customers can see their current plan and manage their subscription. AIWA can build these experiences around your Stripe connection. ## Before You Start You'll need a Stripe account before connecting Stripe to your application. You'll also need the appropriate Stripe credentials for the environment you're using. Stripe provides separate environments for testing and live payments. We recommend building and testing your payment workflow using Stripe's test environment before accepting real payments. ## Connect Stripe to AIWA Open your AIWA project and navigate to the Connectors area. Find Stripe and select it. AIWA Stripe Follow the connection flow and provide the Stripe credentials requested by AIWA. AIWA Stripe Config Once the connection is configured, Stripe becomes available for the application you're building. Treat your Stripe secret credentials as sensitive information. Add them through AIWA's supported connector experience rather than placing them directly into frontend code. ## Test Mode vs Live Mode Stripe provides separate environments for development and production. **Test Mode** Use this while building. Transactions don't charge real cards, allowing you to test: * Successful payments * Failed payments * Checkout * Subscriptions * Billing flows * Webhooks * Application behavior after payment **Live Mode** Use this when you're ready to accept real customer payments. A recommended workflow is: ```text theme={null} Stripe Test Mode ↓ Connect to AIWA ↓ Build payment workflow ↓ Test complete flow ↓ Fix any issues ↓ Configure Live Mode ↓ Test configuration ↓ Publish ``` Don't use real customer payments as your first test of a new billing system. ## Build Your First Payment Flow Once Stripe is connected, tell AIWA what you want customers to purchase. For example: > Add a one-time payment of \$29 for the Complete Marketing Course. Customers should click Buy Now, complete payment through Stripe, and receive access to the course dashboard after successful payment. AIWA Stripe Checkout AIWA can build the workflow around that requirement. Conceptually: ```text theme={null} Customer ↓ Buy Now ↓ Stripe Checkout ↓ Payment ↓ Verify Payment ↓ Record Purchase ↓ Grant Access ↓ Course Dashboard ``` The important part isn't simply getting the customer to Stripe. Your application also needs to know what should happen after payment. ## Building Subscriptions Stripe is especially useful for SaaS applications with recurring billing. Suppose you have: ```text theme={null} Starter $19/month Pro $49/month Business $99/month ``` You could tell AIWA: > Add monthly subscriptions for Starter at \$19, Pro at \$49, and Business at \$99. Users should select their plan from the pricing page and complete payment through Stripe. After successful payment, update their account with the correct subscription. Now you're defining both the payment and the application behavior. ## Define what each plan includes Pricing isn't the only thing AIWA needs to understand. Tell AIWA what each subscription unlocks. For example: > Starter users can create up to 3 projects. Pro users can create up to 20 projects and access analytics. Business users have unlimited projects, analytics, and team collaboration. Your application can then use the customer's subscription to determine which functionality is available. Conceptually: ```text theme={null} Stripe Subscription ↓ Application ↓ Current Plan ↓ Feature Permissions ``` ## Payment Success Don't define payment behavior only around checkout. Tell AIWA what should happen after Stripe confirms a successful payment. For example: > After successful payment, record the purchase, update the customer's subscription, unlock Pro features, and redirect them to the dashboard. This creates a complete payment workflow. ## Payment Failure Payments can fail. Your application should handle that properly. For example: > If payment fails, don't activate the subscription. Show the customer that payment was unsuccessful and allow them to try again. Conceptually: ```text theme={null} Payment Attempt ↓ Successful? ↙ ↘ Yes No ↓ ↓ Activate Keep Current Plan Access ↓ ↓ Dashboard Retry ``` ## Don't Trust the Success Page Alone A customer reaching: ```text theme={null} /payment-success ``` doesn't necessarily prove that payment was successfully completed. Important payment events should be verified through the appropriate server-side Stripe workflow. Don't grant paid access simply because someone reaches your application's payment-success URL. Your application should use confirmed payment information before activating paid functionality. ## Stripe Webhooks Stripe can notify your application when important billing events happen. These notifications are commonly called webhooks. For example: ```text theme={null} Customer ↓ Stripe Checkout ↓ Payment succeeds ↓ Stripe sends event ↓ AIWA application ↓ Subscription updated ``` Webhooks are especially important for subscriptions because billing events can happen even when the customer isn't currently using your application. ## Subscription events happen later Imagine someone subscribes today. Thirty days later, Stripe attempts to renew their subscription. The customer may not even have your application open. Your application still needs to know whether: * Renewal succeeded * Renewal failed * Subscription changed * Subscription was cancelled Stripe can send these events to your application. Your application can then update its own subscription state accordingly. ## Keep Stripe and Your Database in Sync Your application may store information such as: ```text theme={null} User Plan: Pro Subscription Status: Active Stripe Customer ID: ... Stripe Subscription ID: ... ``` Stripe remains responsible for payment processing. Your application uses relevant billing information to determine what experience the customer should receive. Conceptually: ```text theme={null} STRIPE Payment & Subscription State ↓ SERVER-SIDE LOGIC ↓ NEON POSTGRES Application Subscription State ↓ YOUR PRODUCT Features & Access ``` Keeping these systems synchronized is an important part of building reliable subscription software. ## Upgrades Suppose a Starter customer wants to move to Pro. You could tell AIWA: > Allow Starter customers to upgrade to Pro from the Billing page. After Stripe confirms the subscription change, update their account and unlock Pro functionality. Your application should reflect the updated plan once the billing change succeeds. ## Downgrades Downgrades may require more product decisions. Imagine: * Starter: 3 projects * Pro: 20 projects A Pro customer currently has 12 projects and downgrades to Starter. What happens? You need to decide. For example: > If a user downgrades below their current project usage, don't delete existing projects. Prevent them from creating additional projects until they're within their new plan limit. That's a product rule. Stripe manages the billing change. AIWA builds your application's behavior around it. ## Cancellations You should also decide what cancellation means. For example: > When customers cancel, keep their Pro access until the end of their current billing period. After the subscription expires, move them to the Starter plan. Or: > This product has no free plan. After the paid billing period ends, keep the account but restrict access until the customer subscribes again. There isn't one correct cancellation model. Tell AIWA how your product should behave. ## Customer Billing Management For subscription products, customers often need somewhere to manage billing. You can ask AIWA: > Add a Billing section to Account Settings. Show the customer's current plan and subscription status and provide an option to manage their subscription. Depending on your Stripe implementation, customers can use Stripe's billing management functionality for actions such as managing their subscription or payment details. ## Paid Feature Restrictions Your application should enforce paid functionality based on actual subscription state. For example: ```text theme={null} Analytics ↓ Active Pro or Business? ↙ ↘ Yes No ↓ ↓ Show Upgrade Analytics Prompt ``` You might tell AIWA: > Analytics should only be available to Pro and Business customers. Starter users should see an upgrade page instead. Important paid-access rules should be enforced appropriately rather than relying only on hiding navigation links. ## Example: SaaS Subscription Here's a more complete prompt: > Add Stripe subscriptions to this SaaS application. > > Create three monthly plans: > > Starter: \$19/month: 3 projects > > Pro: \$49/month: 20 projects + analytics > > Business: \$99/month: unlimited projects + analytics + team collaboration > > Users should select a plan from the pricing page and complete checkout through Stripe. > > After Stripe confirms payment, update the user's subscription and unlock the appropriate features. > > Add a Billing page showing their current plan and subscription status. > > Customers should be able to manage their subscription. > > If a subscription expires, restrict features based on their new account state. For something this important, I'd recommend: **Plan + Max → Review → Build** rather than immediately asking AIWA to implement everything. ## Example: Paid Booking Stripe isn't only for SaaS. Suppose you're building a consultation platform. > Customers should choose an available appointment, enter their information, and pay a \$100 consultation fee through Stripe. Only create a confirmed booking after payment succeeds. Send the customer a confirmation email afterward. Conceptually: ```text theme={null} Choose Appointment ↓ Customer Details ↓ Stripe Payment ↓ Payment Confirmed ↓ Confirm Booking ↓ Save to Neon ↓ Send Confirmation ``` This combines Stripe with your database and email integration. ## Example: One-Time Digital Product You could also build: > Sell this report for \$49. Customers should pay through Stripe and receive access to the report inside their account after payment is verified. Your application can record the purchase so the customer doesn't need to pay again every time they return. ## Test Your Payment Workflow Before accepting real payments, test the entire customer journey. Don't only test whether Stripe Checkout opens. Test: **Checkout** Can the customer reach Stripe? **Successful payment** Does the application recognize the payment? **Application state** Does the user's plan or purchase update? **Feature access** Are the correct features unlocked? **Refresh** Does the correct access remain after refreshing or signing in again? **Failure** What happens when payment fails? **Cancellation** Does your application respond correctly? **Renewal** For subscriptions, does the application process billing events correctly? **Permissions** Can users access features they haven't paid for? Payment testing should cover the complete workflow, not only the payment screen. ## Common Problems ### Checkout doesn't open Check whether Stripe is connected correctly and whether the application is successfully creating the checkout session. Use Debug Mode and provide any error message you receive. ### Payment succeeds but plan doesn't update This usually means the payment itself and your application's subscription state need to be investigated separately. Tell AIWA: > Stripe payment succeeds, but the user's plan remains Starter afterward. Debug the payment confirmation and subscription update flow. Don't change the checkout interface. ### Plan updates only after refreshing Tell AIWA: > Stripe successfully updates the subscription, but the dashboard continues showing the previous plan until the page is refreshed. Fix the application state so the updated subscription appears after payment. ### Users can access paid features without paying This is more serious. Tell AIWA: > Users without an active Pro subscription can access the Analytics feature directly. Audit the Pro feature authorization and ensure paid access is enforced appropriately on the server side. ### Test payments work but live payments don't Check that you've moved from the correct Stripe test configuration to the appropriate live configuration. Test and live credentials are different. Also verify that any production webhook configuration required by your application is correctly configured. ## Debugging Stripe If something isn't working, use Debug Mode. A strong debugging request looks like: > Stripe checkout completes successfully. > > Expected: The user should be upgraded to Pro immediately after payment. > > Actual: Payment succeeds, but the user's account remains on Starter. > > The Stripe transaction appears successful. > > Debug the complete payment confirmation and subscription update flow. Identify the root cause and fix it without changing the existing pricing or checkout UI. Give AIWA: * What should happen * What actually happens * Any error you're seeing * Which part already works This helps AIWA narrow down the issue. ## Keep Your Stripe Credentials Secure Stripe secret credentials should never be intentionally exposed in your application's frontend. Never publish your Stripe secret key in frontend code, public repositories, screenshots, documentation, or support messages. If you believe a live Stripe credential has been exposed, rotate or revoke it through Stripe and update your application's configuration. ## Think Beyond the Payment Button Adding Stripe isn't simply: > Put a payment button here. Think about the complete lifecycle: ```text theme={null} PLAN ↓ CHECKOUT ↓ PAYMENT ↓ VERIFICATION ↓ SUBSCRIPTION / PURCHASE ↓ FEATURE ACCESS ↓ RENEWAL ↓ UPGRADE / DOWNGRADE ↓ CANCELLATION ``` For simple one-time purchases, the workflow may be much smaller. For subscription SaaS products, billing becomes part of your product architecture. AIWA can help build that architecture when you clearly describe how your business model should work. ## Next: PayPal Some customers prefer to pay with PayPal. Next, we'll connect PayPal so your application can accept PayPal payments alongside, or instead of, Stripe. We'll cover workflows such as: * A PayPal button at checkout * One-time payments * Pay Later and card payments * Monthly subscriptions * Testing with sandbox accounts * Going live Connect PayPal and accept PayPal payments and subscriptions in your AIWA app. # Twilio Source: https://docs.aiwa.codes/integrations/twilio Connect Twilio to send SMS confirmations, reminders, and alerts triggered by real events inside the apps you build with AIWA. Twilio lets applications you build with AIWA communicate with users through channels such as SMS. You can use Twilio to build communication workflows for: * Appointment reminders * Booking confirmations * Order updates * Lead notifications * Verification messages * Customer alerts * Status updates * Internal team notifications Once Twilio is connected, describe who should receive a message, when it should be sent, and what it should say. **Connect Twilio. Define the event. AIWA builds the communication workflow.** ## What You Can Build with Twilio Twilio can add real-time communication to many types of applications. **Appointment reminders** > Send customers an SMS reminder 24 hours before their appointment. **Booking confirmations** > Send the customer a confirmation SMS after their booking is successfully created. **Order updates** > Notify customers by SMS when their order has been shipped. **Lead notifications** > Send the assigned sales representative an SMS when a high-value lead enters the CRM. **Account alerts** > Notify users when an important action occurs on their account. Twilio becomes the communication service behind the workflow you define. ## Before You Start You'll need a Twilio account and the credentials required by the AIWA Twilio connector. Depending on the functionality you're building, you may also need a Twilio phone number or other Twilio configuration. Twilio services, phone numbers, message availability, pricing, and regulatory requirements can vary by country and destination. Check your Twilio account for the requirements that apply to your use case. ## Connect Twilio to AIWA Open your AIWA project and navigate to Connectors. Find Twilio and select it. AIWA Twillio Enter the credentials requested by AIWA and save the connection. AIWA Twillio Config Once connected, you can begin asking AIWA to add Twilio-powered functionality to your application. Keep your Twilio authentication credentials private. Configure them through AIWA's connector experience rather than exposing them in frontend code. ## Build Your First SMS Workflow Suppose you're building a booking application. You could tell AIWA: > After a booking is successfully confirmed, send the customer an SMS containing the service, appointment date, time, and booking reference. Conceptually: ```text theme={null} Booking Confirmed ↓ Save to Neon ↓ Server-Side Logic ↓ Twilio ↓ Customer receives SMS ``` The message is triggered by something happening inside your application. ## Define the Trigger Be clear about when the message should be sent. Instead of: > Send customers an SMS. Try: > Send the customer an SMS immediately after their appointment is successfully confirmed. Or: > Send the assigned sales agent an SMS when a new lead with an estimated value above \$10,000 is created. The event is what activates the workflow. ## Define the Recipient Tell AIWA where the recipient's phone number comes from. For example: > Send the SMS to the phone number the customer provided during booking. Or: > Send the notification to the assigned agent's saved phone number. For applications that collect phone numbers, make sure the appropriate field exists and is validated. ## Define the Message SMS works best when messages are concise. For example: ```text theme={null} Your consultation with Acme has been confirmed for Sept 15 at 2:00 PM. Ref: BK-10482. ``` You can use dynamic application data inside the message. For example: > Personalize the SMS with the customer's first name and include their appointment date, time, and booking reference. ## Phone Numbers Phone-number formatting matters when sending messages internationally. A phone number should generally be stored in a format that clearly identifies its country. For example: ```text theme={null} +14155550123 ``` rather than relying only on: ```text theme={null} 4155550123 ``` If your application serves users in multiple countries, consider collecting the user's country alongside their phone number or using a phone input that handles international dialing codes. ## Validate Phone Numbers Don't wait until Twilio attempts delivery to discover that required phone information is missing. For example: > Make phone number required for SMS appointment reminders and validate the number before saving the booking. You should also decide what happens if a customer doesn't provide a valid number. ## Example: Appointment Reminders One of the most useful Twilio workflows is automated reminders. Suppose your application stores: ```text theme={null} Customer Sarah Chen Service Strategy Consultation Appointment September 15, 2:00 PM Phone +1... ``` You could ask AIWA: > Send customers an SMS reminder 24 hours before their confirmed appointment. Include the service, appointment date, and time. Conceptually: ```text theme={null} Confirmed Appointment ↓ Wait until reminder time ↓ Still confirmed? ↓ Twilio ↓ SMS Reminder ``` Notice the additional condition: **Still confirmed?** You don't want to remind someone about an appointment that has already been cancelled. ## Example: Booking Confirmation You can combine email and SMS. For example: > After a booking is successfully confirmed, send the customer a detailed confirmation email through Resend and a short confirmation SMS through Twilio. The workflow becomes: ```text theme={null} Booking Confirmed ↓ Save Booking ↓ ┌───┴────┐ ↓ ↓ Resend Twilio ↓ ↓ Email SMS ``` Multiple connectors can participate in the same product workflow. ## Example: High-Value Lead Alert Twilio can also be useful for internal notifications. Suppose your sales team wants immediate alerts for valuable opportunities. > When a new lead is created with an estimated budget of \$10,000 or more, mark the lead as High Priority and send the assigned sales representative an SMS containing the lead's name, company, and estimated budget. Conceptually: ```text theme={null} New Lead ↓ Check Budget ↓ $10,000+? ↙ ↘ Yes No ↓ ↓ High Normal Priority ↓ Twilio ↓ Sales Alert ``` This combines database logic with external communication. ## Example: Order Updates For an e-commerce application: > When an order status changes to Shipped, send the customer an SMS containing their order number and tracking information. The trigger isn't the customer clicking a button. It's a change in application data. This allows communication to follow the lifecycle of a record. ## SMS Consent Before sending automated or marketing-related messages, make sure your application collects any consent required for your use case and the countries where you operate. For example, your form may include an appropriate consent option for receiving SMS notifications. Connecting Twilio doesn't remove your responsibility to follow applicable messaging, consent, opt-out, and telecommunications requirements. For high-volume or promotional messaging, review Twilio's requirements and applicable regulations before launching. ## Transactional vs Marketing Messages There's an important difference between: > Your appointment is confirmed for tomorrow at 2 PM. and: > Get 30% off when you book another appointment today! The first is related to an existing customer transaction. The second is promotional. Different requirements may apply depending on your location, recipient location, and type of message. Design your messaging workflow accordingly. ## Don't Send Messages from the Frontend Twilio authentication credentials shouldn't be exposed in browser code. The safer conceptual architecture is: ```text theme={null} USER ACTION ↓ YOUR APPLICATION ↓ SERVER-SIDE LOGIC ↓ TWILIO ↓ SMS ``` rather than having the user's browser directly contain sensitive Twilio credentials. AIWA can build the appropriate server-side workflow around your connector. ## Handle Delivery Failures An SMS may fail to send even though the primary application action succeeds. For example: ```text theme={null} Booking Created ✓ SMS Failed ✕ ``` That doesn't necessarily mean the booking itself should be cancelled. You can define the behavior: > If the booking is created successfully but the confirmation SMS fails, keep the booking confirmed. Record the messaging failure without cancelling the appointment. This separates the core application action from the notification. ## Avoid Duplicate Messages Make sure the same application event doesn't unnecessarily trigger multiple messages. For example: > Send one confirmation SMS when the booking is first confirmed. Don't send another confirmation simply because the customer views or refreshes the booking page. Your message should be tied to the correct event. ## Common Problems ### SMS isn't sending First determine whether the rest of the workflow works. For example: > The booking is being created successfully, but the customer isn't receiving the SMS. Then use Debug Mode to investigate the Twilio portion. ### Invalid phone number Check that the phone number is present and formatted appropriately for the destination. For international applications, pay particular attention to country codes. ### Twilio rejects the request The error returned by Twilio can provide useful information. Copy the error message into Debug Mode without including sensitive credentials. ### Some countries receive messages and others don't Messaging availability and requirements can differ by destination. Check whether your Twilio account, sender, number, and messaging configuration support the affected destination. ### Customers receive duplicate messages Tell AIWA: > Customers sometimes receive two confirmation SMS messages for one booking. Investigate the trigger and ensure a confirmed booking produces only one confirmation SMS. ## Debugging Twilio A useful debugging request looks like: > Expected: After a booking is confirmed, the customer should receive an SMS. > > Actual: The booking is created correctly, but no SMS is received. > > The customer's phone number is saved on the booking. > > Error: \[PASTE ERROR IF AVAILABLE] > > Debug the Twilio portion of the workflow without changing the existing booking functionality. This gives AIWA a specific area to investigate. ## Test Your Workflow Before publishing, test more than whether one SMS arrives. Check: * Is the message triggered at the correct time? * Does it go to the correct number? * Is dynamic information correct? * Are dates and times correct? * What happens with an invalid number? * What happens if Twilio rejects the request? * Are duplicate messages prevented? * Are cancelled bookings excluded from reminders? * Does the core action still succeed if the notification fails? For applications operating internationally, test the destinations you actually intend to support. ## A Good Twilio Prompt A strong communication request defines: * **Trigger:** When? * **Recipient:** Who? * **Message:** What? * **Conditions:** Under what circumstances? * **Failure behavior:** What happens if delivery fails? For example: > Send customers an SMS reminder 24 hours before confirmed appointments. Send it to the phone number associated with the booking and include the customer's first name, service, date, and time. Don't send reminders for cancelled appointments. If SMS delivery fails, don't modify or cancel the booking. That's much stronger than: > Add SMS reminders. ## Think in Communication Events A useful pattern is: **When X happens → send Y → to Z.** For example: * Booking confirmed → Confirmation SMS → Customer * Appointment approaching → Reminder SMS → Customer * High-value lead created → Lead alert → Sales representative * Order shipped → Tracking notification → Customer You define the communication event. AIWA builds the workflow around Twilio. ## Next: Cloudinary Messages aren't the only external assets your application needs. Applications often need to handle: * Images * Profile photos * Property galleries * Product images * Uploaded media Next, we'll look at Cloudinary and how you can use it with AIWA to build media upload and delivery experiences. Connect Cloudinary to store, transform, and deliver uploaded media. # xAI (Grok) Source: https://docs.aiwa.codes/integrations/xai-grok Connect xAI to power AI assistants, generation, extraction, and analysis features with Grok inside apps you build with AIWA. The xAI connector lets applications you build with AIWA use Grok models for AI-powered features. You can use Grok inside your application for experiences such as: * AI assistants * Content generation * Summarization * Classification * Data extraction * Customer support * Research-style workflows * Structured analysis * AI-powered automations Once xAI is connected, tell AIWA what you want Grok to do inside your product. **Connect xAI. Define the AI experience. AIWA builds the workflow around Grok.** ## AIWA vs Grok AIWA is the platform you use to build and evolve your application. Grok can then power individual AI features inside that application. For example: > Build a social media intelligence dashboard with saved topics, monitored accounts, alerts, and reporting. AIWA builds the product. Then: > Add an AI Insight feature using Grok that summarizes the most important developments around a monitored topic. Grok powers the AI step inside the experience. ## Before You Start You'll need access to xAI's API and the credentials required by AIWA's xAI connector. API usage may incur charges according to your xAI account, selected model, and request volume. Available models, pricing, capabilities, and rate limits are controlled by xAI and may change over time. ## Connect xAI to AIWA Open your AIWA project and navigate to Connectors. Find xAI / Grok and select it. AIWA Grok Follow the setup flow and provide the information requested by AIWA. AIWA Grok Config Once connected, Grok becomes available for AI-powered functionality inside your application. Keep your xAI API key private. Configure it through AIWA's connector experience rather than exposing it in frontend code, screenshots, or public repositories. ## Build Your First Grok Feature Suppose you're building a market intelligence application. You could tell AIWA: > Add an AI Insight Generator using Grok. Users should enter a topic and supporting notes. Generate a concise summary, key developments, risks, opportunities, and three recommended next actions. The workflow might look like: ```text theme={null} Topic + Context ↓ Generate ↓ Server-Side Logic ↓ Grok ↓ Structured Result ↓ Application ``` The user interacts with your application. Grok operates behind the feature. ## Define the Input Tell AIWA what context Grok should receive. For example: > Use the user's topic, notes, selected industry, and desired analysis goal. Or: > Use the support ticket and recent conversation history. Or: > Use the lead enquiry, budget, status, and activity history. Only send information that is relevant to the task. ## Define the Output Be clear about what the feature should return. For example: > Return a short executive summary, three risks, three opportunities, and recommended next actions. Or: > Return category, urgency, sentiment, and recommended response. Or: > Extract company name, requirement, budget, timeline, and decision stage. Structured expectations make it easier for AIWA to build a useful interface around Grok's response. ## Example: AI Research Assistant Suppose you're building a research workspace. You could ask AIWA: > Add a Research Assistant using Grok. Users should provide a research question and notes. Return a concise analysis, major themes, open questions, and recommended areas to investigate next. You could then extend it: > Allow users to save the generated analysis to the research project and regenerate it later. That turns a one-time model call into a product workflow. ## Example: Lead Analysis For a CRM: > When a new lead is created, use Grok to analyze their enquiry and generate a short qualification summary containing their likely need, urgency, budget confidence, and recommended sales action. Save the result to the lead record. Conceptually: ```text theme={null} Lead Enquiry ↓ Grok Analysis ↓ Structured Insight ↓ Neon ↓ CRM ``` This makes the AI output part of the application's stored data. ## Example: Support Assistant For a support tool: > Add a Suggested Reply button using Grok. Use the current support ticket and recent customer messages to draft a response. Show the result in the reply editor and require an agent to review it before sending. This keeps a human in control of customer communication. ## Example: Content Generation Suppose you're building a marketing application. You could ask: > Add a Grok-powered content generator. Users should provide their offer, audience, platform, tone, and campaign goal. Generate five content ideas and let users expand any one into a full post. The experience might be: ```text theme={null} Campaign Context ↓ Grok ↓ 5 Ideas ↓ User Selects One ↓ Generate Full Post ↓ Edit / Save ``` Again, Grok is one part of the complete product experience. ## Human Review For higher-impact actions, consider requiring human approval. For example: > Use Grok to generate a proposed sales response, but don't send it automatically. Show it to the sales representative for editing and approval first. Conceptually: ```text theme={null} Grok Generates ↓ Human Reviews ↓ Human Approves ↓ Action Happens ``` This can be especially useful when AI output affects: * Customer communication * Financial decisions * Important business recommendations * Sensitive content * Irreversible actions ## Saving AI Responses Decide whether Grok output should be temporary or saved. For example: > Save approved AI summaries to the lead record. Or: > Don't save generated drafts until the user clicks Save. Or: > Display the existing saved summary by default and only call Grok again when the user clicks Regenerate. This affects user experience and API usage. ## Avoid Unnecessary Requests Don't call Grok every time a page loads if the result doesn't need to change. For example: > Store the generated account summary and display the saved result. Only regenerate it when the account manager requests a new summary. This can reduce latency and unnecessary API usage. ## Model Choice xAI may offer multiple Grok models with different capabilities, costs, and performance characteristics. Your choice may depend on: * Speed * Cost * Reasoning needs * Context requirements * Output size * Application volume You can specify a model when necessary, or describe the product requirement and choose an appropriate supported option. Refer to xAI's current documentation for model availability and API pricing. ## Loading and Error States AI features should clearly communicate when generation is happening. For example: > Generating insight... If the request fails: ```text theme={null} We couldn't generate the insight. [Try Again] ``` Tell AIWA: > Preserve the user's input if the Grok request fails and allow them to retry without starting over. ## Sensitive Data Be deliberate about what information your application sends to an external AI provider. Avoid sending unnecessary sensitive information. Never send passwords, API keys, authentication secrets, or other private credentials to Grok as prompt context. For applications handling private business or customer information, make sure the workflow aligns with your privacy and compliance requirements. ## Common Problems ### Grok feature doesn't respond Check whether: * The xAI connector is configured correctly * The application is making the request * xAI returns an error * The application receives the response * The result is displayed correctly Use Debug Mode with the exact behavior you observe. ### Output quality is poor This may be an instruction or context problem rather than a connector issue. For example: > The generated lead insights are too generic. Improve the Grok prompt so every result identifies the lead's need, urgency, budget confidence, objections, and recommended next action. ### Output structure is inconsistent If your application expects structured fields, make that requirement explicit. For example: > Ensure Grok always returns summary, risks, opportunities, and nextActions in a predictable structured format and validate the result before saving it. ### Responses are slow Ask AIWA to inspect: * Model selection * Context size * Output length * Number of model calls * Application workflow ### Usage is unexpectedly high Check whether the feature is calling Grok too often. For example: > Audit this feature and make sure the account summary isn't regenerated on every page load. ## Debugging xAI A strong Debug Mode prompt could be: > Expected: Clicking Generate Insight should analyze the lead and show a structured summary. > > Actual: The loading state appears, but no result is displayed. > > The lead data itself loads correctly. > > Error: \[PASTE ERROR IF AVAILABLE] > > Debug the xAI/Grok request and response flow without changing the existing lead page. Do not include the API key in the debugging prompt. ## Test Your Grok Feature Before publishing, test: * Normal inputs * Very short inputs * Long inputs * Empty input * Loading states * Failed requests * Retry behavior * Output structure * Saved results * Regeneration * Permissions * Unexpected user input * API usage behavior For higher-impact workflows, also test the human approval step. ## A Good Grok Prompt for AIWA Define: **Purpose** What should Grok accomplish? **Input** What context does it receive? **Output** What should it return? **User experience** How should the user interact with the result? **Persistence** Should the output be saved? **Permissions** Who can use the feature? For example: > Add a Grok-powered Lead Insight feature. Authorized sales users can generate an insight from the lead detail page. Use the lead's enquiry, budget, source, status, and recent activity. Return a concise summary, urgency, purchase intent, risks, and recommended next action. Show a loading state while generating, allow manual regeneration, and save approved results to the lead record. ## Choosing Between AI Providers AIWA supports multiple AI providers so you can choose based on your product requirements. Your application may use: * OpenAI * Anthropic Claude * Google Gemini * xAI Grok You don't need all of them. Choose based on factors such as: * Model capabilities * Cost * Performance * Context needs * Provider preference * Product requirements The provider should serve the product, not become the product architecture by accident. ## Next: Calendly We've completed the AI-provider connectors. Next, we'll move into scheduling with Calendly. We'll cover how to connect Calendly to AIWA and use it in applications for: * Demo bookings * Consultations * Sales calls * Customer onboarding * Appointment scheduling Connect Calendly and add scheduling to your AIWA application. # Export for Android (APK) Source: https://docs.aiwa.codes/mobile/export-android Build an Android APK from your AIWA project or download the mobile source files. Test the build before moving toward Google Play. Once your application has passed AIWA's Mobile Readiness Scan, you can turn it into an Android application. AIWA handles the build process for you. You don't need to manually configure an Android project, set up the application package, or prepare the mobile source code yourself before generating the build. Once AIWA determines that your project is mobile-ready, you can either: * Build the Android app * Download the mobile source files **Scan. Build. Download. Your AIWA project is ready to move beyond the browser.** Android export is available on the Agency plan and above. Building the APK costs 10 credits and the Google Play release kit costs 5 credits. Both unlock once your project scores 80 or more on the [Mobile Readiness Scan](/mobile/readiness-scan). ## Before You Export Your application should first complete the Mobile Readiness Scan. The workflow is: ```text theme={null} AIWA PROJECT ↓ MOBILE READINESS SCAN ↓ READY? ↙ ↘ NO YES ↓ ↓ FIX BUILD APP ISSUES OR DOWNLOAD SOURCE ``` If AIWA identifies readiness issues, resolve them before moving forward. Once your project is determined to be ready, the mobile build and source export options become the next step. ## Your Mobile App Is Ready When AIWA determines that your application is ready for mobile, you'll be able to proceed with the mobile export. AIWA Mobile Export Ready From here, you have two paths: ```text theme={null} MOBILE READY ↓ CHOOSE YOUR PATH ↙ ↘ BUILD APP SOURCE FILES ↓ ↓ APK DOWNLOAD ``` Which option you choose depends on what you want to do next. ## Option 1: Build the Android App If you want AIWA to create the Android application for you, choose the option to Build App. AIWA takes the mobile-ready project and starts the Android build process. ```text theme={null} MOBILE-READY PROJECT ↓ BUILD APP ↓ AIWA BUILDS APP ↓ ANDROID BUILD ↓ DOWNLOAD ``` You don't need to manually create the Android project before doing this. AIWA handles the build process. ## Build Your APK Start the Android build from the Mobile Export interface. AIWA Mobile App Build In Progress AIWA will begin preparing the Android version of your application. Depending on the project, the build may take some time to complete. Wait for the current build to finish before starting another one. ## When Your Android Build Is Ready Once the build completes successfully, AIWA makes the generated Android application available for download. AIWA Download Mobile App You can then download the APK and test it on an Android device. Your workflow becomes: ```text theme={null} AIWA ↓ MOBILE READINESS ↓ BUILD APP ↓ APK ↓ DOWNLOAD ↓ TEST ``` ## What Is an APK? APK stands for Android Package Kit. It's an Android application package that can be installed on compatible Android devices. Your generated APK can be used to test the mobile version of your AIWA application before moving toward public distribution. ## Install and Test Your App Generating the APK isn't the end of the process. Install the application on an Android device and test it. Don't only check whether the app opens. Test the actual workflows your users depend on. For example, if you've built a booking application: ```text theme={null} Open App ↓ Create Account ↓ Sign In ↓ Browse Services ↓ Make Booking ↓ Receive Confirmation ↓ Manage Booking ``` If all of those actions are important to the product, test all of them. ## What Should You Test? Pay particular attention to: * Authentication * Navigation * Forms * Database functionality * Buttons and touch interactions * File uploads * Images * External links * Integrations * Payments, where applicable * Important customer workflows * Mobile layouts Also close the application and reopen it to make sure the experience behaves as expected. ## Your Web and Mobile Apps Can Work Together For applications designed around the same backend and user accounts, your web and mobile experiences can be part of the same product. For example: ```text theme={null} YOUR PRODUCT ↙ ↘ WEB ANDROID ↓ ↓ USERS USERS ↘ ↙ APPLICATION ↓ DATA ``` A user could interact with the product from the web and later continue from the mobile application. The exact behavior depends on how you've designed your application. ## Option 2: Download the Source Files You don't have to use AIWA's generated mobile build as your only path. Once your project is mobile-ready, you can also download the mobile source files. ```text theme={null} MOBILE-READY PROJECT ↓ DOWNLOAD SOURCE ↓ MOBILE SOURCE FILES ↓ YOUR DEVELOPMENT WORKFLOW ``` AIWA Mobile Export Ready This gives developers and agencies more flexibility over what happens next. ## Why Download the Source? Downloading the source can be useful when you want greater control over the mobile application. For example, you may want to: * Continue development outside AIWA * Review the generated mobile code * Make custom changes * Use your own development workflow * Build the application yourself * Hand the project to a developer * Maintain your own mobile build process This makes AIWA useful both for users who want the simplest path and technical teams that want more control. ## Build vs Download Source The choice is straightforward. **Build App** Choose this when you want AIWA to generate the Android build for you. ```text theme={null} AIWA ↓ BUILD ↓ APK ↓ DOWNLOAD ``` **Download Source** Choose this when you want access to the mobile project files. ```text theme={null} AIWA ↓ SOURCE ↓ DOWNLOAD ↓ YOUR WORKFLOW ``` Neither approach changes the application you've already built in AIWA. It's simply a choice about how you want to continue with the mobile version. ## For Agencies This is particularly useful when you're building applications for clients. You might use AIWA to handle the entire build: ```text theme={null} CLIENT PROJECT ↓ BUILD WITH AIWA ↓ MOBILE READINESS ↓ BUILD ANDROID APP ↓ TEST ↓ DELIVER / PUBLISH ``` Or your development team may prefer: ```text theme={null} CLIENT PROJECT ↓ BUILD WITH AIWA ↓ MOBILE READINESS ↓ DOWNLOAD SOURCE ↓ DEVELOPMENT TEAM ↓ CUSTOM WORK / BUILD ``` This gives agencies flexibility depending on the requirements of each client. ## Fixing Problems Found After Export Even after passing the readiness scan, you should test the actual generated Android application. If you find a problem, return to the AIWA project and describe exactly what happened. For example: > The application passed the Mobile Readiness Scan, but in the Android build the bottom navigation covers the Save button on the profile screen. Fix the mobile layout without changing the desktop version. Then follow the process again: ```text theme={null} ISSUE FOUND ↓ FIX IN AIWA ↓ MOBILE READINESS ↓ BUILD AGAIN ↓ DOWNLOAD ↓ TEST ``` Your application can continue evolving. ## If the Build Fails If AIWA can't successfully generate the Android build, check any error information provided. When asking AIWA to investigate, provide the context. For example: > Expected: The mobile-ready project should generate an Android build. > > Mobile Readiness: Passed > > Actual: The Android build starts but fails before the APK is generated. > > Error: \[PASTE ERROR] > > Debug the Android build issue without changing unrelated application functionality. Specific information makes troubleshooting easier. ## Updating Your Android App Your first mobile build doesn't have to be your last. Your application might evolve from: ```text theme={null} Version 1 Core Product ↓ Version 2 New Features ↓ Version 3 Improved Experience ``` When you've made significant changes, you can repeat the mobile workflow: ```text theme={null} UPDATE PROJECT ↓ TEST ↓ MOBILE READINESS ↓ BUILD ↓ DOWNLOAD ↓ TEST NEW VERSION ``` This allows your mobile application to evolve alongside your AIWA project. ## Build Once, Keep Improving Mobile export is part of AIWA's broader product-development workflow. You aren't creating a disposable mobile version. You can continue: ```text theme={null} BUILD ↓ SCAN ↓ EXPORT ↓ TEST ↓ LEARN ↓ IMPROVE ↓ EXPORT AGAIN ``` Your product can continue evolving across web and mobile. ## APK Export vs Play Store Publishing Generating your Android application and publishing it on Google Play are separate steps. AIWA gets you to: ```text theme={null} AIWA PROJECT ↓ MOBILE READY ↓ BUILD ↓ ANDROID APP ``` Store distribution then involves: ```text theme={null} ANDROID APP ↓ GOOGLE PLAY ↓ REVIEW ↓ PUBLIC RELEASE ``` Google controls the Play Store submission and approval process. ## Before Moving to Google Play Before submitting your application, make sure you've tested the generated build. Check: * App installs successfully * App opens successfully * Authentication works * Navigation works * Forms work * Database functionality works * Integrations work * Mobile layouts work * Important workflows work * External links work * No test content remains * No sensitive credentials are exposed Your goal should be to submit a product you've already tested, not use the Play Store review process as your testing environment. ## Android Export Workflow The complete AIWA Android workflow is: ```text theme={null} BUILD YOUR APPLICATION ↓ TEST ↓ MOBILE READINESS SCAN ↓ READY ↓ CHOOSE ↙ ↘ BUILD APP DOWNLOAD SOURCE ↓ ↓ APK SOURCE FILES ↓ ↓ DOWNLOAD YOUR WORKFLOW ↓ TEST ↓ PLAY STORE ``` AIWA removes much of the complexity between having a working web application and having an Android build you can take forward. ## Next: Submitting to the Play Store The next page is Submitting to the Play Store. That's where we'll cover the things that AIWA doesn't need during the build, but Google may require during store submission, such as: * Google Play Developer account * Creating the app in Play Console * App name and store listing * App icon * Screenshots * App description * Privacy policy * Data safety information * Testing requirements * Uploading the Android release * Review and approval * Publishing updates That separation is much cleaner: **AIWA builds the app first. Google Play asks for the store/distribution information later.** Publish your Android build on the Google Play Store. # Export for iOS Source: https://docs.aiwa.codes/mobile/export-ios Generate an App Store kit from your AIWA project or download the mobile source, then build and test your iOS app before starting Apple's App Store workflow. Once your application has passed AIWA's Mobile Readiness Scan, you can prepare it for iOS. AIWA can take your mobile-ready application and generate an App Store kit with everything you need to build and submit it, or let you download the mobile source files so you can continue through your own development workflow. **Scan. Build. Export. Take your AIWA project toward iOS.** iOS export is available on the Agency plan and above. The App Store kit costs 10 credits and unlocks once your project scores 80 or more on the [Mobile Readiness Scan](/mobile/readiness-scan). ## Before You Export Your application should first pass the Mobile Readiness Scan. The flow is: ```text theme={null} AIWA PROJECT ↓ MOBILE READINESS SCAN ↓ READY? ↙ ↘ NO YES ↓ ↓ FIX BUILD APP ISSUES OR DOWNLOAD SOURCE ``` If AIWA identifies readiness issues, resolve them first. Once the project is determined to be ready, you can move to the iOS export options. ## Your Project Is Mobile-Ready After a successful readiness scan, AIWA gives you the next actions for mobile export. AIWA Ios Ready From here, you can choose: **Generate the App Store kit** AIWA prepares everything you need to build and submit the iOS app, including the project, a cloud build configuration, and your store listing. **Download the source** Take the mobile project files into your own development workflow. ```text theme={null} MOBILE READY ↓ CHOOSE YOUR PATH ↙ ↘ APP STORE KIT SOURCE FILES ↓ ↓ BUILD ON YOUR CI DOWNLOAD OR YOUR MAC ``` AIWA doesn't compile the iOS app or upload it to Apple for you. The App Store kit gives you a ready-made build configuration so you can build and upload from your own free cloud build account, without owning a Mac. You can also open the project in Xcode on a Mac. ## Option 1: The App Store Kit Choose the App Store kit when you want to go from your AIWA project to TestFlight and the App Store with as little setup as possible. It costs 10 credits. AIWA Ios Generate The kit contains: | Item | What it is | | - | - | | **iOS Capacitor project** | Your complete app, ready to build for the App Store | | **Cloud build config** | Build and upload without owning a Mac, on a free CI account | | **App Store listing copy** | Name, subtitle, keywords, and description, all within Apple's limits | | **fastlane metadata** | The same copy as files, so you can upload it with one command | | **App Store icon** | Your logo at 1024 × 1024, with no transparency, as Apple requires | | **Screenshot specification** | The exact sizes Apple accepts, and how to capture them | | **Privacy policy** | A real policy page, added to your app so the URL actually loads | | **App Privacy answers** | Pre-filled from what your app really uses | | **Info.plist keys** | The keys that get builds rejected if you miss them | | **Signing and TestFlight guide** | App Store Connect keys, cloud signing, and your first TestFlight build | | **Submission checklist** | Every rejection AIWA can predict, in the order you should clear them | AIWA Ios App Built Your workflow becomes: ```text theme={null} AIWA ↓ MOBILE READINESS ↓ APP STORE KIT ↓ BUILD ON YOUR CLOUD BUILD ACCOUNT OR MAC ↓ TESTFLIGHT ↓ APP STORE ``` ## Apple Developer Account To build a signed app and distribute it through Apple's App Store, you'll need your own Apple Developer account. AIWA doesn't replace Apple's developer enrollment or App Store distribution process. Your Apple Developer account is handled outside AIWA. The signing guide in the kit walks you through creating the App Store Connect keys your build needs. ## Option 2: Download the Source Files You can also download the mobile source files and manage the whole iOS project yourself. ```text theme={null} MOBILE-READY PROJECT ↓ DOWNLOAD SOURCE ↓ MOBILE SOURCE FILES ↓ YOUR DEVELOPMENT WORKFLOW ``` This can be useful when you want more control over the mobile project. Downloading the mobile source is also an Agency plan feature. ## Why Download the Source? Source export can be useful when you want to: * Continue development outside AIWA * Review the generated mobile project * Make custom mobile changes * Hand the project to an iOS developer * Manage your own build process * Maintain your own release workflow This gives agencies and development teams more flexibility. ## App Store Kit vs Download Source **App Store kit** Everything you need to build and submit, including listing copy, privacy answers, and a step-by-step guide. **Download Source** Just the mobile project files, for teams that already have their own iOS workflow. Both start from the same mobile-ready AIWA project. ## Test the iOS Experience Building the app isn't the same as validating the application. Before moving toward public distribution, test the iOS experience thoroughly. Check: * Authentication * Navigation * Forms * Database interactions * Buttons and touch interactions * Uploads * Images * External links * Integrations * Mobile layouts * Critical product workflows Your goal is to verify that the application works as a product, not simply that a build was generated. ## Test Authentication Authentication deserves particular attention on mobile. Test: ```text theme={null} Sign Up ↓ Sign In ↓ Protected Application ↓ Sign Out ``` Also test any external authentication flows your application uses. If users can sign in on both web and mobile, confirm that they can access the appropriate existing account data. ## Test Your Database Workflows If your application uses Neon Postgres, verify that the mobile app can work with the application's data correctly. For example: ```text theme={null} iOS App ↓ Create Project ↓ Neon ↓ Project Saved ``` If the same product also exists on the web, verify that information remains consistent where your architecture is designed to share data. ## Test External Integrations If your application uses connectors, test the workflows from the mobile experience too. For example: * Stripe * Resend * Twilio * Cloudinary * AI providers * Calendly * Google services Don't assume that an integration working correctly in the web experience automatically means the mobile workflow is ready. ## External Links Some functionality may leave the application temporarily. For example: ```text theme={null} App ↓ External Service ↓ Complete Action ↓ Return to App ``` Test things such as: * Payments * Scheduling * Authentication * Documents * External websites Make sure the overall flow is understandable for the user. ## Mobile Payments Payments require extra attention for App Store-distributed products. The rules can depend on what the application sells. There may be important differences between: * Physical products * Real-world services * Digital subscriptions * Digital features * In-app content Before distributing an app through Apple's App Store, review Apple's current payment requirements for your specific product. A payment workflow that works on the web may not automatically be appropriate for App Store distribution. ## Fixing Problems After Export If you find an issue in the generated iOS version, return to the AIWA project and describe the problem. For example: > The application passed Mobile Readiness, but on the iOS build the login form is partially hidden when the keyboard opens. Fix the mobile layout without changing the desktop experience. Then repeat: ```text theme={null} FIX IN AIWA ↓ TEST ↓ MOBILE READINESS ↓ BUILD AGAIN ↓ DOWNLOAD ↓ TEST ``` You don't need to rebuild the product from scratch. ## If the iOS Build Fails If your cloud build or Xcode build fails, first check the kit's submission checklist and signing guide. Most failures are signing or Info.plist issues. If the error points to your app's code, bring it back to AIWA: > Expected: The App Store kit project should build on my cloud build account. > > Mobile Readiness: Passed > > Actual: The build fails while compiling the app. > > Error: \[PASTE ERROR] > > Debug the iOS build issue without changing unrelated application functionality. Then generate a fresh kit. This gives AIWA a focused problem to investigate. ## Re-Exporting After Changes Your iOS application can evolve alongside the project. For example: ```text theme={null} Version 1 Core App Version 1.1 Improved Navigation Version 1.2 New Notifications Version 2 Major Feature Expansion ``` For each significant mobile release: ```text theme={null} UPDATE PROJECT ↓ TEST ↓ MOBILE READINESS ↓ BUILD ↓ DOWNLOAD ↓ TEST NEW VERSION ``` This keeps the mobile product aligned with your AIWA project. ## Web and iOS Can Be the Same Product Your product can exist across both experiences. ```text theme={null} YOUR PRODUCT ↙ ↘ WEB iOS ↓ ↓ USERS USERS ↘ ↙ APPLICATION ↓ DATA ``` For products designed around shared accounts and backend data, users can access the same application from different platforms. ## iOS Export for Agencies For agency work, decide ownership before taking the application toward public distribution. Clarify: * Who owns the app? * Whose Apple Developer account will be used? * Whose branding should appear? * Who manages future releases? * Who handles App Store requirements? * Who maintains the application? For a client-owned app, a workflow might be: ```text theme={null} AIWA ↓ Agency Builds App ↓ Mobile Readiness ↓ iOS Export ↓ Client Apple Developer Account ↓ App Store Workflow ``` ## iOS Export vs App Store Distribution AIWA's iOS export and Apple's App Store submission are separate processes. **AIWA** ```text theme={null} BUILD ↓ SCAN ↓ EXPORT iOS ↓ DOWNLOAD ``` **Apple** ```text theme={null} EXPORTED APP ↓ APPLE DEVELOPER WORKFLOW ↓ APP STORE SUBMISSION ↓ APPLE REVIEW ↓ RELEASE ``` AIWA currently handles the product-building and export side. Apple controls App Store distribution and approval. ## Store Approval Is Separate A successful AIWA export doesn't guarantee App Store approval. Apple has its own requirements related to areas such as: * Developer enrollment * Application functionality * Store metadata * Privacy * Data handling * Permissions * Payments * Content * Review policies These requirements can change over time. Always check Apple's current App Store requirements before submitting an application. ## Before Moving Toward the App Store Before beginning Apple's distribution process, confirm: * Mobile Readiness passed * App Store kit generated and built * Core application works * Authentication works * Navigation works * Database functionality works * Integrations work * Mobile layouts work * Critical workflows work * External links work * No sensitive credentials are exposed * The application has been tested You should be confident in the product before beginning store distribution. ## Complete iOS Export Workflow The AIWA workflow is: ```text theme={null} BUILD APPLICATION ↓ TEST ↓ MOBILE READINESS ↓ READY ↓ CHOOSE ↙ ↘ APP STORE KIT DOWNLOAD SOURCE ↓ ↓ BUILD ON YOUR SOURCE FILES CI OR MAC ↓ YOUR WORKFLOW ``` And if you later want App Store distribution: ```text theme={null} EXPORTED APP ↓ APPLE DEVELOPER WORKFLOW ↓ APP STORE ``` ## Next: Submitting to the App Store Next, we'll cover what happens outside AIWA when you take your exported iOS application toward Apple's App Store. Prepare your exported iOS application for Apple's App Store distribution. # Mobile Export Source: https://docs.aiwa.codes/mobile/overview Prepare AIWA projects for mobile distribution. Understand readiness, Android and iOS export, and how mobile fits your web application. AIWA isn't limited to websites and web applications. Eligible AIWA projects can also be prepared for mobile distribution, allowing you to take an application you've built with AIWA and move toward publishing it for Android and iOS. This means the same product you build with AIWA can potentially reach users through the web and mobile app stores. **Build once with AIWA. Launch on the web. Take your product to mobile.** ## From Web App to Mobile App Most applications you build with AIWA begin as web applications. They run in a browser and can be accessed through a live URL such as: ```text theme={null} app.yourcompany.com ``` With Mobile Export, eligible projects can be prepared for mobile distribution. Conceptually: ```text theme={null} AIWA PROJECT ↓ WEB APPLICATION ↓ MOBILE READINESS ↙ ↘ ANDROID iOS ↓ ↓ MOBILE BUILD MOBILE BUILD ↓ ↓ PLAY STORE APP STORE ``` You don't need to maintain completely separate products just because you want to reach mobile users. ## Mobile Responsive vs Mobile App These are related, but they're not the same thing. **Mobile-responsive website** A responsive AIWA project adapts to smaller screens. Users visit it through their browser: * Chrome * Safari * Edge For example: ```text theme={null} yourcompany.com ``` The interface adapts to the user's phone. **Mobile application** A mobile application is packaged for a mobile platform and can be distributed through channels such as: ```text theme={null} Google Play Store ``` or: ```text theme={null} Apple App Store ``` Users can install it on their devices and launch it like other mobile applications. A website looking good on a phone doesn't automatically mean it's ready to be distributed as a mobile app. That's why AIWA includes a mobile-readiness step before export. ## The AIWA Mobile Workflow The mobile process begins with the application you've already built. A typical workflow is: ```text theme={null} BUILD ↓ TEST WEB APP ↓ MOBILE READINESS SCAN ↓ RESOLVE ISSUES ↓ EXPORT ↓ TEST MOBILE BUILD ↓ SUBMIT TO STORE ``` Each step matters. Don't jump directly from: ```text theme={null} Build → App Store ``` without testing how the application behaves in a mobile environment. ## Start With a Working Application Before thinking about mobile export, make sure the core application works. For example, if you've built a booking application, verify that users can: ```text theme={null} Sign Up ↓ Browse Services ↓ Choose Appointment ↓ Book ↓ Receive Confirmation ↓ Manage Booking ``` If that workflow is broken on the web, exporting it to mobile won't fix the underlying product logic. Get the core application working first. Then prepare it for mobile. ## Mobile Readiness Scan Before exporting your application, AIWA can evaluate whether the project is ready for mobile. AIWA Mobile Ready The purpose of the scan is to identify areas that may need attention before creating the mobile version. Think of it as: ```text theme={null} YOUR APPLICATION ↓ MOBILE READINESS SCAN ↓ READY? ↙ ↘ YES ISSUES FOUND ↓ ↓ EXPORT REVIEW ↓ FIX ↓ SCAN AGAIN ``` We'll cover the Mobile Readiness Scan in detail on the next page. ## What Should Be Mobile-Ready? Mobile readiness isn't only about making the interface narrower. Your application needs to work well in a different usage environment. Important areas may include: * Navigation * Touch interactions * Forms * Authentication * Layouts * Modals * Tables * Images * File uploads * Payments * External links * Responsive components * Application workflows The exact requirements depend on the application you're building. ## Design for Touch Desktop users have a mouse and keyboard. Mobile users primarily interact with their fingers. That means an interface like: ```text theme={null} Tiny Button Tiny Button Tiny Button ``` may technically fit on a phone but still provide a poor mobile experience. Buttons, menus, form controls, and other interactive elements should be easy to use with touch. ## Think About Mobile Navigation A desktop application might use a large sidebar: ```text theme={null} ┌─────────────┬──────────────────────┐ │ Dashboard │ │ │ Customers │ CONTENT │ │ Projects │ │ │ Analytics │ │ │ Settings │ │ └─────────────┴──────────────────────┘ ``` On mobile, the same navigation may need to collapse into a menu or use another mobile-friendly pattern. For example: ```text theme={null} ┌─────────────────────┐ │ ☰ Dashboard │ ├─────────────────────┤ │ │ │ CONTENT │ │ │ └─────────────────────┘ ``` The goal isn't simply to shrink the desktop interface. It's to make the application comfortable to use on a smaller screen. ## Mobile Forms Forms deserve particular attention. Suppose your application contains: * Name * Email * Phone * Company * Address * Country * Message On desktop, these fields may appear across multiple columns. On mobile, a simpler vertical layout may provide a better experience. Test: * Input sizes * Dropdowns * Date pickers * File uploads * Validation messages * Submit buttons * Keyboard behavior * Long forms The entire form should remain usable on a smaller screen. ## Mobile Dashboards Dashboards can be particularly challenging because they're often designed around wide screens. A desktop dashboard might have: ```text theme={null} Revenue | Customers | MRR | Churn ``` across one row. On mobile, those cards may need to stack: ```text theme={null} Revenue Customers MRR Churn ``` Tables, charts, filters, and sidebars may also require different behavior. Tell AIWA what matters most to your mobile users. For example: > Optimize the CRM dashboard for mobile. Keep all existing desktop functionality, but make the navigation, customer list, filters, actions, and analytics comfortable to use on smaller touch screens. ## Android Export On the Agency plan and above, AIWA can prepare your application for Android distribution. The Android workflow is generally: ```text theme={null} AIWA PROJECT ↓ MOBILE READINESS ↓ ANDROID EXPORT ↓ TEST ↓ GOOGLE PLAY ``` We'll cover the Android export process on its own page. Android and iOS export are available on the Agency plan and above. The Mobile Readiness Scan is free on every plan, so you can see where your app stands before upgrading. ## iOS Export AIWA also supports the path toward distributing eligible applications on iOS. The workflow is similar: ```text theme={null} AIWA PROJECT ↓ MOBILE READINESS ↓ iOS EXPORT ↓ TEST ↓ APP STORE ``` There is an important difference: **Publishing an iOS application requires your own Apple Developer account.** AIWA doesn't replace Apple's developer enrollment or App Store submission requirements. For iOS, AIWA prepares an App Store kit, and you build the app on your own free cloud build account or a Mac. For Android, AIWA builds the installable APK for you. ## Exporting Isn't the Same as Store Approval This distinction is important. AIWA can help you prepare the application for mobile distribution. But the app stores control what is ultimately approved for their platforms. For example: ```text theme={null} AIWA ↓ Mobile Export ↓ Your App ↓ Store Submission ↓ Google / Apple Review ↓ Approved? ``` Google and Apple have their own: * Developer requirements * App policies * Content policies * Privacy requirements * Metadata requirements * Review processes AIWA cannot guarantee that every submitted application will be approved by an app store. ## You Own Your Store Presence When publishing an application, your app-store presence belongs to your product or business. For example: ```text theme={null} Your Business ↓ Developer Account ↓ Your Application ↓ Your Store Listing ``` This is particularly important for agencies. If you're building an app for a client, decide whose developer account will own and publish the application. ## Mobile Export for Agencies Mobile Export can be especially useful for agencies building products for clients. For example: ```text theme={null} CLIENT IDEA ↓ BUILD WITH AIWA ↓ WEB APPLICATION ↓ CLIENT APPROVAL ↓ MOBILE READINESS ↓ ANDROID / iOS ↓ CLIENT'S CUSTOM APP ``` You can potentially deliver both: * Web application and: * Mobile application from the same underlying product workflow. ## Example: Booking Application Suppose you build a booking platform for a fitness studio. The web application allows customers to: * Create an account * View classes * Book sessions * Manage memberships * View upcoming bookings Once the web experience is working, you can prepare it for mobile. The customer's journey becomes: ```text theme={null} Open App ↓ Sign In ↓ Browse Classes ↓ Book ↓ View Upcoming Sessions ``` The core product remains familiar across platforms. ## Example: Client Portal An agency could build a client portal where customers: * View projects * Check progress * Review deliverables * Download files * Send messages * Approve work Then prepare the same product for mobile distribution. Instead of customers always opening: ```text theme={null} portal.agency.com ``` they could also access the product through an installed mobile application. ## Example: SaaS Product Imagine you've built a SaaS application with: * Authentication * Dashboard * Projects * Team Members * Billing * Notifications * AI Features Your product could begin on the web. Once you validate it and understand how customers use it, you can prepare the experience for mobile. This allows you to follow a practical path: ```text theme={null} BUILD ↓ LAUNCH WEB ↓ GET USERS ↓ LEARN ↓ IMPROVE ↓ PREPARE MOBILE ↓ LAUNCH MOBILE ``` You don't necessarily need to launch everywhere on day one. ## Web First Can Be a Good Strategy Just because Mobile Export exists doesn't mean every project needs a mobile app immediately. For many products, launching the web version first can help you: * Validate the idea * Get customer feedback * Fix workflows * Understand usage * Improve the product * Avoid unnecessary complexity Then, when the product is ready, you can expand to mobile. ## Keep Mobile Users in Mind While Building If you already know your application will eventually become a mobile app, tell AIWA early. For example: > Build this application as a responsive web application that we plan to export to Android and iOS later. Make all primary workflows mobile-friendly and touch-friendly from the beginning. This can reduce the amount of adaptation needed later. ## Mobile and Your Backend Your mobile application may still depend on the same underlying application functionality. For example: ```text theme={null} DATABASE ↑ │ WEB APP ← APPLICATION → MOBILE APP ``` Users should generally expect the same account and application data across experiences when the product is designed that way. For example, a customer who creates a project on the web should be able to see that project from the mobile experience. ## Authentication Before exporting, test authentication carefully on mobile. Test: * Signup * Login * Logout * Protected screens * Google authentication, where applicable * Session persistence * Password flows * User roles Authentication that works in a desktop browser should still be validated in the exported mobile experience. ## External Integrations If your project uses connectors, test them in the mobile experience as well. For example: * Stripe * Resend * Twilio * Cloudinary * Google services * AI providers * Calendly A workflow working correctly on the web doesn't mean you should skip testing it in the mobile version. ## Payments on Mobile Payments can require additional consideration when applications are distributed through app stores. The type of product, what you're selling, and where the purchase occurs can affect which platform rules apply. Before publishing an application that sells products, subscriptions, digital features, or services, review the current payment requirements of the app store you're submitting to. Don't assume that a web payment implementation can always be used unchanged inside a store-distributed application. ## Mobile Doesn't Replace Your Web App Exporting your project for mobile doesn't mean you have to stop offering the web version. You may have: ```text theme={null} YOUR PRODUCT ↙ ↘ WEB MOBILE ↓ ↙ ↘ yourdomain.com Android iOS ``` Different users can choose the experience that works best for them. ## Before Mobile Export A good checklist is: * Core application works * Mobile layouts are responsive * Navigation works on small screens * Buttons are touch-friendly * Forms work on mobile * Authentication works * Database workflows work * Integrations work * Important dialogs fit * Tables are usable * Images display correctly * No unexpected horizontal scrolling * Critical workflows are tested Then run the Mobile Readiness Scan. ## The Mobile Export Journey The complete workflow is: ```text theme={null} BUILD WITH AIWA ↓ WORKING WEB APP ↓ MOBILE OPTIMIZATION ↓ MOBILE READINESS SCAN ↓ FIX ISSUES ↓ EXPORT ↙ ↘ ANDROID iOS ↓ ↓ TEST TEST ↓ ↓ STORE SUBMISSION ``` AIWA helps take your product from idea to application, and for eligible projects, beyond the browser. ## Next: Mobile Readiness Scan Before generating a mobile build, you need to know whether your application is ready. On the next page, we'll cover Mobile Readiness Scan, including: * What AIWA checks * How to run a scan * Understanding readiness issues * Fixing mobile problems * Re-running the scan * Preparing for Android and iOS export Run a readiness scan to identify mobile issues before exporting. # Mobile Readiness Scan Source: https://docs.aiwa.codes/mobile/readiness-scan Run AIWA's Mobile Readiness Scan to find mobile issues in your project, fix them, and prepare for Android or iOS export. Before exporting your AIWA application for Android or iOS, you should make sure the project is ready for a mobile environment. AIWA's Mobile Readiness Scan analyzes your application and helps identify issues that could affect the mobile experience. Instead of discovering these problems after creating your mobile build, you can find and resolve them first. **Scan first. Fix what matters. Export when your application is ready.** ## What Is the Mobile Readiness Scan? A web application and a mobile application don't always behave in exactly the same way. Your project might work perfectly in a desktop browser while still containing elements that need attention before mobile export. The Mobile Readiness Scan helps identify those issues. The workflow is: ```text theme={null} AIWA PROJECT ↓ MOBILE READINESS SCAN ↓ ANALYZE APPLICATION ↓ READINESS RESULTS ↓ FIX ISSUES ↓ SCAN AGAIN ↓ EXPORT ``` Think of it as a pre-flight check before generating your mobile application. ## When Should You Run a Scan? Run the Mobile Readiness Scan after the main application is working and you're preparing to move toward Android or iOS. Ideally: ```text theme={null} BUILD ↓ TEST ↓ MOBILE OPTIMIZE ↓ READINESS SCAN ↓ FIX ↓ EXPORT ``` Don't wait until you've already submitted your application to an app store to discover basic mobile issues. ## Run Your First Scan Open the project you want to prepare for mobile. Navigate to the Mobile Export area and start the Mobile Readiness Scan. AIWA Mobile Scan AIWA will analyze the project and determine whether there are areas that should be addressed before export. Once the analysis completes, review the results. ## Understanding Your Scan Results The readiness results help you understand the state of your application before creating a mobile build. AIWA Mobile Scan Results Depending on your project, AIWA may identify items that require attention or improvements before export. ### Your readiness score The scan gives your project a score out of 100. Each finding is either a **blocker**, something that would stop the app working properly or being accepted by a store, or a **warning**, something worth improving. | Score | What you can do | | - | - | | **80 or more** | Build the Android APK, the Google Play kit, and the App Store kit (Agency plan and above) | | **Below 80** | Fix the findings and scan again | Any blocker brings your score below 80. A few warnings on their own won't. ### Free scan and deep scan | Scan | What it checks | Cost | | - | - | - | | **Readiness scan** | Automatic checks of your project's files, such as tap targets, safe areas, dark mode, the back button, responsiveness, and store compliance | Free, on every plan | | **Deep scan** | An AI review of the areas that need judgement, such as native-feeling layouts, animations, and dropdowns | 2 credits | Together they cover 13 areas: * Dark Mode * Safe Area Handling * Unified Navigation & Back Stack * Optimistic UI Updates * Overscroll & Sticky Elements * Tap Targets * Native-Like Layouts * Bottom Tabs & Stack Preservation * Dropdowns & Selection Controls * Screen Animations & Transitions * Performance * Responsiveness (Mobile-First) * App Store Review Compliance Don't think of a readiness issue as: > My application is broken. Instead, think of it as: > There's something I should address before packaging this application for mobile. ## What AIWA Is Looking For Mobile readiness involves more than visual responsiveness. AIWA needs to consider whether important parts of your application can provide a usable experience in a mobile environment. Depending on your application, areas worth reviewing include: * Responsive layouts * Navigation * Touch interactions * Forms * Authentication * Dialogs and modals * Tables * Images * File uploads * External links * Integrations * Application workflows * Mobile-specific behavior Not every project will have the same issues. A simple business website and a complex CRM have very different mobile requirements. ## Responsive Layouts One of the first things to check is whether the interface adapts properly to smaller screens. For example, a desktop layout might be: ```text theme={null} ┌───────────────────────────────────────┐ │ Sidebar │ Dashboard │ │ │ │ │ │ Card │ Card │ Card │ Card │ │ │ │ │ │ Large Data Table │ └───────────────────────────────────────┘ ``` That shouldn't simply be squeezed into a phone-sized screen. A mobile layout might become: ```text theme={null} ┌─────────────────────┐ │ ☰ Dashboard │ ├─────────────────────┤ │ Revenue │ ├─────────────────────┤ │ Customers │ ├─────────────────────┤ │ MRR │ ├─────────────────────┤ │ Activity │ └─────────────────────┘ ``` The information remains available, but the presentation adapts. ## Navigation Desktop navigation patterns don't always translate well to mobile. For example, a permanent sidebar may need to become: * A collapsible menu * A drawer * A compact navigation experience * Another touch-friendly navigation pattern Test whether users can easily move between the application's most important areas. Ask yourself: > Could someone comfortably use this application with one hand on a phone? ## Touch Targets Buttons and controls need to be easy to tap. A tiny icon that works perfectly with a mouse may be frustrating on a touchscreen. Review: * Buttons * Menu items * Icons * Dropdowns * Tabs * Checkboxes * Table actions * Form controls Avoid placing several tiny interactive elements too close together. ## Forms Forms are one of the most important areas to test. Suppose your desktop form looks like: ```text theme={null} First Name Last Name Email Phone Company Website Address City ``` On mobile, stacking the fields may provide a better experience: ```text theme={null} First Name Last Name Email Phone Company Website Address City ``` Also check: * Input visibility * Validation messages * Dropdowns * Date pickers * Submit buttons * Long forms * File uploads * Keyboard interaction ## Tables Tables are common in SaaS applications, CRMs, admin dashboards, and internal tools. They're also one of the easiest desktop patterns to get wrong on mobile. Imagine: ```text theme={null} Name | Email | Company | Plan | Status | Created | Actions ``` Trying to display every column on a narrow phone screen may create horizontal scrolling or unreadable content. Instead, consider displaying the most important information first. For example: ```text theme={null} Sarah Chen Acme Ltd. Agency Active [View] ``` Then show the remaining information on the detail screen. ## Modals and Dialogs Check whether dialogs fit inside smaller screens. A modal designed for desktop can sometimes: * Extend beyond the screen * Hide buttons * Become difficult to scroll * Place important controls behind the keyboard For mobile, dialogs should remain accessible and usable throughout the interaction. ## Authentication Test the complete authentication experience on mobile. This includes: ```text theme={null} Sign Up ↓ Verify / Authenticate ↓ Sign In ↓ Protected Application ↓ Sign Out ``` If you're using Google authentication or another external authentication flow, test that as well. Authentication is too important to assume it will behave correctly simply because it works on desktop. ## Images and Media Large images can affect the mobile experience. Check: * Image sizing * Aspect ratios * Galleries * Avatars * Hero images * Uploaded media * Video * Loading behavior An image that looks impressive across a desktop screen may dominate too much of the interface on mobile. ## External Links Your application may open: * Payment pages * Scheduling pages * Documents * External websites * Authentication providers * Third-party services Test what happens when these links are opened from the mobile experience. Make sure users can complete the workflow and return to the application where appropriate. ## Integrations If your application depends on connectors, include them in your mobile testing. For example: ```text theme={null} Mobile App ↓ Booking ↓ Google Calendar ↓ Resend ↓ Confirmation ``` Don't only check whether the booking button works. Test the complete workflow. ## Fixing Readiness Issues If the scan identifies something that needs attention, work through the issues before exporting. For example, you might tell AIWA: > Optimize the customer dashboard for mobile based on the readiness issues identified. Preserve the current desktop experience and functionality. Or: > Fix the mobile navigation and table issues identified by the readiness scan without changing the existing desktop layout. AIWA can then work on the specific areas that need improvement. ## Don't Fix Everything by Redesigning Everything A readiness issue doesn't necessarily require a complete redesign. For example, if the problem is: > Customer table doesn't fit on mobile. Don't immediately ask: > Completely redesign my entire CRM. Instead: > Make the customer table usable on mobile while preserving the existing desktop table and functionality. Smaller, targeted changes reduce the risk of breaking working parts of your application. ## Preserve the Desktop Experience Mobile optimization shouldn't unnecessarily damage the desktop version. Tell AIWA when both experiences matter. For example: > Optimize this dashboard for mobile screens while preserving the current desktop layout for larger screens. Conceptually: ```text theme={null} APPLICATION ↓ RESPONSIVE EXPERIENCE ↙ ↘ DESKTOP MOBILE ``` The same application can adapt to the device being used. ## Re-Run the Scan After addressing the identified issues, run the Mobile Readiness Scan again. AIWA Improved Scan Results The process is intentionally iterative: ```text theme={null} SCAN ↓ ISSUES ↓ FIX ↓ SCAN AGAIN ↓ MORE ISSUES? ↙ ↘ YES NO ↓ ↓ FIX EXPORT ``` Don't assume that making one change means the entire application is ready. ## Test Manually Too The Mobile Readiness Scan is a useful tool, but it shouldn't replace actually using your application. Open the mobile preview and walk through the important customer journeys. For example, for an e-commerce application: ```text theme={null} Open App ↓ Browse Products ↓ View Product ↓ Add to Cart ↓ Checkout ↓ Confirmation ``` For a CRM: ```text theme={null} Login ↓ View Leads ↓ Open Lead ↓ Update Status ↓ Add Note ↓ Create Follow-Up ``` The goal is to determine whether the product feels usable, not merely whether the interface technically fits. ## Test Different Screen Sizes Mobile devices aren't all the same size. An application that looks good on a large phone may have problems on a smaller one. Pay particular attention to: * Fixed widths * Long text * Navigation * Tables * Forms * Buttons * Bottom actions * Modals Avoid designing for only one specific phone. ## Portrait Orientation Most users will interact with your application in portrait orientation. Make sure the primary workflows work comfortably in that layout. For example: ```text theme={null} ┌───────────────────┐ │ │ │ YOUR APP │ │ │ │ │ │ │ │ │ └───────────────────┘ ``` Don't depend on users rotating their phone just to complete ordinary tasks. ## Check for Horizontal Scrolling Unexpected horizontal scrolling is often a sign that something doesn't fit properly. Common causes include: * Wide tables * Fixed-width components * Large images * Long unbroken text * Desktop navigation * Oversized modals If the whole application moves sideways while users scroll, investigate which component is causing the overflow. ## Check Fixed Elements Applications sometimes use fixed: * Headers * Navigation * Chat widgets * Action buttons * Bottom bars Make sure these don't cover important content on smaller screens. For example: ```text theme={null} ┌─────────────────────┐ │ Content │ │ │ │ │ │ │ │ [Important Button] │ ├─────────────────────┤ │ Fixed Navigation │ └─────────────────────┘ ``` The navigation shouldn't hide the button above it. ## Test Empty States Don't only test screens full of sample data. Test what a new user sees. For example: ```text theme={null} Projects You haven't created a project yet. [Create Your First Project] ``` A mobile user should understand what to do next even when the screen contains no data. ## Test Error States Also test what happens when something goes wrong. For example: ```text theme={null} Payment failed We couldn't complete your payment. [Try Again] ``` or: ```text theme={null} Unable to load projects. [Retry] ``` Errors shouldn't create unusable screens or trap the user. ## Mobile Performance Mobile users may have slower connections and less powerful devices than desktop users. Avoid unnecessarily heavy experiences where possible. Be mindful of: * Very large images * Excessive media * Large amounts of content loaded at once * Heavy animations * Unnecessary visual effects A beautiful application that feels slow can still provide a poor mobile experience. ## Payments Require Special Attention If your application involves payments, don't treat mobile readiness as only a layout problem. Applications distributed through Google Play or Apple's App Store may be subject to store-specific payment requirements depending on what you're selling. Before submission, make sure the payment model complies with the requirements of the store you're targeting. We'll discuss store submission separately. ## A Good Mobile Optimization Prompt A strong prompt could look like: > Review the application for mobile readiness. Preserve the current desktop experience. Optimize the navigation, dashboard cards, customer tables, forms, dialogs, and primary workflows for smaller touch screens. Avoid unnecessary horizontal scrolling and ensure important actions remain easy to access. Don't remove any existing functionality. That's much stronger than: > Make it mobile friendly. ## Use Plan Mode for Complex Applications For a large application, consider planning the mobile adaptation before changing anything. For example: > Analyze this application for mobile use. Identify which layouts, navigation patterns, tables, forms, dialogs, and workflows need to change for a good mobile experience. Create a plan only. Don't modify the application yet. Review the plan. Then implement the changes. ```text theme={null} EXPLORE ↓ PLAN ↓ REVIEW ↓ BUILD ↓ SCAN ``` ## When Is Your Application Ready? Mobile readiness doesn't mean: > Every screen looks exactly like the desktop version. It means the important application experiences work effectively on mobile. Before export, you should be confident that users can: * Navigate the application * Read important content * Use primary features * Complete forms * Authenticate * Access their data * Complete critical workflows * Recover from errors without fighting the interface. ## Mobile Readiness Checklist Before moving to export, check: * Mobile Readiness Scan completed * Major readiness issues resolved * Navigation works * No unexpected horizontal scrolling * Buttons are touch-friendly * Forms work * Tables are usable * Modals fit * Authentication works * Images display correctly * External links work * Integrations work * Important workflows work * Empty states work * Error states work * Desktop experience still works * Application tested manually on mobile Then you're ready for the next stage. ## From Scan to Export The process should look like: ```text theme={null} WORKING WEB APP ↓ MOBILE READINESS SCAN ↓ REVIEW RESULTS ↓ FIX ISSUES ↓ TEST ↓ SCAN AGAIN ↓ READY ↓ MOBILE EXPORT ``` The scan isn't an obstacle between you and your mobile app. It's there to help make sure what you export is actually ready to be used. ## Next: Export for Android (APK) Your application is mobile-ready. Next, we'll take it to Android. We'll cover: * Starting an Android export * Preparing your application * App name and identity * App icon * Package information * Generating the Android build * Downloading and testing the build * What to do when an export fails * Preparing for Google Play submission Generate an Android build of your AIWA project. # Preparing for the App Store Source: https://docs.aiwa.codes/mobile/submit-app-store AIWA prepares your App Store kit. Use your Apple Developer account to build, sign, and submit your iOS app to the App Store. After exporting your iOS application from AIWA, you may choose to distribute it through Apple's App Store. AIWA prepares your iOS project and an App Store kit with your listing copy, privacy answers, and a signing guide. You build and sign the app on your own cloud build account or Mac, and submit it through your own Apple Developer account. **AIWA prepares the app and the kit. You build, sign, and submit through Apple.** AIWA does not compile your iOS app or submit it to the App Store on your behalf. ## Where AIWA Stops The current AIWA iOS workflow takes you through: ```text theme={null} AIWA PROJECT ↓ MOBILE READINESS ↓ APP STORE KIT ↓ DOWNLOAD ``` From that point onward, Apple's developer and App Store processes happen outside AIWA. Conceptually: ```text theme={null} AIWA ↓ iOS Export ↓ Your iOS App ↓ Apple Developer Workflow ↓ App Store ↓ Apple Review ↓ Distribution ``` Apple controls the requirements and approval process for App Store distribution. ## You'll Need an Apple Developer Account To distribute an app through the App Store, you'll need your own Apple Developer account. Apple manages developer enrollment separately from AIWA. For agencies, decide early who should own the application. For example: ```text theme={null} AIWA ↓ Agency Builds App ↓ iOS Export ↓ Client Apple Developer Account ↓ App Store ``` For a client-owned product, publishing through the client's developer account can make long-term ownership clearer. ## App Store Information AIWA doesn't need all of your App Store listing information in order to prepare the kit. The kit includes draft listing copy you can edit before submitting. Apple may ask for additional information during the distribution process. This can include things such as: * App name * App icon * App description * Screenshots * App category * Support information * Privacy information * Age rating * Data-use information * Content declarations These belong to the App Store publishing process rather than the AIWA build process. ## App Icon and Store Assets You'll typically need polished visual assets for your store listing. These may include: * App icon * iPhone screenshots * Other store imagery Apple currently requires Prepare assets that accurately represent the product. For example, a CRM app might show: * Dashboard * Leads * Deal pipeline * Customer details * Mobile navigation A booking app might show: * Services * Booking flow * Customer dashboard * Upcoming appointments Avoid using screenshots containing real private customer data. ## App Description Your listing should explain the product from the user's perspective. For example: > Acme Client Portal gives customers one place to track projects, access files, review deliverables, communicate with their team, and monitor progress from their iPhone. A useful description answers: * What is the app? * Who is it for? * What can they accomplish with it? You don't need to explain the underlying AIWA architecture to App Store users. ## Privacy Policy If your application collects or processes user information, Apple may require appropriate privacy disclosures and a privacy policy. This can become relevant when your app uses: * User accounts * Customer information * Files * Images * Payments * Location * Analytics * External integrations Your privacy policy should reflect what the application actually does. Don't use a generic privacy policy that doesn't match your application's actual data collection and processing. ## App Privacy Information Apple may ask you to disclose how the application handles data. Depending on your product, this could involve information such as: * Contact information * Account details * User content * Purchases * Files * Identifiers * Usage data * Other application activity Your disclosures should reflect the actual application and any external services it uses. For example: ```text theme={null} USER ↓ AIWA APP ↓ NEON ↓ STRIPE / RESEND / CLOUDINARY / OTHER SERVICES ``` Understanding your application's data flow helps make these disclosures more accurate. ## Device Permissions Some apps may need access to device capabilities. Examples include: * Camera * Photos * Microphone * Files * Notifications * Location Only request permissions the application genuinely needs. For example, a profile-photo feature may need access to photos or camera functionality. A simple dashboard app probably shouldn't request location access unless there's a clear product reason. ## Explain Why Permissions Are Needed Apple may require applications to clearly explain why certain permissions are requested. For example: > Camera access is used to upload profile photos. or: > Photo-library access is used to attach images to property listings. The permission should make sense in the context of the feature. ## Payments Require Extra Attention If your app sells: * Digital subscriptions * Digital content * In-app functionality * Other digital goods Apple may have specific payment requirements. This can differ from selling: * Physical products * Real-world services * Certain external services A Stripe payment flow that works perfectly on the web may not automatically satisfy App Store rules for every type of purchase. Before submission, review Apple's current payment requirements for your exact business model. ## Test Before Distribution Before beginning App Store submission, test the exported iOS application thoroughly. Check: * App launches * Authentication * Navigation * Forms * Database functionality * Uploads * Integrations * External links * Mobile layouts * Critical workflows * Error states App Store review shouldn't be your first real QA session. ## Test Important User Journeys For a SaaS app: ```text theme={null} Open App ↓ Sign Up ↓ Login ↓ Dashboard ↓ Use Core Feature ↓ Account Settings ``` For a booking app: ```text theme={null} Open App ↓ Browse ↓ Choose Service ↓ Book ↓ Confirmation ``` For a client portal: ```text theme={null} Login ↓ Projects ↓ Open Project ↓ View Files ↓ Send Message ``` The complete customer journey should work. ## Apple's Review Process Apple reviews submitted apps according to its own current guidelines and requirements. Review may involve areas such as: * Application functionality * Privacy * Data handling * Permissions * Payments * Store metadata * Content * User experience AIWA doesn't control Apple's approval decision. App Store requirements can change. Check Apple's current developer guidance when you're ready to submit. ## If Apple Rejects the App A rejection doesn't necessarily mean the entire product needs to be rebuilt. First understand the reason. For example: > Missing privacy information is different from: > App crashes when users sign in. If Apple identifies a product issue, return to AIWA and address that specific problem. For example: > During App Store review, the app crashes when a signed-out user opens the Account screen. Debug this flow without changing the rest of the mobile app. Then: ```text theme={null} FIX IN AIWA ↓ MOBILE READINESS ↓ NEW APP STORE KIT ↓ TEST ↓ RESUBMIT ``` ## Updating the App Later Your application will likely continue evolving after release. For example: ```text theme={null} LIVE iOS APP ↓ Improve in AIWA ↓ Mobile Readiness ↓ New App Store Kit ↓ Build on Your CI or Mac ↓ Test ↓ Upload New Version ↓ Apple Review ↓ Release ``` AIWA remains the product-development environment while Apple manages store distribution. ## For Agencies If you're building iOS apps for clients, clarify responsibilities before launch. Decide: * Who owns the Apple Developer account? * Who owns the app? * Who prepares store assets? * Who manages privacy disclosures? * Who responds to Apple review questions? * Who publishes updates? * Who maintains the app? This avoids confusion later. ## AIWA's Role A simple way to understand the current boundary is: **AIWA handles** * Building the application * Mobile readiness * The App Store kit: project, cloud build config, listing copy, icon, privacy policy, and App Privacy answers * Mobile source export **You handle outside AIWA** * Apple Developer account * Building and signing the app * Reviewing the store listing * Screenshots * Privacy disclosures * App Store submission * Apple review * Public release This makes the workflow clear. ## Before You Begin App Store Submission Prepare: * A tested iOS build * Apple Developer account * App name * App icon * Description * Screenshots * Privacy policy where required * App privacy information * Required permission explanations * Appropriate payment model * Support information Then follow Apple's current submission process. ## The Complete iOS Journey Today, the complete flow looks like: ```text theme={null} BUILD WITH AIWA ↓ MOBILE READINESS ↓ APP STORE KIT ↓ BUILD ON YOUR CI OR MAC ↓ TEST ↓ APPLE DEVELOPER WORKFLOW ↓ APP STORE REQUIREMENTS ↓ SUBMIT ↓ APPLE REVIEW ↓ RELEASE ``` AIWA handles the product-building and export side. Apple handles distribution. ## Next: Inviting Team Members Invite collaborators to your AIWA workspace. # Preparing for Google Play Source: https://docs.aiwa.codes/mobile/submit-play-store AIWA builds your Android app. Use your Google Play Developer account to prepare store assets, disclosures, and the Play Store submission. After exporting your Android application from AIWA, you may choose to distribute it through Google Play. AIWA currently helps you build and export the Android application, but Google Play submission is handled separately through your own Google Play Developer account. **AIWA builds the app. You manage the store submission through Google Play.** AIWA does not currently submit applications to Google Play on your behalf. ## Where AIWA Stops The AIWA mobile workflow currently takes you through: ```text theme={null} AIWA PROJECT ↓ MOBILE READINESS ↓ BUILD ANDROID APP ↓ DOWNLOAD / EXPORT ``` From that point onward, distribution through Google Play takes place outside AIWA. Conceptually: ```text theme={null} AIWA ↓ Android Export ↓ Your Android App ↓ Google Play Console ↓ Google Review ↓ Store Distribution ``` Google controls the requirements and approval process for apps distributed through Google Play. ## The Google Play Release Kit AIWA can do much of the store paperwork for you. The **Google Play release kit** costs 5 credits on the Agency plan and above, and includes: | Item | What it is | | - | - | | **Installable APK** | Your app, ready to put on any Android phone today | | **Full source project** | The complete Capacitor project you build your release from | | **Play store icon** | Your logo at 512 × 512, the exact size Play requires | | **Feature graphic** | 1024 × 500. Play won't publish a listing without one | | **Store listing copy** | App name, both descriptions, release notes, and a suggested category | | **Privacy policy and its URL** | Play requires a live URL, not a file. Publishing again puts yours online | | **Data safety and content rating** | Pre-filled answers for the two Play forms people get stuck on | | **Signing kit** | Keystore commands and build files, with your app ID already filled in | You still review everything and submit it yourself through Google Play. ## You'll Need a Google Play Developer Account To distribute an application through Google Play, you'll generally need your own Google Play Developer account. For agencies, this raises an important ownership decision. If the application belongs to a client, consider whether the app should be published through: * Your agency's developer account * The client's own developer account For long-term client ownership, using the client's account may often make more sense. For example: ```text theme={null} AIWA ↓ Agency Builds App ↓ Android Export ↓ Client Developer Account ↓ Google Play ``` This keeps the store listing and future ownership associated with the client. ## Google May Require Additional App Information AIWA doesn't need all of your store-listing information to generate the mobile app. Google Play, however, may ask for additional information before an application can be distributed. This may include things such as: * Application name * App icon * Short description * Full description * Screenshots * App category * Contact information * Privacy policy * Content declarations * Data-handling information * Age or audience information These requirements belong to the store publishing process, not the AIWA build process. ## App Icon and Store Graphics Your exported application may eventually need visual assets for its Google Play listing. These can include an app icon and store screenshots. The store may also require other promotional or listing assets depending on current requirements. These assets are typically prepared after the app itself is built and tested. A practical workflow is: ```text theme={null} BUILD APP ↓ TEST APP ↓ PREPARE STORE ASSETS ↓ CREATE STORE LISTING ``` ## Screenshots Google Play may ask you to provide screenshots showing what your application looks like. Choose screenshots that demonstrate the most important parts of the product. For example, a CRM might show: * Dashboard * Leads * Deal pipeline * Customer detail * Mobile navigation A booking app might show: * Service selection * Appointment booking * Customer dashboard * Upcoming appointments Don't use screenshots containing private customer data. ## App Description Your store listing will usually need to explain what the application does. A useful description should answer: * What is the app? * Who is it for? * What can users do with it? For example: > Acme Client Portal helps customers track projects, access files, review deliverables, communicate with their account manager, and monitor project progress from one mobile app. Avoid filling the listing with technical implementation details users don't need. ## Privacy Policy If your application collects or processes user information, Google may require a privacy policy. That can become especially relevant when your app uses: * User accounts * Customer information * Payments * Location * Files * Camera or media * Contacts * Analytics * External services Your privacy policy should accurately describe what your application actually does. Don't copy a generic privacy policy that doesn't match your application. Your disclosures should reflect the data your product actually collects and uses. ## Data Safety Google may ask you to disclose how your application handles user data. Depending on your product, that could involve information such as: * Account details * Personal information * Payment-related data * Uploaded files * User-generated content * Application activity This is one reason to understand your application's data model and integrations before publishing. For example: ```text theme={null} USER ↓ AIWA APP ↓ NEON ↓ STRIPE / RESEND / CLOUDINARY / OTHER SERVICES ``` Your disclosures may need to account for the services involved in your application. ## Permissions Some Android apps require access to device capabilities. Examples may include: * Camera * Photos * Files * Notifications * Microphone * Location If your application requests device permissions, make sure they are genuinely needed for the feature. A useful rule is: > Request only the permissions your application actually needs. Users may be uncomfortable with an app requesting access that doesn't make sense for its purpose. ## Payments Applications distributed through Google Play may be subject to specific payment rules depending on what the app sells. For example, there can be an important distinction between: * Physical goods * Real-world services * Digital products * Digital subscriptions * In-app features If your AIWA application uses Stripe or another external payment workflow, don't assume that the same implementation can automatically be used for every type of Play Store application. Review Google's current payment requirements before submitting an app that sells digital products, subscriptions, or in-app functionality. ## Test the Exported App First Before creating your store listing, test the exported Android application thoroughly. Check: * Installation * App launch * Authentication * Navigation * Forms * Database functionality * Uploads * Integrations * External links * Mobile layouts * Important user workflows You want store submission to be the distribution step, not the first time you seriously test the application. ## Testing Releases Google Play may offer different ways to test an application before making it publicly available. This can be useful for distributing the app to: * Your team * QA testers * Selected customers * Beta users A sensible release path is: ```text theme={null} AIWA EXPORT ↓ INTERNAL TESTING ↓ FIX ISSUES ↓ BROADER TESTING ↓ PUBLIC RELEASE ``` The exact testing and release options are managed inside Google Play. ## Google Controls App Approval AIWA doesn't control whether Google approves an application. Google reviews applications according to its own requirements and policies. An app may need changes before approval. For example, Google may raise issues related to: * Privacy * Permissions * Store listing information * App functionality * Payments * Content * Data handling * Developer-account requirements Google's policies and submission requirements can change over time. Always check the current Play Console guidance before submitting. ## If Google Rejects the App A rejection doesn't necessarily mean you need to rebuild the entire application. First understand the reason. For example, if the issue is: > Missing privacy disclosure that's different from: > The application crashes during startup. If Google identifies an application issue, return to AIWA and fix the specific problem. For example: > Google Play testing found that the application crashes when a signed-out user opens the Profile screen. Debug that flow without changing the rest of the mobile application. Then generate and test a new Android build. ## Updating an App Later Mobile applications continue evolving after release. Your workflow may become: ```text theme={null} LIVE APP ↓ Improve in AIWA ↓ Mobile Readiness ↓ New Android Build ↓ Test ↓ Upload New Version ↓ Google Play ``` You manage the Google Play release process externally while AIWA remains your development environment. ## For Agencies If you're delivering Android applications to clients, decide responsibilities before launch. Clarify: * Who owns the Google Play Developer account? * Who prepares store assets? * Who writes the listing? * Who manages the privacy policy? * Who handles Google review feedback? * Who publishes future updates? * Who provides customer support? This avoids ownership confusion after the app is live. ## AIWA's Role A useful way to understand the current workflow is: **AIWA handles** * Building the application * Mobile readiness * Android build generation * Android source export **You handle outside AIWA** * Google Play Developer account * Store listing * Store assets * Policy declarations * Submission * Google review * Public release This keeps the responsibility clear. ## Before You Begin Google Play Publishing Once your Android app has been exported, prepare: * A tested Android build * Google Play Developer account * App name * App icon * Store description * Screenshots * Privacy policy where required * Appropriate data disclosures * Required permissions information * Appropriate payment model * Support/contact information Then follow Google's current Play Console process. ## The Complete Android Journey Today, the AIWA-to-Google-Play journey looks like: ```text theme={null} BUILD WITH AIWA ↓ MOBILE READINESS ↓ BUILD ANDROID APP ↓ DOWNLOAD / EXPORT ↓ TEST ↓ GOOGLE PLAY CONSOLE ↓ STORE REQUIREMENTS ↓ SUBMIT TO GOOGLE ↓ GOOGLE REVIEW ↓ RELEASE ``` AIWA handles the product-building and Android-export portion. Google Play handles distribution and approval. ## Next: Export for iOS Next, we'll return to functionality available inside AIWA and cover Export for iOS. The flow is similar to Android: * Mobile Readiness * Build iOS files or download source * Export We'll also explain why you'll need your own Apple Developer account when you're ready to take the exported application toward App Store distribution. Export your AIWA project toward iOS distribution. # Custom Domains Source: https://docs.aiwa.codes/publishing/custom-domains Connect your own domain to a published AIWA project: root domain, subdomain, DNS setup, verification, and client domain workflows. AIWA lets you connect your own custom domain to a published project. Instead of sharing an AIWA-provided project URL, you can launch your website or application at an address such as: ```text theme={null} yourcompany.com ``` or: ```text theme={null} app.yourcompany.com ``` AIWA continues hosting your application while your custom domain becomes the address your users see. **Build with AIWA. Publish with AIWA. Launch on your own domain.** Custom domains are available on the Solo plan and above. ## What Is a Custom Domain? When you first publish a project, AIWA provides a live URL you can use to access and share it. A custom domain lets you replace that public-facing address with a domain you own. For example: ```text theme={null} AIWA Project ↓ Publish ↓ AIWA Hosting ↓ yourcompany.com ``` Your application remains hosted by AIWA. The domain simply provides your branded address. ## Before You Start You'll need: * A published AIWA project * A domain you own * Access to the domain's DNS settings * An AIWA plan that supports custom domains Your domain may be registered with providers such as Cloudflare, GoDaddy, Namecheap, or another domain registrar/DNS provider. You don't need to transfer ownership of the domain to AIWA. You only need to configure the required DNS records. ## Root Domains and Subdomains You can connect a root domain or use a subdomain depending on how you want your application to be accessed. **Root domain** ```text theme={null} yourcompany.com ``` This is useful when the AIWA project is your primary website. For example: ```text theme={null} acmeconstruction.com ``` **Subdomain** ```text theme={null} app.yourcompany.com ``` This is useful when your main website already exists somewhere else. For example: ```text theme={null} www.acme.com ``` could remain your marketing website, while: ```text theme={null} app.acme.com ``` points to your AIWA application. Other examples include: ```text theme={null} portal.yourcompany.com members.yourcompany.com dashboard.yourcompany.com book.yourcompany.com clients.yourcompany.com ``` Choose the structure that fits your product. ## Connect a Custom Domain First, publish your AIWA project. Then open **Control Panel → Domains** and choose the option to connect a custom domain. AIWA Custom Domain Pick the company that manages your domain's DNS records. This may be different from where you bought the domain. AIWA uses your choice to show step-by-step instructions for that provider. For example, `yourcompany.com` or `app.yourcompany.com`. For a root domain, AIWA recommends **[www.yourcompany.com](http://www.yourcompany.com)**. This keeps your website's records separate from the records your email depends on. AIWA then shows the exact DNS records to add. ## Configure Your DNS Your domain's DNS tells browsers where your application is hosted. After entering your domain in AIWA, you'll be given the DNS record or records required for the connection. AIWA Dns Records Open the DNS management area at the provider managing your domain. Add the records exactly as AIWA provides them. Always use the DNS values displayed by AIWA for your project. Don't copy DNS values from another AIWA project or from an example in this documentation. ### AIWA protects your email Connecting a website to a domain that already has email is the most common way people accidentally break their email. Before showing any instructions, AIWA checks your domain's public DNS and saves a snapshot of your email records (MX, SPF, DKIM, and DMARC). It then: * Tells you which records to leave alone * Warns you before you'd replace an existing website or conflict with an email record * Lets you use **Check email records** later to compare against the snapshot AIWA's checks look at public DNS records. They can't test whether email is actually delivered, so after changing DNS, send and receive a test email. ## Understanding DNS Records Depending on the domain configuration, you may encounter records such as: ```text theme={null} A ``` or: ```text theme={null} CNAME ``` A CNAME commonly maps a hostname such as: ```text theme={null} app.yourcompany.com ``` to another hostname. An A record maps a hostname to an IP address. You don't need to understand the networking behind these records to connect your domain. The important part is to copy the exact values AIWA provides into your DNS provider. ## Example: Connecting a Subdomain Suppose your company owns: ```text theme={null} acme.com ``` Your existing marketing website is already running at: ```text theme={null} www.acme.com ``` You build a customer portal with AIWA and want it available at: ```text theme={null} portal.acme.com ``` Inside AIWA, add: ```text theme={null} portal.acme.com ``` as your custom domain. AIWA provides the required DNS configuration. You then add that configuration to the DNS settings for acme.com. Conceptually: ```text theme={null} Customer ↓ portal.acme.com ↓ DNS ↓ AIWA ↓ Customer Portal ``` Your existing website doesn't need to move. ## Example: Business Website Suppose you build a construction company website with AIWA. You own: ```text theme={null} buildright.com ``` You can connect that domain to the AIWA project so customers visit: ```text theme={null} buildright.com ``` instead of the original project URL. The final experience becomes: ```text theme={null} Visitor ↓ buildright.com ↓ AIWA-hosted Website ``` ## Example: SaaS Application For a SaaS business, you might separate the marketing website from the application. For example: ```text theme={null} aiwaexample.com ``` Marketing website and: ```text theme={null} app.aiwaexample.com ``` Web application The application subdomain can point to the project you've built with AIWA. ## Verify Your Domain After adding the required DNS records, return to AIWA. AIWA needs to detect the DNS configuration before the domain can become active. AIWA Custom Domain Status Depending on your DNS provider, changes may not appear immediately. DNS updates can require some time to propagate. During this period, AIWA may still show the domain as pending or unverified. Your domain goes through these stages: | Status | What it means | | - | - | | **Pending** | AIWA is waiting to see your DNS records | | **Ownership verified** | Your records are correct and AIWA has confirmed you own the domain | | **Securing (HTTPS)** | AIWA is waiting for the secure certificate to be issued | | **Live** | Your domain serves your app over a valid HTTPS connection | AIWA only marks a domain as live once a real HTTPS request to it succeeds. That way, your visitors never land on a "Not secure" warning while the certificate is still being issued. ## DNS Propagation When you change DNS records, the update has to propagate across DNS infrastructure. This means your domain may not start working instantly. You might see: ```text theme={null} DNS Updated ↓ Propagation ↓ AIWA Detects Record ↓ Domain Verified ↓ Domain Active ``` If you just added the records, allow time before assuming something is broken. ## Don't Repeatedly Change DNS Records If you've entered the exact records AIWA requested, avoid repeatedly deleting and recreating them while waiting for propagation. Doing so can make troubleshooting more difficult. Instead: * Confirm the record is correct. * Confirm you're editing the correct domain. * Wait for DNS propagation. * Check the domain status again. ## Existing DNS Records Be careful when your domain is already being used for other services. Your DNS may contain records for: * Your existing website * Email * Verification services * Other applications * Subdomains Don't delete unrelated records just because you're connecting an AIWA project. Removing or replacing the wrong DNS records can interrupt your website, email, or other services using the domain. If you're unsure, add only the records AIWA specifically requires. ## Connecting a Client's Domain If you're an agency, you can also connect a client's domain to the project you've built for them. For example: ```text theme={null} AIWA ↓ Client Website ↓ clientcompany.com ``` You'll need access to the client's DNS configuration or assistance from whoever manages their domain. A simple agency workflow is: ```text theme={null} Build Client Project ↓ Client Approval ↓ Publish ↓ Connect Client Domain ↓ Update DNS ↓ Verify ↓ Launch ``` ## Multiple Client Projects If you're managing multiple projects, each client can use their own domain. For example: ```text theme={null} Project A → clienta.com Project B → clientb.com Project C → app.clientc.com ``` The domain is associated with the appropriate published project. Your plan limits and available domain features depend on your AIWA plan. ## Custom Domains and Hosting Connecting a custom domain doesn't mean you're moving the application to another hosting provider. The architecture remains: ```text theme={null} CUSTOM DOMAIN ↓ AIWA HOSTING ↓ YOUR APPLICATION ``` AIWA continues hosting the published project. This is different from exporting the application and deploying it to your own VPS. ## Custom Domain vs Self-Hosting These are two different options. **Custom domain + AIWA hosting** ```text theme={null} yourdomain.com ↓ AIWA ↓ Your Application ``` AIWA manages the hosting. **Self-hosting** ```text theme={null} AIWA ↓ Export ↓ Your VPS / Infrastructure ↓ yourdomain.com ``` You manage the hosting. If your only goal is to use your own branded domain, you don't need to self-host. ## Updating Your Project Once a custom domain is connected, you can continue improving your application. For example: ```text theme={null} yourdomain.com ↓ Current Version ``` You make changes: ```text theme={null} AIWA ↓ Build ↓ Preview ↓ Test ↓ Publish ``` Then the updated version becomes available through the same custom domain. You don't need to reconnect the domain every time you publish an update. ## SSL and HTTPS Your production application should be accessed securely over HTTPS. Once your domain is correctly connected and activated, AIWA's hosting infrastructure handles the secure connection for the published application. Users should be able to access your project through an address such as: ```text theme={null} https://yourcompany.com ``` Domain verification and secure certificate activation may require the DNS configuration to be fully propagated first. If your records are correct but the certificate is slow to arrive, AIWA automatically asks for it to be issued again. ## Using www You may want visitors to access: ```text theme={null} www.yourcompany.com ``` instead of, or alongside: ```text theme={null} yourcompany.com ``` AIWA recommends connecting the `www` address. Connecting the bare root domain needs a DNS method your provider supports at the root, such as ALIAS, ANAME, or CNAME flattening, and an email-record check. You'll find these under **Advanced apex setup**. If you want visitors who type `yourcompany.com` to reach `www.yourcompany.com`, set up a redirect at your DNS provider. Many providers offer this as a "URL redirect" or "forwarding" option. ## Common Problems ### Domain stays pending If the domain remains pending, check: * The DNS records match AIWA exactly * You're editing the correct domain * The hostname is correct * No characters were accidentally added * DNS has had enough time to propagate ### Domain verification fails Compare the record AIWA requested with the record currently configured at your DNS provider. Pay particular attention to: * Type * Name / Host * Value / Target A small difference can prevent verification. ### My domain still shows my old website Your DNS may still point to the previous hosting provider, or the updated record may not have propagated yet. Check the records for the specific hostname you're trying to connect. ### Subdomain doesn't work For example: ```text theme={null} app.example.com ``` doesn't work while: ```text theme={null} example.com ``` does. These are different hostnames and may require different DNS configuration. Make sure you've configured the exact subdomain entered in AIWA. ### Domain works without www but not with www `example.com` and `www.example.com` are separate hostnames from a DNS perspective. Check whether both have been configured according to your intended setup. ### I changed DNS but nothing happened DNS updates aren't always immediate. First verify that the record matches the values AIWA provided, then allow time for propagation. ### My email stopped working If this happened immediately after changing DNS, you may have accidentally modified records used for email. Don't remove records such as mail-related MX records unless you specifically intend to change your email provider. Restore the appropriate email DNS configuration through your provider if necessary. Use **Check email records** in the Domains section to compare your current records with the snapshot AIWA saved before you connected. ### Still stuck? Use the support option in the Domains section and choose **Email DNS concerns** or **Website connection**. Your domain details are sent along with the request. See also [Domain not connecting](/troubleshooting/domain-not-connecting). ## Debugging a Custom Domain A useful support or Debug Mode report looks like: > Domain: app.example.com > > AIWA Status: Pending Verification > > DNS Provider: \[Provider] > > Record Type: CNAME > > Host: app > > Expected Target: \[VALUE SHOWN BY AIWA] > > Current Target: \[VALUE IN DNS] > > The AIWA live URL works correctly, but the custom domain doesn't. > > Help me identify the domain configuration issue. DNS records are generally intended to be public, but don't include passwords, API keys, registrar login details, or other account credentials when asking for help. ## Test After Connecting Your Domain Once AIWA shows the domain as active, open it and test the application. Check: * Homepage loads * HTTPS works * Navigation works * Authentication works * Forms work * Images load * API functionality works * Integrations work * Mobile layout works * Redirects behave correctly * www/root domain behavior is correct Don't stop testing simply because the domain resolves. ## A Good Domain Setup Workflow The complete process is: ```text theme={null} PUBLISH PROJECT ↓ ADD CUSTOM DOMAIN ↓ COPY AIWA DNS RECORDS ↓ UPDATE DNS PROVIDER ↓ WAIT FOR PROPAGATION ↓ VERIFY DOMAIN ↓ TEST ↓ LAUNCH ``` Once connected, the domain becomes the branded gateway to your AIWA application. ## Your Project. Your Brand. AIWA handles the application and hosting. Your users see your brand. ```text theme={null} AIWA ↓ Your Application ↓ Your Domain ↓ Your Customers ``` This makes custom domains particularly useful for businesses, SaaS products, agencies, client projects, and production applications. ## Next: Version History & Restore Next, we'll cover Version History & Restore. This is important because building software is iterative, and sometimes a change doesn't work the way you expected. We'll cover: * What versions are * How AIWA tracks project changes * Viewing previous versions * Restoring an earlier version * When you should restore vs ask AIWA to fix something * Protecting working functionality while iterating View project versions and restore a previous version when needed. # Publishing to a Live URL Source: https://docs.aiwa.codes/publishing/live-url Publish your AIWA project to a live URL: preview your work, test the production build, and share it with customers or your team. Building your application is only part of the process. When you're ready to share your project with customers, teammates, testers, or the public, AIWA lets you publish it to a live URL. You don't need to configure a server or manually deploy your application just to get it online. **Build with AIWA. Preview your work. Publish when you're ready.** ## Preview vs Published While you're building with AIWA, you can preview your application and see your changes as you work. Your published application is the live version that other people can access. Think of it like this: ```text theme={null} BUILD ↓ PREVIEW ↓ REVIEW ↓ PUBLISH ↓ LIVE APPLICATION ``` You can continue working on your project after it has been published. Publishing isn't the end of development. ## Before You Publish Before publishing your project, take a moment to review the application. Check important areas such as: * Navigation * Forms * Authentication * Mobile responsiveness * Database functionality * Images and media * External integrations * Payments, if applicable * Permissions * Error states * Important user workflows Don't only check whether the homepage looks good. Test the application the way a real user would use it. ## Publish Your Project When you're ready, use the Publish option inside your AIWA project. AIWA Publish Button AIWA will prepare your application and deploy it. AIWA Publishing Once publishing is complete, your project will have a live URL that you can open and share. Conceptually: ```text theme={null} AIWA Project ↓ Publish ↓ Deployment ↓ Live URL ``` ## Your AIWA Live URL After publishing, AIWA provides a live URL for your application. You can use this URL to: * Open your live application * Share it with customers * Send it to teammates * Test the production experience * Collect feedback * Demonstrate your project * Launch your product AIWA Published Url AIWA provides hosting for your published projects, so you can launch directly from AIWA without setting up separate hosting infrastructure. ### Choosing your address Your live URL looks like this: ```text theme={null} your-project.aiwacodes.com ``` You choose the first part when you publish. It must be 3 to 63 characters long and use only lowercase letters, numbers, and hyphens. A few names, such as `www`, `app`, and `admin`, are reserved. ### Who can see it When you publish, you choose who can open the live site: | Option | Who can view | Plan | | - | - | - | | **Public** | Anyone with the link | Every plan | | **Only your workspace** | People in your workspace | Agency and above | | **Only selected members** | The people you choose | Agency and above | ### Ready for search engines Every published site gets the basics search engines and social networks look for, without any setup: * A page title and description * Preview cards for when your link is shared on social media or in messages * A `robots.txt` file and a `sitemap.xml` file, so search engines can find your pages You can edit the title, description, and sharing details in **Control Panel → SEO**. ### The AIWA badge Sites published on the free Launchpad plan show a small **Made with AIWA** badge. Upgrading to Solo or above removes it. ## Open Your Published Application After deployment completes, open the live URL. Don't assume that a successful deployment means every part of the application works perfectly. Test the actual published version. For example: ```text theme={null} Publish ↓ Open Live URL ↓ Test Application ↓ Everything Works? ↙ ↘ Yes No ↓ ↓ Share Fix ``` ## Test the Live Version Your published application should be tested separately from the editor preview. Try important workflows such as: **Navigation** Open different pages and verify that links work correctly. **Authentication** If your application requires accounts, test: * Sign up * Sign in * Sign out * Protected pages **Forms** Submit real test data and confirm that it reaches the correct destination. **Database** Create, update, retrieve, and delete test records where appropriate. **Integrations** Test any external services you've connected. For example: * Stripe * Resend * Twilio * Cloudinary * OpenAI * Calendly * Google services **Responsive design** Open the live application on both desktop and mobile. ## Publishing a Website Publishing isn't limited to complex applications. You can also publish websites built with AIWA. For example: > Build a professional website for a construction company with Home, About, Services, Projects, Testimonials, and Contact pages. Once you're happy with the result: ```text theme={null} Construction Website ↓ Review ↓ Publish ↓ Live Website ``` You can then share the URL or connect a custom domain. ## Publishing a Web Application The same process applies to more advanced products. For example: > Build a CRM where sales representatives can manage leads, contacts, deals, tasks, and follow-ups. Your application may include: * Authentication * Database * Dashboard * CRM * Integrations * Permissions AIWA handles publishing the application so users can access it online. ## Continue Building After Publishing Publishing doesn't lock your project. You can continue working with AIWA. For example, your first version might include: * Website * Contact Form * Customer Accounts Later you might tell AIWA: > Add appointment scheduling. Then: > Add customer subscriptions. Then: > Add an admin dashboard. Then: > Add an AI customer support assistant. Your application can continue evolving. This connects directly to the principle we introduced in What is AIWA: **Your first prompt is only the beginning.** ## Updating a Published Project Suppose your application is already live and you ask AIWA to make changes. For example: > Add a Pricing page and include it in the main navigation. You can review the updated application before making the new version live. The workflow remains: ```text theme={null} LIVE APPLICATION ↓ Continue Building ↓ Make Changes ↓ Preview ↓ Review ↓ Publish ↓ UPDATED LIVE APPLICATION ``` This allows your product to evolve without rebuilding everything from scratch. ## Don't Publish Every Change Immediately For small visual changes, publishing quickly may be fine. For larger changes, review them first. This is especially important when modifying: * Authentication * Payments * Database structures * User permissions * Integrations * Important customer workflows * Existing production data A better workflow is: ```text theme={null} CHANGE ↓ PREVIEW ↓ TEST ↓ PUBLISH ``` rather than: ```text theme={null} CHANGE ↓ PUBLISH IMMEDIATELY ``` ## Share Your Live URL Once your application is live, you can share the published URL with other people. For example: ```text theme={null} Your Project ↓ Publish ↓ Live URL ↓ Customers Team Testers Clients ``` This can be useful even before connecting your final custom domain. You might use the AIWA-provided URL for testing and review, then connect your branded domain when you're ready for the public launch. ## Custom Domains Your AIWA live URL doesn't have to be the final address customers use. Eligible plans can connect a custom domain. For example: ```text theme={null} AIWA Live URL ↓ yourcompany.com ``` or: ```text theme={null} app.yourcompany.com ``` We'll cover the complete custom-domain setup later in this section. ## Hosting Your Project Elsewhere AIWA provides hosting for published projects. If you prefer to use your own infrastructure, you can export your project and deploy it separately. For example: ```text theme={null} AIWA ↓ Export Project ↓ Your Infrastructure ↓ VPS / Hosting Environment ``` You can also use a GitHub-based workflow: ```text theme={null} AIWA ↓ Export to GitHub ↓ Your Repository ↓ Your Deployment Infrastructure ``` Using your own hosting infrastructure is different from publishing directly through AIWA. When self-hosting, you're responsible for configuring and maintaining your deployment environment. ## Common Problems ### Publishing takes longer than expected Wait for the deployment process to finish before repeatedly attempting to publish again. If it appears stuck, check whether AIWA displays an error or deployment status. ### The live URL doesn't open Confirm that publishing completed successfully. If the deployment failed, use the error information provided by AIWA to troubleshoot the problem. ### Preview works but published app doesn't This is particularly useful information for Debug Mode. Tell AIWA: > The application works correctly in Preview, but the published version fails when I open the live URL. Debug the production issue without changing the current design. Then provide the specific error or behavior. ### My latest changes aren't live Confirm that you published the updated version after making your changes. Changes you're previewing while building aren't necessarily the same thing as the currently published version. ### An integration doesn't work after publishing Tell AIWA which integration fails and whether it works in Preview. For example: > Stripe works during testing in Preview, but checkout fails on the published application. Debug the production Stripe configuration without changing the checkout interface. That gives AIWA much more useful context than: > Stripe doesn't work. ## Debugging a Published Project A strong Debug Mode request might look like: > Expected: Users should be able to submit the contact form on the published website. > > Actual: The form works in Preview, but submitting it on the live URL produces an error. > > Everything else on the published site works. > > Error: \[PASTE ERROR IF AVAILABLE] > > Debug the published contact form without changing its current design. The distinction between Preview and Published is important. ## Before Sharing Your Project Use this quick launch checklist: * Homepage loads * Navigation works * Mobile layout works * Forms submit * Authentication works * Database actions work * Images load * Integrations work * Permissions are correct * Important workflows are tested * No test content remains * No sensitive credentials are exposed * Live URL works Then share your application. ## From Build to Live The complete AIWA workflow now looks like: ```text theme={null} IDEA ↓ PLAN ↓ BUILD ↓ PREVIEW ↓ TEST ↓ PUBLISH ↓ LIVE URL ↓ LEARN ↓ IMPROVE ↓ PUBLISH AGAIN ``` Publishing isn't the finish line. It's the point where your application starts interacting with real users. From there, you can continue working with AIWA to improve it. ## Next: One-Click Deployment Now that you understand what publishing means, the next page will look more closely at AIWA's deployment process. We'll cover: * What happens when you deploy * One-click deployment * Deployment status * Updating an existing deployment * What to do when deployment fails See how AIWA handles deployment in one click. # One-Click Deployment Source: https://docs.aiwa.codes/publishing/one-click-deployment Deploy AIWA projects with a single click. Understand deployment status, updates, debugging, and how AIWA hosting handles it for you. AIWA lets you take the application you've built and deploy it without manually configuring traditional hosting infrastructure. When your project is ready, you can deploy it directly from AIWA and make it accessible online. You don't need to manually: * Configure a web server * Upload application files * Set up a traditional hosting account * Configure deployment pipelines just to launch * Transfer files through FTP * Build your own deployment system **Build your application. Click Publish. AIWA handles the deployment.** ## What Is Deployment? Deployment is the process of taking the application you've built and making it available in a live environment. While building, you work with your project inside AIWA. Deployment takes that project and makes it accessible through a live URL. ```text theme={null} AIWA PROJECT ↓ BUILD ↓ DEPLOY ↓ LIVE APPLICATION ``` AIWA handles this process for you. ## Publishing vs Deployment You'll often hear the words publish and deploy used together. In AIWA, you can think about them like this: **Publish** is the action you take. **Deployment** is the process that gets your application online. For example: ```text theme={null} You Click Publish ↓ AIWA Starts Deployment ↓ Application Prepared ↓ Application Goes Live ↓ Live URL Available ``` You don't need to manage the underlying deployment infrastructure yourself. ## Deploy Your Project When you're ready to make your application live, click Publish inside your AIWA project. AIWA Publish Button AIWA begins preparing and deploying your application. You'll see the deployment process while AIWA gets your project ready. AIWA Publishing Once deployment succeeds, your application becomes available online. ## Your Live Application After deployment completes, AIWA provides access to your live application. AIWA Published Url Open the live application and test it before sharing it with customers. AIWA includes hosting for projects published directly through the platform. You don't need to purchase separate hosting just to make an AIWA project available online. ## What AIWA Handles Traditional deployment can involve several technical steps. A developer may need to deal with things such as: ```text theme={null} Application ↓ Build Process ↓ Server ↓ Hosting Configuration ↓ Deployment ↓ Domain ``` AIWA simplifies this into: ```text theme={null} Application ↓ Publish ↓ Live ``` The goal is to let you focus on the product you're building rather than the mechanics of getting it online. ## You Can Keep Building Deploying your project doesn't mean development stops. Suppose you launch a booking application today. Version one might include: * Landing Page * Services * Booking Form * Customer Accounts A few weeks later, you might ask AIWA: > Add recurring appointments and allow customers to manage their bookings from their dashboard. You can build and review those changes before updating the live application. ## Updating an Existing Deployment When your project is already live, you don't need to create an entirely new application every time something changes. The workflow is: ```text theme={null} LIVE APPLICATION ↓ Make Changes ↓ Preview ↓ Test ↓ Publish ↓ UPDATED APPLICATION ``` For example: > Add a Testimonials section to the homepage. AIWA can make the change while you continue working on the same project. Once you're satisfied with the result, publish the updated version. ## Review Before Redeploying Just because deployment is easy doesn't mean every change should immediately go live. For significant updates, use: ```text theme={null} BUILD ↓ PREVIEW ↓ TEST ↓ PUBLISH ``` This is especially important when changing: * Authentication * Database structures * Payments * User permissions * APIs * Integrations * Important workflows * Existing customer functionality Always test important changes before updating an application being used by real customers. ## Small Changes vs Major Changes Not every update carries the same risk. Changing: > Make the hero headline larger. is very different from: > Change how subscription payments and user access are handled. For simple visual changes, testing may be quick. For major functional changes, test the complete workflow before deploying. ## Deployment Status During deployment, AIWA may show the current deployment state. Depending on the state of the project, you may see that deployment is: ```text theme={null} Preparing Deploying Successful Failed ``` Wait until deployment completes before assuming the new version is available. If deployment succeeds, open the live application and verify it. AIWA Publishing If deployment fails, investigate the error before repeatedly trying to deploy again. ## When Deployment Fails Sometimes a project may fail to deploy. A deployment failure doesn't necessarily mean your entire project is broken. The issue could be related to: * Build errors * Application code * Configuration * Dependencies * Environment requirements * External integrations * Recent changes Start by checking any error information AIWA provides. AIWA reads the build output for you and tells you, in plain language, which kind of failure it was: | What AIWA says | What it means | What to do | | - | - | - | | **Your app's code didn't compile** | The production build is stricter than the preview and found an error in your app | Click **Fix it**. AIWA finds the file and repairs it, then you publish again | | **Build servers had a hiccup**, **We hit a snag on our side**, or **The build ran long and was stopped** | Something went wrong on AIWA's build infrastructure, not in your app | Click **Retry deploy**. A fresh build almost always completes | | **There are no saved files to deploy** | Your project has no saved files yet, even if the preview looks fine | Restore a version from version history, or make one change in chat, then publish again | The raw build log stays available under **Technical details** if you or a developer want to see it. If a deploy fails more than once, a **Nudge support** button appears. It sends the failure to the AIWA support team with the details attached, so you don't need to copy anything. You'll see **Support has been notified** once a ticket is open. ## Use Debug Mode If deployment fails, Debug Mode can help investigate the problem. For example: > Expected: The project should deploy successfully when I click Publish. > > Actual: Deployment starts but fails before the application goes live. > > The project works correctly in Preview. > > Error: \[PASTE DEPLOYMENT ERROR] > > Identify the cause of the deployment failure and fix it without changing the current application design or functionality unnecessarily. Providing the actual error is much more useful than simply saying: > Deployment doesn't work. ## Preview Works, Deployment Fails This is an important distinction to tell AIWA. For example: > The application works correctly in Preview, but deployment fails when I click Publish. Then include the deployment error. This helps AIWA focus on the difference between the development/preview environment and the deployed environment. ## Deployment Succeeds but the App Doesn't Work A successful deployment doesn't automatically guarantee that every application workflow is functioning correctly. For example: ```text theme={null} Deployment ↓ Successful ↓ Website Opens ↓ Login Fails ``` In this situation, deployment itself worked. The problem is with a feature in the live application. Tell AIWA exactly what works and what doesn't. For example: > Deployment succeeds and the homepage loads correctly, but users can't sign in on the published application. Authentication works in Preview. Debug the production authentication issue. ## Test After Every Important Deployment After publishing a significant update, test the live application. Check the most important workflows. For example: **SaaS application** Test: * Sign up * Login * Dashboard * Core feature * Billing * Account settings **E-commerce application** Test: * Products * Cart * Checkout * Payment * Order confirmation **Booking application** Test: * Service selection * Date selection * Booking * Confirmation * Notifications **Website** Test: * Navigation * Forms * Links * Mobile layout * Calls to action Focus on the workflows that would matter most if they stopped working. ## Deploying Client Projects If you're using AIWA for client work, the same deployment workflow applies. For example: ```text theme={null} Build Client Project ↓ Preview ↓ Client Review ↓ Changes ↓ Final Approval ↓ Publish ↓ Live ``` You can use the AIWA-provided live URL or connect the client's custom domain when you're ready. ## AIWA Hosting Projects published directly through AIWA are hosted for you. That means you can go from: ```text theme={null} IDEA ↓ AIWA ↓ APPLICATION ↓ PUBLISH ↓ LIVE ``` without separately purchasing and configuring hosting for each project. This is particularly useful when you're rapidly launching: * Landing pages * Business websites * Internal tools * MVPs * SaaS products * Client applications * Prototypes ## Using Your Own Hosting You aren't required to use AIWA hosting if your workflow requires your own infrastructure. You can export your project and deploy it yourself. One option is: ```text theme={null} AIWA ↓ Export Project ↓ Your VPS ``` Another is: ```text theme={null} AIWA ↓ Export to GitHub ↓ Your Repository ↓ Your Deployment Workflow ↓ Your Infrastructure ``` When you deploy outside AIWA, you're responsible for configuring and maintaining your own hosting environment, deployment process, infrastructure, and related services. ## AIWA Hosting vs Self-Hosting The main difference is responsibility. **AIWA Hosting** AIWA handles the deployment infrastructure for the project. You: ```text theme={null} Build → Publish → Live ``` **Self-Hosting** You take the exported project and manage deployment yourself. ```text theme={null} Build ↓ Export ↓ Configure Infrastructure ↓ Deploy ↓ Maintain ``` Self-hosting can give technical teams more control, while AIWA hosting provides the simpler path to getting a project online. ## Deployment and Custom Domains Once your project is deployed, you may want users to access it through your own domain. Instead of an AIWA-provided project URL, you might use: ```text theme={null} yourcompany.com ``` or: ```text theme={null} app.yourcompany.com ``` Connecting a domain doesn't mean you have to move the application away from AIWA hosting. The domain simply becomes the address users use to access your deployed project. We'll cover this on the next page. ## Common Problems ### Deployment is stuck If deployment remains in progress for an unusually long time, check whether AIWA provides an error or status information. Avoid repeatedly triggering additional deployments while another deployment is still processing. ### Deployment failed If AIWA offers **Fix it**, use it. Otherwise retry once, and use **Nudge support** if it fails again. For anything else, copy the error information and use Debug Mode. Tell AIWA whether the project works correctly in Preview. ### My changes aren't appearing Make sure the latest version was actually published. If you've made changes but haven't published again, the live application may still be running the previous version. ### The live application is different from Preview Tell AIWA exactly what differs. For example: > The dashboard layout works correctly in Preview, but the sidebar doesn't appear on the deployed application. Specific differences make debugging easier. ### A connector stopped working after deployment Identify the connector and describe whether it works in Preview. For example: > Resend works in Preview, but emails aren't being sent from the deployed application. This gives AIWA a much narrower problem to investigate. ## A Good Deployment Debug Prompt When reporting deployment problems, include: * Expected behavior * Actual behavior * Whether Preview works * Deployment status * Error message * Recent changes For example: > Expected: The application should deploy and open normally. > > Actual: Deployment fails during the publishing process. > > Preview: The complete application works in Preview. > > Recent Change: I added the Stripe checkout workflow. > > Error: \[PASTE ERROR] > > Find the cause of the deployment failure and fix it without changing unrelated functionality. ## Deployment Checklist Before deploying an important update: * Review your latest changes * Test in Preview * Test authentication * Test forms * Test database operations * Test integrations * Test important permissions * Check mobile layouts * Remove test content * Check for exposed secrets * Publish * Wait for deployment to complete * Open the live URL * Test critical workflows again You're now ready to share the updated application. ## One Click From Build to Live AIWA is designed to reduce the distance between creating software and putting it in front of users. ```text theme={null} BUILD ↓ REVIEW ↓ PUBLISH ↓ DEPLOY ↓ LIVE ``` You can then continue improving the application and deploy new versions as your product evolves. ## Next: Custom Domains Your application is live. Now it's time to give it your own address. On the next page, we'll cover Custom Domains, including: * Connecting your domain * Using a root domain * Using a subdomain * DNS configuration * Domain verification * Troubleshooting DNS * Client domains * What happens when you update your project Connect your own domain to your published AIWA project. # Production vs Development Source: https://docs.aiwa.codes/publishing/production-vs-development Understand development, preview, and production in AIWA. Test authentication, payments, and connectors safely before customers see changes. When building with AIWA, you'll work with your application in different stages. While you're creating, modifying, and testing your project, you're working on the application before those changes are made available to your users. Once you publish the project, users access the production version of your application. Understanding this distinction becomes increasingly important as your application gains real users, customer data, payments, and integrations. **Build and test your changes first. Publish them when they're ready for your users.** ## What Is Development? Development is where you're actively building and improving your application. You might ask AIWA to: * Add a feature * Redesign a page * Fix an issue * Modify a workflow * Connect an integration * Change application logic * Improve the user experience During this process, you can review your changes before deciding whether they're ready to go live. Think of development as your working environment. ```text theme={null} YOUR IDEA ↓ AIWA ↓ BUILD ↓ PREVIEW ↓ TEST ``` You're still shaping the product. ## What Is Production? Production is the version of your application being used by real users. For example, if you've published: ```text theme={null} app.yourcompany.com ``` and your customers are signing in and using it, that's your production application. Production may contain real: * Users * Customer accounts * Payments * Orders * Projects * Bookings * Messages * Files * Business data Changes to a production application should therefore be treated more carefully than changes to an early prototype. ## Preview vs Live One of the easiest ways to understand the difference is: **Preview** What you're currently reviewing while building. **Live** What your users access after you've published. ```text theme={null} AIWA ↓ BUILD ↓ PREVIEW ↓ Are You Happy? ↓ PUBLISH ↓ LIVE APPLICATION ``` AIWA Publish Button This gives you an opportunity to inspect your work before making it available to users. ## Your Live Application Doesn't Stop You From Building Once you've published a project, you can continue improving it. Suppose Version 1 contains: * Landing Page * Authentication * Dashboard * Projects Your customers begin using it. You can then return to AIWA and say: > Add team collaboration so workspace owners can invite other users to their projects. You can build and review the new functionality before publishing the update. Conceptually: ```text theme={null} CURRENT LIVE VERSION ↓ Continue Building ↓ New Changes ↓ Preview ↓ Test ↓ Publish ↓ UPDATED LIVE VERSION ``` Your product can continue evolving after launch. ## Don't Use Real Users as Your Test Environment Once customers are using your application, avoid publishing major changes without testing them first. For example, imagine you change: > How subscription permissions are calculated. If you immediately publish without testing, you could accidentally prevent paying customers from accessing their accounts. Instead: ```text theme={null} CHANGE ↓ PREVIEW ↓ TEST ↓ VERIFY ↓ PUBLISH ``` This becomes increasingly important as your application grows. ## Test the Complete Workflow Don't only test the page you changed. Think about what the change affects. Suppose you modify your signup experience. Don't stop after confirming that the signup page looks correct. Test: ```text theme={null} Signup ↓ Account Created ↓ Authentication ↓ Onboarding ↓ Dashboard ``` A change at the beginning of a workflow can affect everything that comes afterward. ## Test Data vs Real Data During development, you may create sample information to test your application. For example: ```text theme={null} Customer: John Test Company: Acme Demo Order: #TEST-001 ``` That's useful while developing. But your production application may contain actual customer information. Before launching, remove unnecessary placeholder or demo content that shouldn't appear to real users. Be especially careful when testing actions that modify or delete data in an application already being used by real customers. ## Development Data and Production Data The distinction between your application version and its data is important. Your project may evolve through different versions while the database contains persistent information such as: * Users * Customers * Orders * Projects * Bookings * Subscriptions Don't assume that changing or restoring an application version automatically resets its database data. As covered in Version History & Automatic Restore, application recovery and database recovery are separate concepts. ## Test Authentication Carefully Authentication is one of the most important areas to test before publishing changes. If you modify: * Signup * Login * Password handling * Google authentication * Protected pages * User roles * Permissions test the entire authentication experience. For example: ```text theme={null} New User ↓ Sign Up ↓ Account Created ↓ Login ↓ Correct Dashboard ``` Then test an existing user. ```text theme={null} Existing User ↓ Login ↓ Existing Data Available ``` Don't only test with your administrator account. ## Test User Roles If your application supports different roles, test each one. For example: * Owner * Admin * Member * Customer A feature working correctly for an Owner doesn't necessarily mean it works correctly for a Customer. Check that each user: * Sees the correct pages * Has the correct permissions * Can perform allowed actions * Cannot perform restricted actions * Can only access appropriate data ## Test Payments Before Going Live Payment workflows deserve extra attention. If you're using Stripe, your development workflow should include testing before processing real transactions. For example: ```text theme={null} Choose Plan ↓ Checkout ↓ Payment ↓ Subscription Created ↓ Correct Access Granted ``` Don't only test whether the checkout page opens. Verify what happens after payment. Does the application: * Recognize the payment? * Update the customer? * Activate the correct plan? * Unlock the correct features? * Handle failed payments? * Handle cancellations? For payment-related changes, test the complete billing workflow before making the implementation available to customers. ## Test External Connectors If your application uses connectors, test them as part of your production checklist. For example: **Resend** Does the email actually arrive? **Twilio** Does the intended message get sent? **Cloudinary** Do uploaded images appear correctly? **Stripe** Does payment update the application correctly? **Google Calendar** Is the correct event created? **Google Meet** Is the meeting link available where expected? A successful application build doesn't guarantee every external service behaves as intended. ## Protect Secrets Never place sensitive credentials directly into publicly accessible application code or interfaces. This includes: * API keys * Secret keys * Database credentials * Access tokens * Passwords * Private service credentials Use AIWA's appropriate connector or secure configuration mechanism when credentials are required. Never test whether a secret is hidden by simply publishing it and checking the page. Credentials should be handled securely from the beginning. ## Development Credentials vs Production Credentials Some services provide separate testing and production environments. Payments are a common example. You might use: ```text theme={null} Development → Stripe Test Mode ``` and later: ```text theme={null} Production → Stripe Live Mode ``` Don't accidentally launch a production application with test configuration when real transactions are expected. Likewise, don't accidentally perform development testing against live systems when that could trigger real charges, messages, emails, or customer actions. ## Be Careful With Destructive Actions Some application actions are difficult or impossible to undo. Examples include: * Deleting customer records * Cancelling subscriptions * Removing files * Deleting projects * Changing permissions * Sending bulk communications Test these workflows carefully. For important destructive actions, consider confirmation interfaces such as: ```text theme={null} Delete Project? This action cannot be undone. [Cancel] [Delete Project] ``` You can ask AIWA: > Add a confirmation step before permanently deleting a project. Make it clear that the action cannot be undone. ## Development Emails and Messages Be careful when testing applications that send communication. For example, if your database contains 5,000 real customers, you don't want a development test to accidentally trigger: ```text theme={null} 5,000 emails ``` or: ```text theme={null} 5,000 SMS messages ``` When developing messaging workflows, use controlled test recipients where appropriate. Then verify the automation before allowing it to operate against real customer data. ## Making a Small Production Change Suppose your application is live and you want to change: > Change the homepage headline from "Build Faster" to "Build Your Next Product With AI." This is relatively low risk. Your workflow might simply be: ```text theme={null} Change ↓ Preview ↓ Check ↓ Publish ``` ## Making a Major Production Change Now imagine: > Replace the current authentication system, redesign onboarding, and change how user permissions work. That's significantly more consequential. Use: ```text theme={null} EXPLORE ↓ PLAN ↓ REVIEW ↓ BUILD ↓ TEST ↓ TEST DIFFERENT USERS ↓ PUBLISH ↓ VERIFY PRODUCTION ``` The size of your testing process should match the risk of the change. ## Use Plan Mode for Production Changes Plan Mode becomes especially valuable once your application is live. Instead of: > Change our subscription system. Try: > Analyze the existing subscription system and create a plan for adding annual billing without disrupting existing monthly subscribers. Don't make any changes yet. You can review the approach before AIWA modifies the application. This is particularly useful for: * Payments * Authentication * Database changes * Permissions * Major integrations * Existing customer workflows ## Tell AIWA What Must Not Change When modifying an established application, give AIWA boundaries. For example: > Add filtering to the customer table. Don't change the existing search, pagination, sorting, customer permissions, or table design. Or: > Add annual billing to the existing Stripe subscription workflow. Don't modify existing monthly subscriptions or customer access rules. This helps protect working functionality. ## Use Version History as Your Safety Net If a build starts consistently failing, AIWA attempts to diagnose and repair it. As covered on the previous page, if repeated repair attempts aren't successful, AIWA can automatically restore the project to a previous working version. The recovery process looks like: ```text theme={null} New Change ↓ Build Failure ↓ AIWA Attempts Repair ↓ Still Failing ↓ Additional Iteration ↓ Cannot Recover ↓ Previous Working Version ``` This helps prevent a failed build from becoming a dead end. However, version recovery doesn't replace proper production testing. ## After Publishing, Test Again A feature working in Preview doesn't mean you should skip testing the live application. After an important deployment: ```text theme={null} Publish ↓ Open Live URL ↓ Test Critical Workflows ↓ Everything Working? ↙ ↘ Yes No ↓ ↓ Done Debug ``` AIWA Published Url Test the production experience the same way your customers will use it. ## Preview Works but Production Doesn't This is useful information for AIWA. Don't simply say: > Login is broken. Instead: > Login works correctly in Preview, but after publishing, users can't sign in on the live application. The login request returns this error: \[ERROR]. Debug the production authentication issue without changing the current login interface. The distinction helps AIWA narrow down the problem. ## Production Debugging A strong Debug Mode request might look like: > Expected: Existing customers should be able to sign in and access their dashboard. > > Preview: Authentication works correctly. > > Production: The login form loads, but submitting valid credentials returns an error. > > Recent Change: We updated the onboarding workflow. > > Error: \[PASTE ERROR] > > Debug the production authentication issue without changing unrelated dashboard or onboarding functionality. Give AIWA as much context as possible about where the problem occurs. ## Production Checklist Before publishing an important update, check: * Preview works correctly * Navigation works * Mobile layouts work * Authentication works * Different user roles work * Permissions are correct * Database operations work * Forms work * Payments work * External connectors work * Error states are handled * Test content has been removed * Secrets aren't exposed * Destructive actions are protected * Critical customer workflows are tested After publishing: * Open the live application * Test the critical workflows again * Confirm the latest version is live ## Think in Environments A useful mental model is: ```text theme={null} BUILD ↓ DEVELOPMENT ↓ PREVIEW ↓ TEST ↓ PUBLISH ↓ PRODUCTION ↓ REAL USERS ↓ LEARN ↓ BUILD AGAIN ``` Production isn't the end of the AIWA workflow. It's where your application meets real users. Their feedback gives you new ideas, and you return to AIWA to continue evolving the product. ## From project to production You've now seen the whole path from a project in AIWA to a live application: ```text theme={null} AIWA PROJECT ↓ BUILD ↓ TEST ↓ PUBLISH ↓ CUSTOM DOMAIN ↓ PRODUCTION ``` ## Next: Mobile Export Next, we'll look at turning your project into a mobile app: * Mobile readiness scan * Export for Android (APK) * Submitting to the Play Store * Export for iOS * Submitting to the App Store Learn how AIWA can help you export your project as a mobile application. # Version History & Automatic Restore Source: https://docs.aiwa.codes/publishing/version-history AIWA tracks project versions and can automatically restore a working version when repeated build repairs fail during development. Building software is iterative. As you add features, change designs, connect services, and evolve your application, occasionally a new build may introduce a problem. AIWA is designed to help recover from these situations automatically. When a build fails, AIWA first attempts to understand and fix the problem. If the build continues failing after multiple repair attempts and AIWA determines that continuing isn't producing a working result, it can automatically restore the project to a previous working version. **AIWA doesn't just help you build. It also helps protect your project when a build goes wrong.** ## How AIWA Handles Failed Builds When AIWA encounters a problem while building your application, restoring the project isn't the first action. AIWA first attempts to fix the issue. The recovery process looks like this: ```text theme={null} BUILD ↓ Something Fails ↓ AIWA Diagnoses the Problem ↓ Attempts a Fix ↓ Tests Again ↓ Still Failing? ↙ ↘ No Yes ↓ ↓ Continue Iterate & Repair ↓ Still Can't Resolve? ↓ Restore Working Version ``` This gives AIWA an opportunity to repair the current build before falling back to an earlier state. ## AIWA Tries to Fix the Problem First Many development problems can be fixed without abandoning the current build. For example, AIWA may encounter an issue after: * Adding a new feature * Changing application logic * Updating a component * Connecting an integration * Modifying a workflow * Restructuring part of the application AIWA can analyze the failure and attempt to correct it. If the repair succeeds, development continues normally. You don't need to manually restore the project simply because one build attempt failed. ## Automatic Recovery Sometimes a build continues failing despite repeated attempts to fix it. Instead of allowing AIWA to continue indefinitely with a broken state, AIWA can fall back to a previous working version. Conceptually: ```text theme={null} Working Version ↓ New Change ↓ Build Fails ↓ AIWA Attempts Repair ↓ Repair Fails ↓ AIWA Tries Again ↓ Still Failing ↓ Automatic Restore ↓ Previous Working Version ``` This provides a recovery mechanism when the current implementation can't be repaired successfully. ## Why Automatic Restore Matters Imagine you have a working CRM. It includes: * Dashboard * Contacts * Leads * Deals * Tasks * Authentication * Database You ask AIWA: > Add an advanced reporting dashboard with revenue forecasting and pipeline analytics. During implementation, something goes wrong and the project stops building correctly. AIWA attempts to diagnose and repair the problem. If those attempts continue failing, AIWA can restore the project to the previous working state rather than leaving you with a consistently broken build. Your working CRM becomes the recovery point. ## Your Project Evolves Through Versions As you build, your application moves through different states. For example: ```text theme={null} Version 1 Landing Page ↓ Version 2 Authentication ↓ Version 3 Dashboard ↓ Version 4 CRM ↓ Version 5 Payments ↓ Version 6 New Feature ``` These previous states make it possible to recover when a later change introduces a problem that can't be resolved. ## Version History AIWA Version History AIWA's version history gives your project continuity as it evolves. You can use version history to understand how your application has changed over time and restore a previous version. | What AIWA keeps | For how long | | - | - | | Your most recent versions | The latest 50 | | Versions you bookmark | Always | | The version that's currently live | Always | Before a big change, bookmark the version you're happy with. Bookmarked versions are never cleared out, and you'll find them on the **Bookmarks** tab of the version history panel. This becomes especially valuable when you're making significant changes to an existing application. ## Automatic Restore vs Manual Restore There are two different reasons you might return to an earlier version. **Automatic Restore** AIWA may restore a previous working version when the current build repeatedly fails and repair attempts aren't resolving the problem. ```text theme={null} Build Failure ↓ Automatic Diagnosis ↓ Repair Attempts ↓ Still Failing ↓ Automatic Restore ``` This is a recovery mechanism. **Manual Restore** You may also want to return to an earlier version yourself. For example, perhaps the new version works technically, but you simply preferred the previous design. ```text theme={null} Working Version ↓ Major Redesign ↓ You Don't Like It ↓ Version History ↓ Restore Previous Version ``` This is a product decision rather than failure recovery. ## When AIWA Automatically Restores Automatic restoration is useful when the current build becomes consistently unsuccessful. For example: ```text theme={null} Attempt 1 Build Fails ↓ AIWA Fixes ↓ Attempt 2 Still Fails ↓ AIWA Investigates Again ↓ Attempt 3 Still Can't Produce Working Build ↓ Restore Previous Working Version ``` The purpose isn't to abandon a change at the first sign of trouble. The purpose is to prevent repeated unsuccessful iterations from leaving your project in an unusable state. ## What Happens After an Automatic Restore? When AIWA restores the project, you're returned to a previous working state. From there, you can continue building. You might approach the feature differently. For example, your original request was: > Completely rebuild the CRM dashboard, reporting system, navigation, filters, and analytics experience. After restoration, you might break the work into smaller steps: > First, add the revenue analytics cards to the existing dashboard. Keep everything else unchanged. Then review the result before moving on. This can make complex changes easier to implement safely. ## Failed Build Doesn't Mean Lost Project This is one of the important reasons AIWA maintains project versions. A failed iteration shouldn't automatically mean starting over. Think of your project as a sequence of working states: ```text theme={null} WORKING ↓ WORKING ↓ WORKING ↓ FAILED CHANGE ↓ REPAIR ATTEMPTS ↓ RECOVERY ↓ WORKING ``` AIWA can use that history to recover when necessary. ## You Can Still Use Debug Mode Automatic recovery doesn't replace Debug Mode. If your application builds successfully but a particular feature isn't behaving correctly, Debug Mode is often the better choice. For example: > The new search feature works, but pagination stopped working after the change. Fix pagination without removing search or changing the table design. The project itself isn't failing to build. There's simply a functional issue. In that situation: ```text theme={null} Application Builds ↓ Feature Has Problem ↓ Debug ↓ Fix Specific Issue ``` There's no reason to discard the entire iteration. ## Build Failure vs Functional Bug Understanding the difference is useful. **Build failure** The application can't successfully complete the build process. AIWA may need to: ```text theme={null} Diagnose ↓ Repair ↓ Retry ↓ Recover if necessary ``` **Functional bug** The application builds, but something doesn't behave correctly. For example: * Login works * Dashboard works * CRM works * Search works * Pagination broken Use Debug Mode to repair the specific problem. ## Automatic Restore Is the Last Resort AIWA doesn't need to revert every time something goes wrong. The preferred sequence is: 1. Detect 2. Understand 3. Fix 4. Retry 5. Validate 6. Restore if recovery isn't succeeding Restoration provides a safety net when repeated attempts to repair the current build aren't producing a working result. ## Example: Adding Payments Imagine your SaaS application is working correctly. You tell AIWA: > Add subscription billing with three plans and restrict features based on the user's subscription. AIWA begins implementing the feature. If the resulting build fails, AIWA first attempts to repair it. ```text theme={null} Working SaaS ↓ Add Billing ↓ Build Failure ↓ Diagnose ↓ Repair ↓ Retry ``` If the issue is fixed: ```text theme={null} Billing Added ↓ Continue Building ``` If repeated attempts fail: ```text theme={null} Repeated Failure ↓ Automatic Restore ↓ Previous Working SaaS ``` Your project has a path back to the working state. ## Example: Major Redesign Now consider a different scenario. You tell AIWA: > Completely redesign my dashboard. The redesign builds successfully. Nothing is technically broken. You simply don't like it. AIWA shouldn't automatically restore the previous version because there hasn't been a build failure. Instead, you can use version history to return to the design you preferred. ```text theme={null} Original Dashboard ↓ New Dashboard ↓ Build Successful ↓ You Prefer Original ↓ Version History ↓ Manual Restore ``` ## Use Plan Mode for Large Changes Automatic recovery gives you protection, but preventing unnecessary failures is even better. For significant changes, use Plan Mode before building. For example: > I want to restructure the entire authentication and onboarding system. Analyze the current implementation and create a plan first. Don't make any changes yet. Then: ```text theme={null} IDEA ↓ PLAN ↓ REVIEW ↓ BUILD ↓ VALIDATE ``` This is particularly useful for changes involving: * Authentication * Database architecture * Payments * Permissions * Large redesigns * Complex integrations * Major application workflows ## Make Complex Changes Incrementally Instead of: > Redesign the entire CRM, dashboard, billing, navigation, settings, and customer portal. Consider: ```text theme={null} Dashboard ↓ Review CRM ↓ Review Billing ↓ Review Customer Portal ↓ Review ``` Smaller iterations make problems easier to identify and repair. They also give your project clearer working states as it evolves. ## Protect Existing Functionality When requesting changes, tell AIWA what must remain untouched. For example: > Add advanced filtering to the customer table. Keep the existing search, pagination, sorting, customer editing, and table design working exactly as they do now. This gives AIWA clearer boundaries. It's particularly useful when working with mature applications that already contain many interconnected features. ## Version History and Published Applications Version history and publishing are related, but they're not the same thing. Your project may have: ```text theme={null} Project Version ↓ Preview ↓ Test ↓ Publish ↓ Live Application ``` When working on an application already being used by customers, review significant changes before publishing them. Automatic recovery protects the building process, but you should still test your application before pushing an important update live. ### Rolling back the live site Restoring a version changes what you're working on. It doesn't change what's live until you publish again. If a release causes problems for your users, the project owner can roll the live site back to an earlier deployment from **Control Panel → Releases**. Releases lists every deployment of the project, including failed ones, so you can see exactly what went live and when. ## What About My Database? Project version restoration and database recovery are different concepts. Your production database may contain: * Users * Customers * Orders * Payments * Projects * Messages * Bookings You should not assume that restoring an earlier project version restores your database to an earlier point in time. Version history is not a replacement for database backups or data recovery. Restoring application code and restoring production data are different operations. This distinction becomes especially important once your application has real users. ## What About Connectors? After a major restore, test any important integrations used by the application. For example: * Stripe * Resend * Twilio * Cloudinary * OpenAI * Google services If the restored version predates a workflow that depended on one of these connectors, that functionality may need to be reviewed. ## Common Questions ### AIWA keeps failing to build. What should I do? AIWA will attempt to diagnose and repair build problems during the development process. If the current build continues failing and AIWA can't resolve it after multiple iterations, it can restore the project to a previous working version. ### Will AIWA restore after every failed build? No. A failed build may be repairable. AIWA first attempts to fix the issue and continue the current build. Automatic restoration is the fallback when repeated repair attempts aren't succeeding. ### My application builds, but one feature is broken. Will AIWA restore it? A functional problem doesn't necessarily require restoration. Use Debug Mode and describe the specific issue so AIWA can attempt to repair it without discarding working changes. ### Can I return to an earlier version even if nothing failed? Yes. Version history can also be useful when you simply want to return to an earlier implementation or design. ### Does restoring a version restore my database? Don't treat project version history as a database backup system. Application versions and production data recovery are separate concerns. ## A Good Recovery Workflow The overall AIWA recovery process can be thought of as: ```text theme={null} NEW BUILD ↓ SUCCESS? ↙ ↘ YES NO ↓ ↓ Continue Diagnose ↓ Fix ↓ Retry ↓ Successful? ↙ ↘ YES NO ↓ ↓ Continue Iterate ↓ Still Failing? ↓ Automatic Restore ↓ Working Version ``` This allows AIWA to be persistent when problems are fixable without endlessly continuing down a failing path. ## Build With a Safety Net AIWA is designed for continuous product development. You can: ```text theme={null} BUILD ↓ ITERATE ↓ EXPERIMENT ↓ DEBUG ↓ RECOVER ↓ KEEP BUILDING ``` Version history provides the foundation. AIWA's automatic recovery process adds another layer by helping return your project to a working state when repeated build repairs aren't successful. Your application can keep evolving without every failed experiment becoming a dead end. ## Next: Production vs Development Next, we'll look at **Production vs Development**. We'll explain: * Development vs production * Preview vs live applications * Test data vs real customer data * Testing payments * Making changes to live applications safely * Protecting production users * What to test before publishing Understand the difference between development and production and how to keep users safe. # AIWA roadmap and what's coming Source: https://docs.aiwa.codes/reference/coming-soon Where to follow AIWA's public roadmap, vote on ideas and request features, plus what AIWA doesn't do yet. AIWA keeps a public roadmap so you can see what's being worked on and help decide what comes next. ## The public roadmap The roadmap at **[aiwa.codes/roadmap](https://aiwa.codes/roadmap)** is always the most up-to-date view. It has three columns: | Column | Meaning | | - | - | | Coming soon | Scoped and queued; next in line for the build team | | In progress | Being designed and built right now | | Live | Shipped and ready to use today | Some items are marked as **ideas**: things the team is exploring rather than committed to. Votes help an idea become a feature. ## Vote and request features On the roadmap you can: * Vote for the items you want most * Submit your own feature request * Follow updates as items move between columns To request an integration your app needs, see [Request a connector](/integrations/request-a-connector). ## What AIWA doesn't do yet So you can plan around it, here is what AIWA does **not** do today: * **Build and upload your iOS app for you.** AIWA gives you the App Store submission kit and a build configuration to run on your own account. You submit the app yourself. * **Several workspaces under one account.** Each account works in one workspace today. * **Referral credits.** * **Building through WhatsApp.** You can build from [Telegram](/agency/telegram) on the Agency plan. This list describes what isn't available today. It isn't a promise of what will ship or when; the public roadmap is the place for that. ## Next: Contacting support That's the end of the docs. If you can't find what you need, get in touch. How to reach the AIWA team. # AIWA credit cost table Source: https://docs.aiwa.codes/reference/credit-cost-table A quick lookup of AIWA credit prices for standalone actions. Builds and edits are charged by the work done. A one-glance lookup. For how charges work, see [Credit costs](/billing/credit-costs). | Action | Credits | | - | - | | Build, edit or repair | Depends on the work; shown after each request | | Explore question | 1 | | Brief | Free once a day, then 2 | | Generated image | 4 | | Stock photo | 0 | | Voice transcription | 2 | | Idea shuffle | 2 | | Mobile readiness scan | 0 (deep check: 2) | | Android APK | 10 | | Google Play kit | 5 | | App Store kit | 10 | | Brand logo (agency console) | 4 | | Brand accent or invitation copy (agency console) | 1 | | Publish, hosting, custom domain | 0 | Top-up credits cost \$0.10 each. ## Next: Coming Soon What AIWA doesn't do yet, and where to follow the roadmap. # AIWA glossary of terms Source: https://docs.aiwa.codes/reference/glossary Plain-English definitions of the terms used across AIWA: credits, plans, modes, Min and Max, the Brief, connectors, publishing, the agency console and more. A quick reference for the words you'll see in AIWA and in these docs. ## Accounts and billing **Workspace**: Your account's home for projects, team, credits and billing. Your plan applies to the whole workspace. **Owner**: The person who controls a workspace's plan, billing and team. **Credit**: The unit of AI work in AIWA. Building, editing, planning, images and repairs use credits. See [How credits work](/billing/how-credits-work). **Monthly credits**: The credits your plan gives you each cycle. They reset to your plan's amount at the start of every cycle. **Top-up credits**: Credits you buy on a paid plan, at \$0.10 each. They never expire. **Overdraft**: A one-time 20-credit cushion that lets a build finish if you run out halfway. It is repaid from your next monthly allowance. **Launchpad**: The free plan, with 80 credits a month and up to 5 projects. **Solo**: The plan for individual builders, with 200 credits a month, custom domains and code export. **Agency**: The plan for building with a team and for clients, with 1,000 credits a month, client review, the agency console and mobile app kits. **Enterprise**: Custom plans for larger organizations. **White Label**: A partner program for selling AIWA under your own brand. See [White Label](/white-label/overview). **Partner**: A business on the White Label program. ## Building **Project**: One website or app you build in AIWA. **Prompt**: What you type to tell AIWA what you want. **Build mode**: AIWA makes the changes you ask for straight away. **Plan mode**: AIWA writes a plan and specification for you to review before anything is built. **Explore mode**: Ask questions about your app without changing it. Costs 1 credit. **Debug mode**: Describe a problem and AIWA investigates and fixes it. **Brief**: A short interview in which AIWA asks you questions and writes a clear request before you build. One free per day. **Clarifying questions**: Questions AIWA asks when a request is too thin to build well, before any credits are spent. **AIWA Min / AIWA Max**: Two levels of effort. Min is faster; Max thinks more deeply about harder requests. Max is available on paid plans, which start on Max by default. **Project Memory**: What AIWA remembers about your project, such as decisions and preferences, so you don't repeat yourself. **Automatic repair**: When a build has an error, AIWA tries to fix it before showing you the result. **Remix**: Make your own copy of a shared project or template to build on. **Template**: A ready-made project in the gallery that you can start from. ## Connecting services **Connector**: A saved connection to an outside service, such as Stripe, PayPal or Resend, that your app can use. See [Integrations](/integrations/overview). **API key**: The credential a service gives you so AIWA can connect your app to it. **Test mode / live mode**: Test credentials let you try payments and messages safely. Live credentials work with real customers and money. ## Previewing and publishing **Preview**: The working version of your app inside AIWA, where you try changes before anyone else sees them. **Publish**: Put the current version of your app online. Publishing is free. **Live URL**: Your published app's address, such as `your-project.aiwacodes.com`. **Custom domain**: Your own address, such as `www.yourbusiness.com`, connected to a published app. Available on Solo and up. **Version history**: The list of earlier versions of your project, which you can restore. **Control Panel**: A project's management area, with sections for domains, SEO, people, releases, connectors and more. ## Mobile **Readiness scan**: A check of how ready your project is to become a mobile app. The standard scan is free. **APK**: An installable Android app file. **Release kit / submission kit**: The bundle of files you need to submit your app to Google Play or the App Store. ## Teams and clients **Editor**: A teammate who can build and change projects. **Viewer**: A teammate who can look but not change. **Admin**: A teammate who can help manage the workspace. **Client**: Someone you invite to review a project, leave comments and sign it off. Clients don't use a team seat. **Agency console**: The Agency plan's home for clients, team, usage, activity and branding. See [Agency console](/agency/console-overview). **Client portal**: The page where your client sees their project and leaves comments. **Pinned comment**: A comment attached to a particular spot on the page. **Hand-off**: Passing a finished, live project to your client, who can sign it off. ## Next: Plan & Tier Matrix Every AIWA feature across every plan. # AIWA plan and tier matrix Source: https://docs.aiwa.codes/reference/plan-tier-matrix One table showing every AIWA limit and feature across the Launchpad, Solo, Agency and Enterprise plans. Every limit and feature, by plan, in one table. For explanations, see [Plan inclusions](/billing/plan-inclusions). ✓ = included · – = not included | | Launchpad | Solo | Agency | Enterprise | | - | - | - | - | - | | **Price** | Free | \$20/mo or \$210/yr | \$149/mo or \$1,565/yr | Custom | | **Monthly credits** | 80 | 200 | 1,000 | Custom | | **Projects** | 5 | 100 | Unlimited | Unlimited | | **Team seats (including owner)** | 3 | 1 | 15 | Unlimited | | Extra editor seat | – | – | \$19/month | Custom | | Top-ups (\$0.10/credit) | – | ✓ | ✓ | ✓ | | Attachments per message | 5 | 10 | 10 | 10 | | AI images per project | 2 | 10 | 25 | 25 | | Stock photos per project | 7 | 20 | 50 | 50 | | AIWA Min | ✓ | ✓ | ✓ | ✓ | | AIWA Max | – | ✓ (default) | ✓ (default) | ✓ (default) | | Publish to a live URL | ✓ | ✓ | ✓ | ✓ | | "Made with AIWA" badge removed | – | ✓ | ✓ | ✓ | | Custom domains | – | ✓ | ✓ | ✓ | | Site analytics | – | ✓ | ✓ | ✓ | | Code export | – | ✓ | ✓ | ✓ | | GitHub sync | – | ✓ | ✓ | ✓ | | Restrict who can view a published site | – | – | ✓ | ✓ | | Invite viewers | ✓ | – | ✓ | ✓ | | Invite editors | – | – | ✓ | ✓ | | Invite clients | – | – | ✓ | ✓ | | Agency console | – | – | ✓ | ✓ | | Client portal and hand-off | – | – | ✓ | ✓ | | Build from Telegram | – | – | ✓ | ✓ | | Mobile readiness scan | ✓ | ✓ | ✓ | ✓ | | Android APK | – | – | ✓ | ✓ | | Google Play kit | – | – | ✓ | ✓ | | App Store kit | – | – | ✓ | ✓ | | Mobile source download | – | – | ✓ | ✓ | | SSO/SAML and audit log | – | – | – | By arrangement | Mobile builds and kits also need a readiness score of 80 or more. For White Label partner limits, see [White Label](/white-label/overview). ## Next: Credit Cost Table What each AIWA action costs. # Client Sharing & Review Source: https://docs.aiwa.codes/teams/client-sharing Invite clients to their AIWA project, show them the live site in a branded client portal, and collect their feedback without giving them access to the builder. When you build for a client, they need to see the work and tell you what they think. They don't need your builder, your prompts, your files or your bills. AIWA gives clients their own space: the **client portal**. A client sees the live site for their project, with a comment panel beside it, under your agency's name and logo. **Clients review the real site. Your team keeps the builder.** Inviting clients is available on the Agency and Enterprise plans. ## How Client Review Works ```text theme={null} BUILD WITH AIWA ↓ PUBLISH ↓ CLIENT OPENS THE PORTAL ↓ CLIENT COMMENTS ON THE LIVE SITE ↓ YOUR TEAM HANDLES THE COMMENTS ↓ PUBLISH AGAIN ``` Publishing is the release. There is no separate approval step and no review copy to manage: the client always sees what is live at the project's address. ## Invite a Client Use the **Clients** tab of the [agency console](/agency/console-overview), or the **People** tab of the project's Control Panel. Enter the client's e-mail address. You can add their company name, so the console groups clients by company. Choose the projects this client should see. They will never see any other project. Add an optional message. The invitation goes out under your agency's name. AIWA Client Sharing The invitation link names your agency, the project and the invited address before the client creates an account. The client signs up or signs in with that address and lands in the portal. Clients are free. They don't use a team seat and they never spend your credits. ## What the Client Sees In the portal, a client sees: * A list of their projects (if there is only one, it opens straight away) * The live site, shown in a frame * A comment panel beside it, where they write comments and read your replies If a project isn't published yet, the portal says so instead of showing a site. A client never sees: * The builder or your prompts * Files and code * Deploy details * Other team members or clients * Credits and spending Read more in [The Client Portal](/agency/client-portal). ## Publish Before You Share Because clients see the live site, publish the version you want them to review. A good rhythm is to publish at clear milestones: ```text theme={null} Milestone 1: Homepage and design direction Milestone 2: Main pages and content Milestone 3: Forms, bookings or payments Milestone 4: Final polish ``` Each milestone gives the client something focused to react to. Everything you publish is live at the project's address. If the site is already in use by real customers, test changes in the builder's preview before you publish them. ## Collecting Feedback Clients comment directly on the site. They can: * Click a spot on the page to drop a **pin** and comment on that exact element * Leave a comment about the whole site * Reply in a thread * Mark their own comment as done, or reopen it Your team is told by e-mail when a client comments, and the client is told when you reply. See [Commenting & Feedback](/teams/commenting) for the full workflow. ## Turn Feedback Into Clear AIWA Requests Client feedback is often short: > The booking section feels too busy. From the project's Control Panel, you can let AIWA handle a comment as it is, or add your own instructions first: > Simplify the booking section. Keep the date picker and the confirm button. Move the cancellation policy into a short note under the button. Keep the current colours. Good instructions say what to change, what to keep, and what to avoid. ## Don't Implement Every Request Automatically Some requests: * Conflict with each other * Change the scope of the project * Would break something already working * Need a conversation first Reply to the comment to ask a question, or dismiss it with a reply explaining why. You stay in control of what gets built. ## Multiple Client Stakeholders A client business may have several people who need to see the site: an owner, a marketing lead, an operations manager. Invite each of them as a Client on the project. They all see the same site and the same comments, so feedback stays in one place. If two people disagree, reply in the thread and ask them to agree on one direction before you build. ## Live Sites and Ongoing Work Many client projects keep going after launch. The same loop works for a live site: ```text theme={null} LIVE SITE ↓ CLIENT COMMENTS ↓ TEAM CHANGES IN THE BUILDER ↓ TEST IN PREVIEW ↓ PUBLISH ``` The client always comments on what is live, so feedback never refers to an old version. ## Handing the Site Over When the work is finished, you can send the client a formal **hand-off**. The client receives a summary of their site and is asked to sign it off. You can also give them a Traffic page and an Accounts page for their site. See [Client Hand-off & Sign-off](/agency/client-handoff). ## Removing a Client When a project ends, remove the client from it. You can tick **Let them know by e-mail** to send a short message, under your agency's brand, naming the projects they can no longer open. ## A Strong Agency Workflow ```text theme={null} CLIENT BRIEF ↓ BUILD WITH AIWA ↓ PUBLISH A MILESTONE ↓ INVITE THE CLIENT ↓ PINNED COMMENTS ON THE LIVE SITE ↓ HANDLE COMMENTS WITH AIWA ↓ PUBLISH AGAIN ↓ HAND OFF AND SIGN OFF ``` ## Next: Commenting & Feedback Next, we'll look at comments in detail: pins, threads, statuses, and how your team turns comments into changes. Pinned comments, threaded replies, and handling client feedback with AIWA. # Commenting & Feedback Source: https://docs.aiwa.codes/teams/commenting Pin comments to a spot on the live site, reply in threads, and turn client feedback into changes with AIWA from the project's Control Panel. Comments are how clients and your team talk about a site. A comment lives on the site itself. A client can point at the exact button, heading or image they mean, and your team can turn that comment straight into a change. **Feedback in context is feedback you can act on.** Client comments are available on the Agency and Enterprise plans, together with client invitations. ## Where Comments Happen Comments have two sides: | Who | Where | What they do | | - | - | - | | **Clients** | The [client portal](/agency/client-portal), beside the live site | Write comments, pin them, reply, mark their own comments done | | **Your team** | The **Comments** tab of the project's Control Panel, in the builder | Reply, let AIWA handle comments, dismiss and reopen | Your team can also open the client view to see the site exactly as the client does, and comment there too. Clients on the project get an e-mail about a team comment. ## Pinned Comments A pinned comment is attached to a spot on the page. In the client portal, switch to commenting. Click an element on the live site. A pin drops there and a bubble opens next to it. On a phone or tablet, tap to place a pin; dragging still scrolls the site. Type the comment in the bubble and send it. The comment appears in the panel with a number that matches the pin. You can also leave a comment about the whole site, without a pin. Use this for general feedback such as tone or overall colour. For a better view, open **focus mode**: the site goes full screen with the comment panel at its side. ### When the site changes Sites change after comments are written. A pin can show a short note: | Note | What it means | | - | - | | **This spot has changed** | The element the pin was on has moved or changed | | **Placed before the latest update** | The comment was written before the site was last published | | **Not visible at this width** | The pinned element is hidden at the current screen size | Each pinned thread has **Show on the site**, which scrolls to the pin. ## Threads and Replies Every comment starts a thread. * Your team replies from the Control Panel. The client reads the reply under their comment in the portal. * The client can reply back in the same thread. * The person who wrote a comment is e-mailed when someone replies to it. Keep the conversation about one issue in one thread. Start a new comment for a new issue. ## Comment Statuses | Status | Meaning | | - | - | | **Open** | New, waiting for your team | | **Being handled** | AIWA is building the change | | **Done** | The change has been built, or the client marked their comment done | | **Closed** | Your team dismissed the comment | Clients see "Being worked on" for comments your team is handling, and can mark their own comments done or reopen them. There is also a quick **Looks good** button in the portal for clients who are happy with what they see. ## Handling Comments With AIWA In the builder, open the project's Control Panel and go to **Comments**. For each open comment you can: * **Let AIWA handle it**: the comment becomes the build request as it is * **Add instructions first**: tell AIWA how to treat the comment, what to keep and what to avoid * **Reply**: answer or ask a question without building anything * **Dismiss**: close the comment, ideally with a reply explaining why **Handle all open comments** builds one request from every open comment, in the order the client wrote them. Pinned comments carry their place into the request, for example "On /pricing near 'Get started'", so AIWA knows where to make the change. When the build succeeds, the comments move to **Done**. Handling a comment builds the change in your project. It does not publish it. Check the preview, then publish so the client sees the change on the live site. ## Good Comments vs Vague Comments Share this with your clients. | Vague | Clear | | - | - | | "Make it better." | "The headline is hard to read on the photo. Can it be darker?" | | "Change this." | "Change 'Learn more' to 'Book a consultation'." | | "Doesn't work." | "I clicked Submit on the contact form and nothing happened." | A good comment says what is wrong and, if possible, what the client wants instead. ## Add Instructions When Feedback Is Short Client feedback is often brief: > The pricing section is confusing. Add instructions before letting AIWA build: > Simplify the pricing section. Keep the three plans. Put the monthly price first and the annual price underneath in smaller text. Don't change the colours. ## Combine Related Comments Several comments often describe one change: ```text theme={null} "The menu is hard to use on my phone." "I can't find the contact page." "The hamburger icon is too small." ``` These belong together. Use **Handle all open comments**, or add instructions to one comment and dismiss the duplicates with a reply. ## Separate Major Changes Some comments are bigger than they look: > Can customers also book recurring appointments? That may change the database, the booking flow and the emails. Reply first to agree the scope, then build it as its own request, perhaps in Plan mode. ## Resolve Conflicting Feedback Two client stakeholders may disagree: ```text theme={null} "Make the hero bigger." "The hero takes up too much space." ``` Don't build both. Reply in the thread, ask them to agree on one direction, and build once they have. ## A Good Comment Workflow ```text theme={null} PUBLISH ↓ CLIENT PINS COMMENTS ON THE LIVE SITE ↓ TEAM REVIEWS THE COMMENTS ↓ REPLY, ADD INSTRUCTIONS, OR DISMISS ↓ LET AIWA HANDLE THEM ↓ CHECK THE PREVIEW ↓ PUBLISH AGAIN ``` ## Notifications * The Owner and Admins are e-mailed when a client comments. * The comment's author is e-mailed when someone replies, or when the comment is done. * Open client comments with no team reply appear under **Needs you** in the [agency console](/agency/console-overview). Each person can choose, per category, whether they get feedback e-mails immediately, as an hourly digest, or not at all. Change this from the notification bell. ## Next: The Agency Console Comments are one part of running client work. Next, we'll look at the agency console, where you see every project, client, comment and credit in one place. Run your agency from one place: projects, clients, team, usage and activity. # Inviting Team Members Source: https://docs.aiwa.codes/teams/inviting-members Invite teammates, developers, designers, partners and clients to your AIWA workspace without sharing your account credentials or password. Building a product doesn't always happen alone. AIWA allows you to invite other people to collaborate on your projects, making it easier to work with teammates, developers, designers, partners, and other people involved in your product. Instead of sharing account credentials, you can invite people to participate through their own access. **Build together without sharing your AIWA login.** ## Why Invite Team Members? You may want other people involved at different stages of your project. For example, you might have: * A developer helping refine functionality * A designer reviewing the interface * A marketing team preparing the launch * A business partner reviewing progress * A team member managing content * Someone testing the application Rather than sending screenshots back and forth or sharing your AIWA account credentials, you can bring collaborators into the appropriate project. ## Your AIWA Workspace Think of your AIWA account as the place where your products live. Inside it, you may have several projects: ```text theme={null} YOUR AIWA WORKSPACE ↓ ┌──────┼──────────┐ ↓ ↓ ↓ CRM Website Booking App ``` Collaboration allows you to bring other people into your workflow without giving them ownership of your entire account. ## Who You Can Invite on Your Plan Your plan decides who you can invite: | Plan | Team seats (including you) | You can invite | | - | - | - | | **Launchpad** | 3 | Viewers | | **Solo** | 1 | Nobody. Solo is a one-person plan | | **Agency** | 15 | Admins, Editors, Viewers and Clients | | **Enterprise** | Unlimited | Admins, Editors, Viewers and Clients | Clients never take a seat. On Agency, extra Editor seats are \$19 a month each. If a role is locked on your plan, the invite dialog shows which plan unlocks it. ## Invite a Team Member You can invite people from several places, and they all use the same invite dialog: * The **Team** section of your workspace settings * The **People** tab of a project's Control Panel * The **Team** and **Clients** tabs of the [agency console](/agency/console-overview), on Agency and above Choose the option to invite someone. AIWA Invite Team Member Enter the email address of the person you want to invite. For example: ```text theme={null} designer@yourcompany.com ``` Then fill in the rest of the dialog: The e-mail address and the role. For a client, you can add their company name. For an Editor, you can switch on **Can publish** and **Can view secrets** (Owner only). Pick the projects the person can open. This step is skipped for an Admin or for someone given access to all projects. Add a short note that appears in the invitation e-mail. We'll explain each role on the next page. ## Send the Invitation Once you've entered the team member's information, send the invitation. AIWA Team Dialog The invited person receives an e-mail with a link. The link shows who invited them and to what, before they create an account. They sign up or sign in with the invited address, and they're in. If someone is already signed in with that address, they join automatically. ### Pending invitations Until it is accepted, an invitation stays in your list as pending, with its e-mail status. From there you can: * **Resend** it, which sends a fresh link * **Revoke** it, so the link stops working Spending limits are not set in the invite dialog. Once someone joins, you can set their monthly allowance from the [Usage tab](/agency/spend-limits). You don't need to give them: * Your AIWA password * Your email password * Your personal login * Your billing credentials Never share your AIWA account password as a way to collaborate. Invite people through the collaboration features instead. ## Choose Access Carefully Not everyone needs the same level of access. For example, someone helping you actively build the application may need more access than someone who only needs to review the project. Conceptually: ```text theme={null} PROJECT OWNER ↓ Invite Collaborator ↓ Choose Access ↙ ↘ Editor Viewer ``` Give each person only the level of access they need. We'll cover the differences between these roles on the next page. ## Working With a Developer Suppose you're building a SaaS product and another developer is helping you. Your workflow could look like: ```text theme={null} You ↓ Create Project ↓ Build Initial Product ↓ Invite Developer ↓ Collaborate ↓ Continue Building ``` This allows multiple people to participate in the product-development process without sharing a single account. ## Working With a Designer You may want a designer to review: * Layout * Typography * Navigation * Mobile responsiveness * User experience * Branding * Visual consistency Instead of sending screenshots every time the project changes, you can give them appropriate access to review the latest version. ## Working With Your Internal Team AIWA collaboration can also support internal product teams. For example: ```text theme={null} FOUNDER ↓ AIWA PROJECT ↓ ┌────────┬─────────┬──────────┐ ↓ ↓ ↓ ↓ Product Design Marketing Developer ``` Different people can contribute to the same product-development process. This becomes particularly useful as an AIWA project moves from an idea into a real business application. ## Working With Clients Agencies may also need to involve clients in the project lifecycle. For example: ```text theme={null} AGENCY ↓ Build Client Project ↓ Review ↓ Client Feedback ↓ Changes ↓ Publish ↓ Client Comments on the Live Site ``` Clients are different from team members. A client: * Is invited to specific projects only * Doesn't take a seat on your plan * Never spends your credits * Sees the live site and a comment panel in the [client portal](/agency/client-portal), not the builder We'll cover the dedicated Client Sharing & Review workflow later in this section. ## Don't Give Everyone Editing Access More access isn't always better. Someone who only needs to inspect the project shouldn't necessarily be able to modify it. For example: ```text theme={null} Developer → May need editing access Designer → May need editing or review access Business Partner → May only need to review Client → May only need to review ``` Choose access based on what the person actually needs to accomplish. This helps protect the project from accidental changes. ## Collaboration and Production Apps Be especially careful when inviting people to work on applications that are already live. A production application may contain: * Real users * Customer workflows * Payments * Integrations * Business logic * Important data Someone making changes to the project should understand that their work may eventually affect a production application. Use the same workflow we've discussed throughout the documentation: ```text theme={null} CHANGE ↓ PREVIEW ↓ TEST ↓ PUBLISH ``` Don't publish changes simply because a collaborator made them. Review important updates first. ## Collaborating With AIWA Remember that your human team isn't working alone. AIWA itself remains part of the product-development workflow. For example: ```text theme={null} YOUR PRODUCT ↓ ┌────────┼────────┐ ↓ ↓ ↓ YOU TEAM AIWA ↓ BUILD ↓ PRODUCT ``` Your team can use AIWA to help: * Plan features * Build functionality * Improve designs * Debug problems * Explore ideas * Iterate on the product This is where the idea of AIWA as your AI product team becomes particularly powerful. Your human team brings business knowledge and decisions. AIWA helps accelerate the work required to turn those decisions into software. ## Managing Team Members As your project evolves, the people who need access may change. For example: ```text theme={null} Early Stage Founder + Developer ↓ Design Stage + Designer ↓ Launch + Marketing Team ↓ Client Review + Client ``` Review project access periodically and make sure the right people still have the appropriate permissions. ## Remove Access When It's No Longer Needed If someone is no longer working on the project, remove their access rather than leaving unused collaborator accounts indefinitely. When you remove a team member, they receive an e-mail telling them. When you remove a client, you can tick **Let them know by e-mail** to send them a short message naming the projects they can no longer open. This is particularly important when: * A contractor finishes their work * A team member leaves * A client relationship ends * A temporary reviewer no longer needs access * Someone changes responsibilities Good access management becomes more important as your applications become more valuable. ## Collaboration Without Credential Sharing Avoid workflows like: ```text theme={null} One AIWA Account ↓ Password Shared With 5 Different People ``` Apart from being difficult to manage, shared credentials make it harder to control who should still have access. Instead: ```text theme={null} PROJECT OWNER ↓ INVITE ↓ INDIVIDUAL ACCESS ↙ ↓ ↘ Person A Person B Person C ``` Each collaborator uses their own access. ## Common Questions ### Do I need to share my AIWA password? No. Use AIWA's invitation and collaboration functionality instead. ### Can I invite someone just to review my project? Use the appropriate Viewer or review access rather than giving them unnecessary editing permissions. We'll explain roles on the next page. ### Can I collaborate with clients? Yes, on the Agency and Enterprise plans. Clients see their live site and comment on it from the client portal. We'll cover Client Sharing & Review separately because clients need a different experience from internal team members. ### Can my team continue working after the app is published? Yes. Publishing doesn't end development. Your team can continue improving the project, test the changes, and publish new versions when they're ready. ### Should everyone on my team have the same permissions? Usually not. Give people access based on what they actually need to do. Someone reviewing a project doesn't necessarily need the ability to change it. ## A Good Collaboration Workflow A healthy workflow might look like: ```text theme={null} PROJECT OWNER ↓ CREATE PROJECT ↓ INVITE TEAM ↓ ASSIGN APPROPRIATE ACCESS ↓ BUILD WITH AIWA ↓ TEAM REVIEW ↓ TEST ↓ PUBLISH ``` As your product grows, you can adjust who participates and what level of access they have. ## Build Together AIWA can be your AI product team without preventing your human team from participating. ```text theme={null} YOUR PRODUCT ↓ ┌──────────┼──────────┐ ↓ ↓ ↓ YOU YOUR TEAM AIWA └──────────┼──────────┘ ↓ BUILD ↓ SHIP ↓ IMPROVE ``` Whether you're a solo founder bringing in a contractor, a startup team building a product, or an agency working with clients, collaboration gives you a structured way to bring the right people into the project. ## Next: Roles & Permissions Inviting someone is only the first step. Next we'll cover Roles & Permissions, specifically: * Owner, Admin, Editor, Viewer and Client * What each role can do * Who should receive each role * Protecting projects from unnecessary changes * Changing someone's access * Removing access Understand each role and choose the right access for each collaborator. # Roles & Permissions Source: https://docs.aiwa.codes/teams/roles-permissions Owner, Admin, Editor, Viewer and Client: what each AIWA role can do, which plans can invite which roles, and how to give people only the access they need. When you invite someone into your AIWA workspace, you choose what they can do. Not everyone needs to change your project. Some people need to build, some need to look, and some only need to leave feedback. AIWA has five roles: * Owner * Admin * Editor * Viewer * Client **Give people the access they need, and no more than they need.** ## The Roles at a Glance | Role | Who it's for | What they can do | | - | - | - | | **Owner** | The person who owns the workspace | Everything, including billing, publishing and secrets | | **Admin** | Someone who runs the agency with you | Manage people, clients, spending limits and brand. Build projects | | **Editor** | Developers, designers, contractors | Build and change the projects they can see | | **Viewer** | Stakeholders, reviewers, partners | Open and look at projects without changing them | | **Client** | The people you build for | See their live site and comment on it from the client portal | Owner, Admin, Editor and Viewer are **team** roles: they are members of your workspace. A Client is not a member of your workspace. A client is invited to specific projects only. ## Owner The Owner holds every permission in the workspace. Only the Owner can: * Manage billing and the plan * Turn the agency profile on or off * Give another person the right to publish or to see secrets * Invite an Admin There is one Owner per workspace. ## Admin An Admin helps the Owner run the workspace. An Admin can: * Invite and remove team members and clients * Choose which projects people can see * Set monthly allowances and project budgets * Edit the agency's brand and invitation wording * Build and change projects An Admin cannot switch the agency profile on or off, cannot give anyone publish or secret access, and cannot invite another Admin. Whether an Admin can publish or see secrets follows the same two permissions as an Editor, described below. The Admin role is available on the Agency and Enterprise plans. ## Editor An Editor actively builds. Editors can use AIWA to create and change the projects they have access to. Use this role for: * Developers * Designers * Contractors * Product team members ### All projects or assigned projects When you invite an Editor, you choose their scope: * **All projects**: they can work on every project in the workspace. * **Assigned projects**: they can only see the projects you pick. Every other project is invisible to them. Assigned scope is the safer default for contractors and freelancers. ### Two extra permissions An Editor can also be given two sensitive permissions: | Permission | What it allows | | - | - | | **Can publish** | Publish the project to its live address | | **Can view secrets** | See connector keys and other saved credentials | Only the Owner can switch these on. On an ordinary workspace, Admins and Editors have both permissions by default. Once you turn on the agency profile, both start switched off and the Owner turns them on person by person. Be careful with **Can view secrets**. Anyone with it can read the API keys connected to a project, such as Stripe or OpenAI keys. ## Viewer A Viewer can open projects and look at them, but cannot change anything. Use Viewer access for: * Business partners * Investors * Stakeholders checking progress * Team members who don't build Like Editors, Viewers can be given all projects or only assigned ones. ## Client A Client is the person or business you are building for. Clients use the [client portal](/agency/client-portal). They can: * See the live site for their projects * Leave comments, including comments pinned to a spot on the page * Reply to your team and mark their own comments as done * Sign off a hand-off, when you send one Clients never see your files, prompts, other team members, deploy details or spending. Clients are free: * They don't take a seat on your plan. * They never spend your credits. A person can be a team member or a client on a project, not both. Inviting clients is available on the Agency and Enterprise plans. ## Who You Can Invite on Each Plan Your plan decides which roles you can invite and how many team seats you have. Seats include the Owner. Clients never count as seats. | Plan | Team seats | You can invite | | - | - | - | | **Launchpad** | 3 | Viewers | | **Solo** | 1 (just you) | Nobody. Solo is a one-person plan | | **Agency** | 15 | Admins, Editors, Viewers and Clients | | **Enterprise** | Unlimited | Admins, Editors, Viewers and Clients | On Agency, you can add extra Editor seats for \$19 a month each. If you move to a smaller plan, people already in your workspace keep their access. You just can't send new invitations that the smaller plan doesn't allow. ## Choosing the Right Role Before inviting someone, ask: > Does this person need to change the project, or only to look at it and give feedback? ```text theme={null} Runs the agency with you → Admin Builds or designs → Editor Watches progress internally → Viewer Is the customer → Client ``` ## Example: Agency Team Suppose you run a small agency with three client projects. | Person | Suggested role | | - | - | | You | Owner | | Operations lead | Admin | | In-house designer | Editor, all projects | | Freelance developer | Editor, assigned to one project | | Investor | Viewer | | Each client | Client, on their own project only | The freelancer sees only the project they work on. Each client sees only their own site. ## Changing Someone's Access Responsibilities change. You can change a person's role, scope, assigned projects and permissions at any time. You can do this from: * The **Team** section of your workspace settings * The **People** tab of a project's Control Panel * The **Team** and **Clients** tabs of the [agency console](/agency/console-overview) The person is told by e-mail when their access changes. ## Remove Access When Work Ends Remove people when they no longer need access. Common moments: * A contractor finishes their work * An employee leaves * A client project ends * A temporary review is over When you remove a client, you can choose to let them know by e-mail. The message names the projects they can no longer open. ## Roles Are Better Than Shared Accounts Never share your AIWA password with your team. ```text theme={null} PROJECT OWNER ↓ INDIVIDUAL ACCESS ┌────┼────┬────┐ ↓ ↓ ↓ ↓ Admin Editor Viewer Client ``` Each person has their own login, so you can always see who did what and remove one person without affecting anyone else. ## Next: Client Sharing & Review Clients need a different experience from your team. On the next page we'll cover how to bring a client into a project, show them the live site and collect their feedback. Invite clients to review their live site and comment on it, without giving them editing access. # Contacting support Source: https://docs.aiwa.codes/troubleshooting/contacting-support How to reach AIWA support, what to include so the first reply is useful, and what to try before you write. If something is not working and the rest of this section has not solved it, get in touch. **[support@aiwa.codes](mailto:support@aiwa.codes)** ## Asking from inside AIWA For some problems, you can reach support without writing an email, and the details are attached for you: | Where | How | | - | - | | **A failed deploy** | Click **Nudge support** on the failure message | | **A custom domain** | Use the support option in **Control Panel → Domains** | ## Before you write Two minutes here often saves a day of back and forth, and sometimes solves it outright. A surprising number of preview and editor problems are a stale browser tab. Reload before anything else. The troubleshooting section covers the common failures one by one, including previews that will not load, builds that stall, and deployments that fail. If a build failed, run it again. A repeated failure is a real fault and worth reporting; a single one is often a transient upstream hiccup that has already cleared. ## What to include Support can only be as fast as the detail allows. A message with these four things usually gets a specific answer first time; one without them usually gets a request for them. The project name, and the link to it if you have one open. The prompt you sent or the button you pressed, immediately before it went wrong. The exact error text if there is one. A screenshot of the whole screen beats a crop, because the surrounding state is often the clue. Roughly what time, and your timezone. That is what makes your session findable in the logs. If it happened more than once, say how many times and whether anything differed between attempts. A fault that is intermittent is diagnosed very differently from one that is reliable. ## Credits and billing If a build failed and you think you were charged for it, include the project and the approximate time. Charges for work that genuinely failed are put right. Never send passwords, API keys, or card details in a support message. Support will never ask for them. If a connector key needs replacing, do it from the Connectors screen inside your account. ## What to expect You will get a reply with either a fix, a workaround, or a clear statement that it is being investigated. If it is a fault on our side, you will be told when it is resolved rather than being left to check. ## Next: Glossary Plain-language definitions of the terms used across AIWA. # My AIWA credits disappeared Source: https://docs.aiwa.codes/troubleshooting/credits-disappeared Understand where AIWA credits went by reviewing usage history, and learn how to prevent unexpected credit drain. If your balance is lower than you expected, one of these is usually the reason. ## Builds and edits cost different amounts There's no fixed price for a build or an edit. A full application with several pages uses far more credits than a one-line copy change, because it's far more work. Planning, image generation, and automatic repairs during a build all count toward that build. Check the completed charge in the builder after each request to see what it actually cost. See [What each action costs](/billing/credit-costs). ## Other actions that use credits | Action | Credits | | - | - | | Generating an image | 4 | | A Brief, after your free one each day | 2 | | Voice transcription | 2 | | Mobile deep scan | 2 | | An Explore Mode question | 1 | | Android APK | 10 | | Google Play kit | 5 | | App Store kit | 10 | Publishing, connecting a domain, and hosting don't use credits. ## Your balance went below zero Every workspace has a one-time cushion of 20 credits, so a build that runs slightly over your balance can finish instead of stopping halfway. If you used it, your balance shows as negative, and the amount is taken from your next monthly credits or upgrade. The cushion doesn't refill. ## You're looking at a different workspace Credits belong to a workspace, not to you personally. If you're a member of someone else's workspace, the balance in the sidebar is that workspace's balance. Check which workspace is selected. ## Someone else on your team is building Everyone in a workspace draws from the same balance. On the Agency plan, the **Usage** tab in the Agency console breaks spending down by person, project, and day, and you can set spending limits for each person and project. See [Spend limits](/agency/spend-limits). ## What you're not charged for * A build that's interrupted before it finishes * Answering AIWA's clarifying questions * A Brief you abandon halfway If a build failed and you think you were charged for it anyway, contact support with the project name and approximate time. Charges for work that genuinely failed are put right. ## Avoiding surprises Use Explore Mode (1 credit) or the Brief to make sure AIWA understands you before a large build. Several focused requests are easier to review, and to stop, than one enormous one. Your balance is always visible while you build, so you see each charge as it happens. ## Next: My Stripe integration is not working Fix payment problems with Stripe and PayPal. # My AIWA database is not working Source: https://docs.aiwa.codes/troubleshooting/database-not-working Fix common AIWA database issues, including connection errors, missing tables, and failed migrations after a deploy. AIWA gives each project that needs stored data its own Neon Postgres database. If data isn't saving or loading, start by checking whether your project has one. ## My project doesn't have a database AIWA only adds a database when your request needs stored data, such as accounts, records, bookings, or a dashboard. A website with a contact form doesn't get one. Its form submissions are emailed to you through Resend instead. If you expected submissions to be saved, ask for it: > Save every enquiry to the database and show them in an admin dashboard. See [Your database](/builds/database). ## Data isn't saving Describe exactly what happens in Debug Mode: > **Expected:** Saving a new client adds it to the Clients list. > > **Actual:** The form shows "Saved", but the client doesn't appear in the list, even after reloading. > > Fix this without changing the form's design. Say whether the data is missing after a reload. That tells AIWA whether the problem is in saving or in displaying. ## The preview won't start because of the database If the preview reports that the database never became ready, the app's database setup is failing when it starts. Click **Fix it** on the preview message, or describe the error in Debug Mode. ## A column or table is missing This usually happens when a feature was added without the matching data structure, or after restoring an older version. Ask AIWA directly: > The Bookings page errors because the bookings table has no "notes" column. Add the column and keep the existing bookings. Restoring an earlier version of your project restores code, not data. It doesn't roll your database back. See [Version history](/publishing/version-history#what-about-my-database). ## Users can see each other's data Treat this as urgent. Describe it in Debug Mode: > Customer A can see Customer B's orders. Audit data access so each signed-in user only sees their own records. See [Authentication](/builds/authentication). ## Next: Mobile export errors Fix readiness, Android, and iOS export problems. # My custom domain is not connecting to AIWA Source: https://docs.aiwa.codes/troubleshooting/domain-not-connecting Fix a custom domain that will not connect to your AIWA project by checking DNS, HTTPS, and propagation status. Custom domains are available on the Solo plan and above. Open **Control Panel → Domains** to see where your domain is in the process. ## Find your status | Status | What's happening | What to do | | - | - | - | | **Pending** | AIWA can't see your DNS records yet | Check the records match exactly, then wait for DNS to update | | **Ownership verified** | Your records are correct | Nothing. AIWA moves on to securing the domain | | **Securing (HTTPS)** | The secure certificate is being issued | Wait. This can take a few minutes after verification | | **Live** | Your domain serves your app over HTTPS | You're done | AIWA only marks a domain as live once a real HTTPS request to it succeeds. If you can see your app at the domain but it isn't marked live yet, the certificate is still being issued. ## Stuck on Pending Compare each record at your DNS provider with what AIWA shows. Check: * **Type**, for example CNAME or TXT * **Name / Host**: many providers add your domain automatically, so enter only the part AIWA shows * **Value / Target**: copy it exactly, with no extra spaces or characters * **The verification TXT record** is a separate record. Don't add it to an existing SPF record Make sure you're editing DNS at the provider that manages your nameservers. This isn't always where you bought the domain. DNS changes can take time to spread. Once the records are right, avoid changing them again while you wait. ## Stuck on Securing (HTTPS) If your records are correct, AIWA automatically asks for the certificate to be issued again. If it's still securing after a day, contact support from the Domains section. ## The root domain doesn't work AIWA recommends connecting `www.yourdomain.com`. Connecting the bare `yourdomain.com` needs a DNS method your provider supports at the root, such as ALIAS, ANAME, or CNAME flattening. You'll find these under **Advanced apex setup**. ## My email stopped working You may have changed or removed an email record. Use **Check email records** in the Domains section to compare your current records with the snapshot AIWA saved before you connected, then restore anything that's missing. Keep your MX, SPF, DKIM, and DMARC records exactly as they were. ## Still stuck? Use the support option in the Domains section and choose **Website connection** or **Email DNS concerns**. Your domain details are sent along with the request. See [Custom domains](/publishing/custom-domains) for the full setup guide. ## Next: My credits disappeared Understand where your credits went. # AIWA generated an error in my project Source: https://docs.aiwa.codes/troubleshooting/generated-error What to do when AIWA generates code that produces an error, including how to use Debug mode to fix it fast. Most errors are caught and repaired before you ever see them. AIWA checks every build, confirms the page actually renders, and runs automatic repair rounds when something fails. When an error does reach you, there are three ways to fix it. ## 1. Use Fix it When the preview shows **Preview error**, a blank page, or a backend that crashed while starting, click **Fix it**. AIWA reads the error, finds the file responsible, and repairs it in place. While it works, you'll see **Fixing the preview…**. If AIWA can't resolve it after several attempts, you'll see **Couldn't fix this automatically**. You can choose **Try fix again**, or move on to Debug Mode. Fix it uses credits, like any other repair. It only appears for errors a code change can actually fix, so you won't be charged for retrying a problem on AIWA's side. ## 2. Use Debug Mode For errors that aren't on screen, such as a button that does nothing or data that doesn't save, switch to Debug Mode and describe the problem precisely: > **Expected:** Clicking Save stores the booking and shows a confirmation. > > **Actual:** Clicking Save does nothing. No confirmation appears. > > **Steps:** Open Bookings, click New Booking, fill in the form, click Save. > > Fix this without changing unrelated parts of the app. The more specific you are, the faster AIWA finds the cause. See [Fixing errors](/building/fixing-errors). Use **Select an element** in the preview to attach the exact button or section that misbehaves. ## 3. Restore a working version If a recent change broke something important and you'd rather go back, open version history and restore the last version that worked. Then make the change again in smaller steps. AIWA also does this for you when a build fails repeatedly. See [Version history & restore](/publishing/version-history). ## Next: My project will not deploy What each deploy failure means and how to fix it. # Mobile export errors in AIWA Source: https://docs.aiwa.codes/troubleshooting/mobile-export-errors Troubleshoot common errors when exporting your AIWA project for Android or iOS, including signing and build failures. ## The export buttons are locked There are two reasons the Android and iOS options can be unavailable. | Reason | Fix | | - | - | | **Your plan** | The APK, Google Play kit, App Store kit, and mobile source download are on the Agency plan and above. The readiness scan itself is free on every plan | | **Your readiness score is below 80** | Fix the findings and scan again | ## Raising your readiness score Every blocker lowers your score below 80, so start with blockers, then warnings. Each finding names the file and the problem, such as a tap target that's too small or content hidden behind the phone's notch. > Fix the mobile readiness findings for tap targets and safe areas without changing the desktop layout. Re-run the scan to confirm the score has gone up. For an AI review of the areas automatic checks can't judge, such as animations and native-feeling layouts, run the deep scan (2 credits). See [Mobile readiness scan](/mobile/readiness-scan). ## The Android build failed Use the error information AIWA shows and describe it in Debug Mode: > The Android build starts but fails before the APK is generated. Error: \[PASTE ERROR]. Fix it without changing unrelated functionality. Then build again. ## Google Play rejects the privacy policy URL Google Play needs a live web address for your privacy policy, not a file. The release kit adds the policy page to your app. Publish your project again so the page is online, then use its address. ## The iOS build fails on my cloud build account or Mac AIWA doesn't compile the iOS app itself. You build it from the App Store kit. Most failures are about signing: * Check that your App Store Connect API key is set up as the kit's signing guide describes * Check the bundle ID matches the app you created in App Store Connect * Work through the kit's submission checklist, which lists the Info.plist keys that most often cause rejections If the error points to your app's own code, describe it to AIWA in Debug Mode, then generate a fresh kit. ## The app works on the web but not on the phone Describe the difference: > On Android, the login form is hidden behind the keyboard when it opens. Fix the mobile layout without changing the desktop experience. ## Next: Contacting support How to reach AIWA support and what to include. # My AIWA preview will not load Source: https://docs.aiwa.codes/troubleshooting/preview-wont-load Fix an AIWA preview that will not load, from browser and network checks to rebuilding the project preview. Your preview runs your full application, frontend and backend, in its own cloud sandbox. When it doesn't appear, AIWA usually tells you why. Your app and its files are saved separately from the preview. A preview problem never deletes your work. ## "Preview paused" If you've been away for a while, AIWA puts your preview to sleep: > We put your preview to sleep while you were away. Your app and data are untouched. Open the project and the preview wakes up again. This takes a moment. ## "Reconnecting to your preview" The connection to the sandbox dropped briefly. AIWA restores it automatically. Wait a few seconds. ## "Preview unavailable" | Message | What it means | What to do | | - | - | - | | **Your app is built and saved, but the preview could not start** | The sandbox didn't start. This is usually temporary | Click **Retry** | | **The preview service is temporarily unavailable** | AIWA's preview service is having a problem | Retry in a moment | | **Its backend crashed while starting** | Your app's own server code fails when it starts, so retrying gives the same result | Click **Fix it**. AIWA diagnoses and repairs the server code | ## "Preview needs secrets access" The preview runs with your project's real connector credentials. If your role doesn't allow you to see secrets, you can't open the live preview, but you can still edit and build. Ask the project owner to give you secrets access, or to check the preview for you. See [Roles & permissions](/teams/roles-permissions). ## A blank page or an error screen If the preview loads but shows a blank page or an error, AIWA detects it and shows **Preview error** with a **Fix it** button. See [AIWA generated an error](/troubleshooting/generated-error). ## Browser checks If none of the above appear and the preview area is simply empty: A stale browser tab is the most common cause. Ad blockers and privacy extensions can block the preview frame. Company networks and VPNs sometimes block the preview's address. ## Next: AIWA generated an error Fix errors in your app with Fix it and Debug mode. # My Stripe integration is not working in AIWA Source: https://docs.aiwa.codes/troubleshooting/stripe-not-working Debug a Stripe integration that is not working in your AIWA app, from API keys to webhooks and test vs live mode. Most payment problems come down to the wrong keys, the wrong mode, or a step after payment that never runs. This page covers Stripe and PayPal. ## Check the connector first Open **Connectors** in your project and check the payment connector. AIWA checks your keys with the provider when you save them, so an error here points straight at the problem. ### Stripe | Field | Check | | - | - | | **Secret key** | Starts with `sk_test_` while you're testing and `sk_live_` for real payments | | **Currency** | The three-letter code your prices are in, such as `gbp`. Empty means US dollars | ### PayPal | Field | Check | | - | - | | **Client ID** and **Secret** | Copied from the same app in the PayPal developer dashboard | | **Mode** | `sandbox` while testing, `live` for real customers. It must match where you copied the credentials from | | **Currency** | Your PayPal account's main currency. A payment in another currency can wait in PayPal until you accept it by hand | Never paste a secret key into a prompt or into your app's frontend code. Add it on the connector page only. ## Test mode vs live mode The most common problem is mixing the two. * With **test keys** or **sandbox mode**, no real money moves. Use Stripe's test cards, or a PayPal sandbox buyer account, to pay. * With **live keys** or **live mode**, real cards are charged. If test payments work and live ones don't, check that the live keys are saved on the connector and that the live site has been published since you changed them. ## Payment succeeds, but nothing happens If the customer pays but doesn't get access, the payment worked and the step after it didn't. Describe exactly that in Debug Mode: > Stripe checkout completes successfully and the payment appears in my Stripe dashboard, but the customer's account isn't upgraded to Pro afterward. Fix the post-payment step without changing the checkout. If your app relies on Stripe webhooks, mention it, and check the webhook's delivery log in your Stripe dashboard for failed attempts. ## Checkout uses the wrong provider If your project has PayPal connected and not Stripe, asking AIWA to "add a checkout" uses PayPal. To use a particular provider, name it in your request: > Add a Stripe checkout for the Pro plan at \$49 a month. ## Still not working? See the [Stripe](/integrations/stripe) and [PayPal](/integrations/paypal) guides, or [contact support](/troubleshooting/contacting-support). ## Next: My database is not working Fix data that won't save, load, or appear. # My AIWA project is stuck generating Source: https://docs.aiwa.codes/troubleshooting/stuck-generating Fix an AIWA project that appears stuck while generating, including retry steps and how to recover any partial work. A large build can take several minutes. Before assuming it's stuck, check what AIWA is telling you. ## Is it actually stuck? While AIWA works, the status line under your message shows which step it's on and how long that step has been running. Some steps, such as planning a large app or checking the finished build, can run for a while without new text appearing. A first build of a full application usually takes longer than an edit, because AIWA plans the app, writes it, checks that the page actually renders, and repairs anything that fails before showing it to you. As long as the elapsed time keeps counting, AIWA is still working. ## If you closed the tab or lost connection Your build keeps running on AIWA's side even if you close the browser. When you return to the project, you'll see: > Your build is still running. Picking it back up... AIWA reconnects to the build in progress. You don't need to send your message again. ## If the run stopped If a build is interrupted before it finishes, AIWA tells you plainly: > This run stopped before it finished. Nothing it produced was saved, and it was not charged. or, if part of the work was already saved: > This run stopped early and was not charged. Your work up to that point is saved below. In both cases, send your request again when you're ready. ## "A build is already running on this project" AIWA runs one build at a time per project. If you see this message, the previous build is still going and will finish on its own. Wait for it to complete, then send your next request. If a build ever gets stuck in a "running" state for good, AIWA automatically releases it after 20 minutes, so you're never locked out of your own project. ## Stopping a build yourself You can click **Stop** while AIWA is working. AIWA stops the build and restores your project files to how they were before the request. ## Steps to try Give a large build a few minutes, especially a first build. If nothing has changed for several minutes, reload. AIWA reconnects to a build that's still running. If the same request keeps stalling, break it into stages. See [Writing effective prompts](/building/writing-effective-prompts#break-complex-work-into-stages). If a build fails repeatedly, contact support with the project name and the approximate time. See [Contacting support](/troubleshooting/contacting-support). ## Next: My preview will not load What to do when the live preview doesn't appear. # My AIWA project will not deploy Source: https://docs.aiwa.codes/troubleshooting/wont-deploy Diagnose a failing AIWA deploy, from build errors and environment misconfigurations to database migration failures. When a deploy fails, AIWA reads the build output and tells you in plain language what kind of failure it was. Start with that message. ## What the message means | Message | Cause | What to do | | - | - | - | | **Your app's code didn't compile** | The production build is stricter than the preview and found an error in your code | Click **Fix it**, then publish again | | **Build servers had a hiccup** | A temporary problem on AIWA's build infrastructure | Click **Retry deploy** | | **We hit a snag on our side** | A packaging or start-up problem on AIWA's side, not your app | Click **Retry deploy**. If it happens again, use **Nudge support** | | **The build ran long and was stopped** | The build servers were slow | Click **Retry deploy**. A fresh build almost always completes | | **There are no saved files to deploy** | Your project has no saved files, even though the preview may look fine | Restore a version from version history, or make one change in chat, then publish again | The full build log is under **Technical details** if a developer needs it. Use **Copy details** to copy it. ## Why does the preview work but the deploy fail? The preview is forgiving so you can iterate quickly. The production build checks your code more strictly. An error the preview tolerates can stop a production build. This is exactly what **Fix it** is for. ## If it keeps failing Infrastructure problems usually clear on a second attempt. After a failed deploy, a **Nudge support** button appears. It sends the failure to AIWA support with the details attached. You'll see **Support has been notified** once a ticket is open. If deploys started failing after a specific change, restore the version before it and publish that. ## Deployed, but the live app is broken If the deploy succeeded but something doesn't work on the live site, compare it with the preview and describe the difference in Debug Mode: > Bookings save correctly in Preview, but on the live site the Save button shows an error. The project owner can also roll the live site back to an earlier release from **Control Panel → Releases** while you fix it. ## Next: My custom domain is not connecting Fix DNS, verification, and HTTPS problems. # Branding & Domains Source: https://docs.aiwa.codes/white-label/branding-and-domains Brand your white-label platform: name, logo, colours, customer e-mails and legal links, then connect your platform domain and your published-apps domain. Your customers should only ever see your brand. This page covers the **Branding** and **Domains** tabs of the partner console: how your platform looks, how it e-mails customers, and where it lives. ## Your Brand Name Your brand name appears everywhere your customers look. As you type it, AIWA checks whether it's available. If the name is already taken or reserved, you can't save it, and you're offered two alternatives that are free to use. Names that differ only in capitals or punctuation count as the same name, so "Acme", "ACME" and "Acme!" can't belong to two partners. ## Brand Studio The **Branding** tab is your brand studio. Nothing changes for your customers until you save. | Field | What it does | | - | - | | **Logo** | PNG, JPEG, WebP or SVG, up to 5 MB | | **Colours** | Your palette. Not sure? Let the studio mix two palettes for you | | **Tagline** | One line used as your search description and on your share card. Select **Suggest taglines**, or leave it blank and one is written from your brand name | | **Support e-mail** | Where customer replies land, and the address on your documentation's Contact Support page | | **Sender name** | The name customers see on e-mails from you. Blank uses your brand name | | **Badge** | Whether customers' published apps show a "Made with" badge with your brand name, or no badge | | **Documentation URL** | Where your platform's help links go, if you use your own docs site | The palette and tagline helpers are free for partners. ### Live preview The studio shows your unsaved changes in a live preview, on desktop and mobile: * **The app** your customers use * **The welcome e-mail** * **The verification e-mail** ## Legal Pages Your sign-up page should link your own terms. In the Branding tab, add: * **Terms of Service URL**: the terms your customers accept when they sign up * **Privacy Policy URL**: how you handle your customers' data Both are optional. Until you add yours, your sign-up page links AIWA's standard policies. ## Customer E-mail Your customers receive welcome, verification and account e-mails. By default, AIWA sends them from an AIWA address under your brand name, with your logo and support contact. To send from your own domain, connect a Resend account: In the partner console, find the customer e-mail section. Enter your sending address and a Resend API key with full access, then select **Verify and save**. Select **Send test to me** to check delivery. Connecting Resend also turns on **sign-up notifications**, so you're told whenever someone signs up on your platform. Password-reset e-mails are sent by the sign-in provider and need their own sender configuration. Partner programme e-mails to you (not your customers) come from AIWA. ## Your Two Domains Your platform uses two addresses, each with its own purpose: | Domain | What it's for | Example | | - | - | - | | **Platform domain** | Where your customers sign in and build | `app.yourbrand.com` | | **Published apps domain** | Where your customers' apps go live | `yourbrandapps.com` | ## Connect Your Platform Domain Use a subdomain, such as `app.yourbrand.com`. In the **Domains** tab, enter your platform subdomain, without `https://` or a path. The console shows two DNS records. Add them at your DNS provider. The console checks automatically every 15 seconds. ## Connect Your Published Apps Domain For the published apps domain, choose where DNS is managed: | Option | How it works | | - | - | | **Keep DNS in Cloudflare** | Use your existing Cloudflare account, with no nameserver change. You can use a domain or a subdomain from a zone already active in Cloudflare | | **Let AIWA manage DNS** | Use a whole domain dedicated to published apps, such as `yourbrandapps.com`, and change its nameservers at your registrar to the two values the console shows | ### Keep DNS in Cloudflare Create a Cloudflare API token with **Zone Read** and **DNS Edit** permissions, limited to the zone for this domain. Copy the token and paste it into the console. AIWA stores it encrypted. ### Let AIWA manage DNS Replace the nameservers at your domain registrar with the two values shown. The console checks automatically. ## Going Live Once the DNS is correct, AIWA secures the domain with HTTPS. The domain goes live as soon as it's secure, usually within a few minutes. On the published apps domain, new apps publish there straight away. Existing apps move when they are next published. ## Next: Customers & Offers With your brand and domains ready, the next step is deciding what your customers pay. Set your plans, free offers, project caps and top-up rate. # Customers & Offers Source: https://docs.aiwa.codes/white-label/customers-and-offers Set your white-label prices: Solo and Agency offers, a partner-funded Free plan, project caps, your customer top-up rate and display currency, and manage your customers. On your white-label platform, you decide what customers pay and what they get. This page covers the **Pricing**, **Users** and **Credits** tabs of the partner console. Customers pay you through your own Stripe account. Connect Stripe before you publish paid prices: prices are created on your Stripe account. ## Plans and Offers Your customers choose from two plan families, the same ones AIWA sells: | Family | Who it's for | | - | - | | **Solo** | One builder, with their own workspace | | **Agency** | Teams that invite clients and ship with sign-off | Inside each family you create **offers**: the price, the monthly credits and the project cap. You can have up to 12 published offers in each family. The console starts you with suggested pricing, the same grid AIWA uses itself. Edit it, then select **Publish** to go live. ### Rules for paid offers * Two paid offers in the same family must have different credit allowances. To make a variation, duplicate an offer and change its allowance before publishing. * Each offer's price must work out to at least \$0.11 per credit, just above your wholesale cost, so you can't accidentally sell below cost. * Changes to an offer's allowance take effect at each customer's next billing cycle. ## A Free Plan You can offer a **Free** plan: Solo access that you fund from your credit pool. Free sign-ups don't need Stripe, so you can go live with a free tier while Stripe is still being set up. Choose how Free credits work: | Option | How it works | | - | - | | **Monthly** | Refills every 30 days. Unused credits expire | | **One-time starter** | Granted once. They never expire | | **No credits** | Solo access with no credits. Customers buy top-ups or upgrade | Two controls protect your pool: * **Monthly budget**: the most credits you'll give away as free grants each calendar month. Leave it blank for no cap, or enter 0 to pause free grants. * **Reserve**: credits kept back for paying customers. Left blank, AIWA keeps your largest paid allowance in reserve, so a free grant never starves a paying customer. Free credits require a verified e-mail address. Turning Free off stops new sign-ups at once; existing Free customers keep Solo access and any credits they bought. ## Project Caps Each Free, Solo or Agency offer can have a project cap: **Unlimited** (the default), or a whole number of 1 or more. * Caps apply straight away to every workspace on that offer. * A workspace at its cap keeps all its projects and can keep editing them, but can't create, remix or start from a template until it's under the cap. * Every non-deleted project counts, including drafts and suspended projects. Deleting a project frees a slot. ## Your Customer Top-up Rate When your customers buy extra credits mid-month, they pay your **top-up rate**. * The minimum is \$0.20 per credit. * The maximum is \$1.00 per credit. * Above \$0.50, the console asks you to confirm you meant it. Your rate is separate from what you pay AIWA. You buy pool credits at the wholesale rate of \$0.08 each. ## Display Currency Choose how prices are shown to your customers: | Setting | What customers see | | - | - | | **US dollars** | Prices shown and charged in US dollars | | **Euros** | Prices shown in euros at the ECB rate, still charged in US dollars | ## Your Customers The **Users** tab lists everyone on your platform, with their plan and credits. Customers can sign up themselves on your domain. You can also create an account for a customer: In **Users**, choose to create a user and enter their details. The customer is e-mailed their sign-in details with a temporary password. The password is also shown to you once, in case the e-mail doesn't arrive. They can choose their own with **Forgot password** once they're in. The **Projects** tab shows the projects your customers have built. ## Your Credit Pool The **Credits** tab shows your pool: your balance, what you've bought and what your customers have used. * Your monthly partner credits are added every month and roll over. * Every customer grant (plans, top-ups, free offers) is paid from the pool. * Buy more at \$0.08 per credit, with a minimum of 1,000 credits. If the pool can't cover a customer's credits, the grant waits until you top up, even though the customer has paid you. Keep a buffer, and act on the low-pool alert. ## Next: Your Hosted Handbook Your customers need help docs too. Next, we'll look at the handbook AIWA can host under your brand. A full handbook on your domain, in your name, in up to six languages. # Your Hosted Handbook Source: https://docs.aiwa.codes/white-label/hosted-handbook Give your white-label customers a full help handbook under your brand, on your own domain, with your screenshots and in up to six languages. Your customers will need help. Your platform can link to documentation in two ways: * **Your own docs site**: you write and host it yourself, and your platform links to it. * **A hosted handbook**: AIWA hosts a complete handbook for your platform, written under your brand name. Our own documentation never appears under your brand. ## Linking Your Own Docs In the **Branding** tab, enter your **Documentation URL**, for example `https://docs.yourbrand.com`. The account menu and the Templates page on your platform then link there. If you leave it blank, those links stay hidden. ## The Hosted Handbook With a hosted handbook, your customers get a full guide to building on your platform, with your name on every page. It covers getting started, building, integrations, publishing, mobile export, teams and troubleshooting. The hosted handbook is switched on for your platform by AIWA. If you don't see a **Documentation** tab in your partner console, it isn't enabled for you yet. ### What's tailored to you * Your brand name throughout * Your published apps domain in examples * Your support e-mail on the Contact Support page (set it in Branding) * Your own credit prices: pages about AIWA's plans and prices are left out, and a credits page based on your own offers takes their place ## Your Handbook's Address The handbook is live as soon as it's enabled, on your platform's address. You can move it to its own subdomain, such as `docs.yourbrand.com`: In the **Documentation** tab, enter the subdomain. Add the records shown at your DNS provider. The page checks automatically; propagation can take a few minutes. Once the DNS is set, AIWA secures the domain. It goes live as soon as it's secure, usually within a few minutes. Once it's live, your own domain becomes the handbook's main address. ## Use Your Own Screenshots Every screenshot in the handbook starts as a plain, unbranded image. In the **Documentation** tab, you can replace any of them with your own: * **Upload yours** to replace an image * **Replace** an image you've already changed * **Use the default** to go back to the plain image Nothing here is required. Any image you leave alone stays as the unbranded default. ## Languages The hosted handbook is available in six languages: | Code | Language | | - | - | | `en` | English | | `fr` | French | | `es` | Spanish | | `nl` | Dutch | | `de` | German (formal, *Sie*) | | `de-informal` | German (informal, *du*) | In the **Documentation** tab: 1. Tick the languages you want to offer. 2. Choose a default language. 3. Select **Save languages**. New platforms start with English only. You can turn English off once another language is the default. ### What readers see * Readers can switch language with the language picker. Their choice is remembered, and they stay on the same page. * The handbook does not guess from the browser's language; it uses the reader's choice or your default. * Search works in the selected language. Languages apply to the hosted handbook only. They don't translate the app itself or your partner console. ## Next: Troubleshooting That's the end of the White Label section. Next, we'll look at troubleshooting common problems. Fix common problems, starting with a project that seems stuck generating. # White Label Overview Source: https://docs.aiwa.codes/white-label/overview Run AIWA as your own branded app-building platform: your name, domain, Stripe and prices. Plans, WL999, partner credits and how the programme works. White Label lets you offer the whole AIWA platform as your own product. Your customers sign up on your domain, see your name and logo everywhere, pay you through your own Stripe account, and build apps that publish on your domain. AIWA stays in the background. **Your platform, your customers, your prices.** ## What You Get * Your name, logo and colours across the whole product, including loading screens and e-mails * Your own domain, with sign-in working on it * A second domain where your customers' apps go live * Your own Stripe account, so customers pay you directly * Your own prices, for plans and credit top-ups * A **partner console** for your customers, pricing and credit pool * An Agency-level workspace for your own builds * Partner credits every month Your customers never see AIWA. We don't co-brand and we never contact your customers. ## Plans | Plan | Price | Partner credits | | - | - | - | | **Monthly** | \$199 a month | 1,500 a month | | **Annual** | \$1,990 a year (two months free) | 1,500 a month | | **WL999** | \$999 a year, locked for as long as you stay subscribed | 500 a month | **WL999** is a launch offer for new partners: the annual plan for \$999 a year instead of \$1,990. The price never goes up while your subscription stays active. Lifetime White Label deals are no longer sold. Existing lifetime partners keep their plan. You can cancel at any time from your console. Your customers and their apps stay yours to hand over. ## How Partner Credits Work Everything your customers build runs on credits. As a partner, you hold a **credit pool**: * Your monthly partner credits are added to the pool and **roll over** if unused. * When a customer gets credits (from a plan, a top-up, or a free offer), they come out of your pool. * You can buy extra pool credits at the wholesale rate of **\$0.08 per credit**, with a minimum purchase of 1,000 credits. You sell credits to your customers inside your plans and top-ups, at prices you set, and keep the difference. Keep an eye on your pool. If it runs too low to fund a customer's credits, the grant waits until you top up, even though the customer has already paid you. The console warns you before that happens. ## How It Works Choose monthly, annual or WL999 and check out. Your platform exists as soon as payment is confirmed. Name your platform, pick your colours and add your logo. A live preview shows what your customers will see. Connect your own Stripe account. Customers pay into it, at plan and top-up prices you choose. Connect the domain where customers sign in and the domain where their apps go live. From there, it's your product. ## The Partner Console After setup, you run your platform from the partner console. Its tabs are: | Tab | What it's for | | - | - | | **Overview** | Your setup progress and how your platform is doing | | **Users** | Your customers, their plans and their credits | | **Projects** | The projects your customers have built | | **Credits** | Your credit pool: balance, purchases and usage | | **Pricing** | Your plans, offers, top-up rate and currency | | **Branding** | Your name, logo, colours, e-mails and legal links | | **Domains** | Your platform and published-apps domains | | **Documentation** | Your hosted handbook, if it's enabled | | **Billing** | Your own White Label subscription | A setup tracker in the console shows which steps are done and what to do next. ## Next: Branding & Domains Next, we'll set up your brand and connect your domains. Name, logo, colours, e-mails, legal pages, and the two domains your platform uses.