Question 1

How does the automated device testing work?

Accepted Answer

Every build compiles to a real release binary (.apk / .aab) and runs on infrastructure we operate: a real Android emulator on self-hosted hardware and a real iOS Simulator on GitHub Actions runners. An automated crawler exercises navigation, checks 48dp touch targets, captures crash traces and records real screen telemetry.

Question 2

Are screenshots and preview videos captured from real execution?

Accepted Answer

Yes. App Store and Google Play guidelines strictly prohibit simulated or AI-hallucinated app store listings. Every screenshot and video in your release report is captured directly from a real install-and-run on our own infrastructure.

Question 3

Can I test and publish an app I already coded?

Accepted Answer

Yes. Upload any compiled .apk, .aab, or .ipa to instantly run our automated device crawler, generate store-compliant media packs, and prepare App Store Connect and Google Play releases.

Question 4

How does automated App Store & Play Store publishing work?

Accepted Answer

We automate provisioning, signing, asset packaging, and release metadata. Connect your Apple Developer ($99/yr) or Google Play ($25) credentials, and we push straight to TestFlight and the Play Internal Testing track.

Question 5

Do I need my own Apple Developer and Google Play accounts?

Accepted Answer

Yes. Store guidelines require apps to be owned by your own developer account — we don't pay for or provision these for you. Once you connect access, we handle the entire build, upload, and release workflow.

Question 6

Can I test and publish an app I built in Studio?

Accepted Answer

Yes. Studio apps compile to a real .apk/.aab and go through the same device-testing pipeline as block-assembled apps. Publishing currently happens in the Burgndy app, which handles both paths — Studio doesn't have its own separate submission flow yet, only a working handoff to the existing one.

Question 7

Is Burgndy.ai the same thing as "Burgundy AI"?

Accepted Answer

Yes. Burgndy.ai is the stylized domain spelling of the same name — most people say, type and search for it as "Burgundy AI." It is one product, an AI app builder, and either spelling gets you here. It is unrelated to other projects that happen to share the name "Burgundy AI."

Question 8

Where does my user data, database, and payments live?

Accepted Answer

Cloud Firestore for your database, Firebase Authentication for sign-in, Razorpay for payments. Real infrastructure, not a toy backend — apps run on a shared Burgndy-operated project today, with a dedicated-project option on the roadmap.

Question 9

How much can I actually customize?

Accepted Answer

It depends on the path. Block-assembled apps are built from a fixed, hand-audited library of feature modules — customization is bounded to what's in that catalog (branding, content, and which modules you include). Studio has no such ceiling: describe anything, and the AI agent writes real source code for it, the same as a developer would.

Question 10

Is there a good alternative to Emergent, Bolt.new, or Lovable for building a real native app?

Accepted Answer

Yes, if you need a compiled Android/iOS binary rather than a browser or Expo preview. Emergent and Bolt.new preview mobile apps through Expo on a physical device, and Lovable is web-only by its own docs. Burgndy.ai compiles a real .apk/.aab (+.ipa), tests it on emulator and Simulator infrastructure, and submits through the real store pipelines.

Question 11

Why choose Burgndy.ai over a standalone device-cloud vendor?

Accepted Answer

Device clouds charge $199+/month just for testing seats — and that's on top of whatever you're already paying for code generation, build infrastructure, and backend setup. Burgndy.ai runs the whole chain — architecture, backend, automated device testing, store publishing — on one flat plan.

Question 12

Can I get the real source code, or am I locked into Burgndy.ai?

Accepted Answer

For apps built in Studio: yes — real Flutter or Node source, pushed straight to a GitHub repo under your own account, so any developer can pick it up and keep building outside Burgndy.ai entirely. For block-assembled apps, you get the real compiled .apk/.aab today; a source export for that path isn't available yet.

Question 13

Can I self-host Burgndy.ai, or hand a project off to my own developer?

Accepted Answer

Burgndy.ai itself is a hosted platform, not something you self-host. But a Studio app's real source lives in your own GitHub repo, so your own developers can take it over at any point — you're not dependent on us to keep building it.

Question 14

What do the pricing tiers actually limit?

Accepted Answer

A published monthly credit pool. Every action — an AI mockup, a device test, a Studio session, a real app build — costs a set number of credits, and the exact costs and your live balance are on the Billing page. If you run out mid-month you can buy a top-up pack or upgrade; nothing is silently throttled.

Question 15

Is there a free tier?

Accepted Answer

Yes. Free gives you 60 credits a month — enough to generate and compile one real, complete app end-to-end, or try a handful of AI-generated mockups first (5 credits each). No card required.

Build real mobile apps with AI. App Store ready.

Watch a real app build & run.

Blueprints

Course Platform & Student Academy

Auramax Headphone Showcase

Modern E-Commerce Boutique

More blueprints, ready to use.

Real apps. Not a website in disguise.

Buttery Smooth

Tested on Real Phones

Backend, Already Wired

$14 / mo

Idea to app in three steps.

Describe it

Watch it build

Test, then ship

4 tools. 1 price: $14/mo.

Stop Paying 4 Bills

Frequently asked questions.

Your idea, shipped today.