Frequently Asked Questions
Questions we get most often, grouped by theme.
About the product
Is Appsanic for me if I've never coded?
Yes. Most of our users haven't. Start with the Quickstart.
Is Appsanic for me if I'm a senior engineer?
Yes, in a different way. Read Writing Prompts and Fast vs Pro, then treat Appsanic as the part of your stack that handles the scaffolding-heavy work (auth, CRUD, payments, notifications) while you focus on the parts that actually differentiate your product.
Does the agent really work, or is this a demo dressed up?
It works. Real apps from real founders launch on the App Store and Play Store every week. The honest caveat: the agent is best on the kind of mobile app most people want to build (React Native, Expo, Supabase). It's weaker on more unusual stacks or deeply research-flavoured code.
What happens to my app if Appsanic goes away?
Your code is in your GitHub. Your backend is in your Supabase. Your app store accounts are in your name. Your app keeps running. You'd lose the ability to iterate with the agent; everything else continues.
Can I use this to build a web app?
Appsanic is focused on mobile apps. The generated codebase includes a web build via Expo Web, but we don't optimize for complex web-first products. For web-only, use a different tool.
About ownership
Who owns the code the agent writes?
You do. Every prompt you write and every file the agent produces belongs to you. See our Terms of Service for the long form.
Can I open-source what the agent writes?
Yes. The code is yours; you can license it however you want.
Does Appsanic train AI models on my prompts?
No. Your prompts and generated code are processed by AI model providers under our commercial agreements and are not used to train foundation models.
Do I need to credit Appsanic in my app?
No. No attribution required. You can, of course, if you want to.
About the models
What's the difference between Fast and Pro?
See Fast vs Pro. Short version: Pro thinks longer, sees more of your project at once, and catches edge cases Fast misses. Pro costs more per request. Fast is the default.
Can I pick which AI model powers this?
Not today. We curate the model lineup to keep quality consistent. We use leading commercial models from our providers. See our Sub-processors list for current providers.
Will Appsanic get faster or smarter over time?
Yes. We update the underlying models as better ones are released. Every Appsanic user automatically benefits when we do. You don't pick versions.
About output quality
The code looks generic. How do I make it feel like mine?
Two paths:
- Prompt for it. Paste screenshots of apps you like and describe the tone. "Make the copy feel like Linear's. Direct, confident, a bit playful."
- Edit after export. Once in GitHub, customize components, copy, motion, and palette to taste. Push changes back via git.
Is the generated code high quality?
It's well within the range of code a senior React Native engineer would write. Conventions follow modern React Native + TypeScript practices: styling is StyleSheet.create plus a central theme.ts design-token file (no NativeWind, no Tailwind), and Zustand holds shared state. See Editing Exported Code for the specifics.
That said, no code is perfect. Review what you release. Test before deploying. See the AI disclaimer in our Terms.
What if the agent produces a bug?
Tell it. The agent reads error messages well and can usually fix its own bugs when you paste them in. If it keeps missing, start a new conversation or switch from Fast to Pro.
What if the agent produces code that infringes someone's copyright?
AI models occasionally write code that resembles something in their training data. Before you launch, give the output the same review you'd give any contributor's code. Our Terms cover the details.
About connectors
Do I have to use Supabase?
No, but it's the default, and it's the only backend with a managed connector. Supabase covers auth, database, storage, and realtime in one service. If you'd rather use another backend, the agent can wire it up best-effort when you ask - it just won't get the managed treatment (encrypted key storage, account tools, an audit log). See Authentication and Database & Data.
Can I use my existing backend?
Yes. If you have an existing API, tell the agent: "The app should fetch data from my existing API at https://api.myapp.com. Here are the endpoints..." The agent generates the client calls.
What third-party services can the agent set up?
There are sixteen managed connectors: Supabase, Stripe, Resend, OpenAI, Anthropic (Claude), PostHog, Sentry, RevenueCat, Twilio, OneSignal, Mapbox, Google Maps, Algolia, Replicate, Expo Push, and AdMob. Connect a service once in your dashboard and every project in your account can use it. Connecting requires a paid plan; browsing the catalogue doesn't. For anything outside the catalogue - anything with a well-documented API - the agent can usually wire it up best-effort when you ask. It will tell you it's not a managed connector, ask for a fresh minimum-scope key (never a production master key), and keep secret values out of the app itself. See Connectors Overview for the full picture.
Is it safe to give Appsanic my API keys?
Yes, and here's the honest version of why. Keys are encrypted with AES-256-GCM before they're stored, and saved secrets never display again - not in your browser, not to us. The AI is built so it structurally never sees secret or admin keys; only values designed to be public ever reach your app's code. Every action the AI takes in your account is logged to the Activity feed on that connector's page. And the agent will never ask for a key in chat - if you paste one there, it refuses and points you to the dashboard. Disconnecting a service wipes its stored keys.
Can the agent make changes in my Stripe or Supabase account?
Only if you switch it on. Supabase, Stripe, and Resend each have an Account Access toggle on their connector page, off by default. Turn it on and the AI can do real account work during builds - create database tables, Stripe products, webhooks, email domains - through server-side tools that never expose your admin keys. Everything it does lands in the Activity feed at the bottom of that connector's page, so you can audit it line by line.
About publishing
Publishing through Appsanic is rolling out. The one-click flow below is how it works: you connect your store account, click Publish, and Appsanic builds and uploads your app for you. While we finalise it, if it is not yet enabled on your account you can publish today by exporting your code and running EAS yourself. We will remove this note when the flow is live for everyone.
How does publishing actually work?
One-click, from inside the build. There is a Publish button in the build top bar. It opens a Publish dialog that walks you through three steps, then tracks progress on a live Status screen:
- Connect. Add your store account with a revocable key (never a password). For Apple that's an App Store Connect API key; for Google it's a Google Cloud service-account JSON. See Publishing to the App Store for the exact key-creation steps.
- Your app. Confirm the app name, the iOS bundle ID / Android package, and the version.
- Publish. Choose App Store or Google Play - each publish targets one store, so being on both stores is two publishes. The dialog shows the exact credit cost before you confirm (set server-side, so it's authoritative), then you confirm to start.
After you confirm, Appsanic builds the release in the cloud with EAS and uploads it for you - iOS to your TestFlight, Android to your Play internal testing track. A status screen shows progress, and a build takes roughly 10 to 20 minutes. No Mac and no command line required. Once it lands, you install it on a real device, then submit for review in App Store Connect / Play Console.
Prefer to drive it yourself? You can instead export your code to GitHub and run Expo Application Services (EAS) from your own repo (eas build, eas submit). That fallback is always available.
Publishing is a paid-plan capability (Pro and Business).
Do I need a Mac to publish an iOS app?
No. Builds happen in the cloud via Expo Application Services (EAS). Whether Appsanic runs EAS for you in the one-click flow, or you run it from your exported repo, you can build and submit to the App Store from Windows or Linux.
How long from starting a project to being in the App Store?
- Realistic minimum with focused work: one week.
- Typical for a first-time launcher: 2-4 weeks.
- Apple review time: 24-72 hours (separate from your build time).
See Publishing to the App Store.
What about TestFlight?
TestFlight comes for free with your Apple Developer Program. Once your build is in App Store Connect, you can share it with up to 10,000 external testers (after a one-time Apple review of the beta version). See Publishing to the App Store.
About billing
Does the free tier give me enough to launch an app?
No. Free lets you step through five template demos to see how the agent plans and builds. Running your own prompts, then exporting to GitHub and taking the app to the App Store via EAS, starts on Pro.
Do you offer annual billing?
Not yet. Billing is monthly only today - every paid plan renews each month, and you can cancel at any time. Annual plans are on the roadmap. When they arrive, the cancellation and refund terms in our Refund Policy and Australian Consumer Law will still apply.
Do you offer refunds?
Not for change of mind or unused portions of a billing period. We do refund duplicate charges, unauthorised charges, and service-level failures. See the Refund Policy for the specifics.
Do you have a student discount?
Not currently.
About trust & security
Is Appsanic SOC 2 certified?
Not yet. See our Security page for what we actually deliver today. Enterprise customers can request a current security questionnaire under NDA.
Can I do enterprise SSO?
Enterprise plans include SAML SSO and SCIM onboarding. Write to contact@appsanic.com to scope a pilot.
Where is my data stored?
- Your code: in your GitHub account.
- Your users' data: in your Supabase project (in the region you chose when setting up Supabase).
- Appsanic's record of your project: US region by default (EU available on enterprise plans).
- Billing records: on Stripe.
- Email-delivery records: on Resend.
See our Sub-processors list for specifics.
Can I delete all my data?
Yes. See Deleting Your Account for the complete flow.
About support
How do I contact support?
Email contact@appsanic.com. It's our single point of contact. Mention what the question's about in the subject line so we route it to the right person. Typical response times:
- General support, enterprise, billing: within 1 business day.
- Security: acknowledged within 48 hours.
- Privacy or data-subject requests: within 30 days per the Privacy Act.
Where's the community?
A Discord server is on the roadmap. Until it's live, the blog, these docs, and the support inbox are the main channels.
Anything else?
If your question isn't here, email contact@appsanic.com. We read every message. If a question comes up often, it ends up on this page.