Frequently asked questions

Build iOS and Android apps such as booking tools, habit trackers, community apps, travel planners and business apps. Use Studio to build and edit, connect services, test a native preview and prepare a store release with the publishing agent.

RNBlocks is designed for React Native mobile apps, not large 3D or open-world games like GTA. Simple quizzes, puzzles and turn-based experiences are more suitable starting points. Games that need a 3D world, advanced physics or real-time multiplayer need a dedicated game engine and specialist development.

You can start by describing your idea in plain language, try the result and ask for changes. More complex features can need a developer’s help. Test your app before sharing or publishing it.

Yes. New accounts currently receive 100 promotional AI credits with no credit card required. This is a one-time signup offer, subject to the promotion terms, and does not refill each month.

Yes. Continue in the same Studio conversation to ask for focused changes, review the result and test it again. Open your saved app to pick up where you left off.

On a computer, choose iOS or Android in the Studio preview, or use My Device for the phone instructions. On your phone, switch to Preview and use Open with Expo Go. Some native capabilities require a development or testing build.

The connector guides cover Supabase, OpenAI, Anthropic / Claude, Groq, Replicate and ElevenLabs. Use them for features such as accounts, saved data, AI responses, generated images or voice, then test the actual feature in your app.

Providers have their own pricing, usage limits and billing. Your app’s provider usage is separate from RNBlocks credits used to build the app. Connecting a service does not buy its plan.

Open your saved app in Studio and choose Publish. Tell the publishing agent whether you want to test on a phone, invite testers or prepare a store release. The workspace keeps settings, store details, screenshots and build results together.

The accounts depend on your platform and testing or release destination. The direct build path uses Expo; Apple distribution uses the appropriate Apple developer and App Store Connect setup, while Google Play distribution uses a Play Console developer account. Account verification, app records and signing are separate steps.

No. Preparing a release, submitting it, passing store review and making it public are separate states. Check the store’s status and your release settings after submission.

Both paid plans include the same Studio toolset. Pro costs $15 per month with 150 monthly credits; Studio costs $29 per month with 400 monthly credits.

Active Pro and Studio subscribers can buy 50 credits for $5, 150 for $15 or 350 for $30. Monthly plan credits reset each billing cycle. Top-up credits carry over while you remain subscribed; remaining plan and top-up credits are removed when the subscription ends.

It can. Credits pay for actual work already performed, even if a request fails or you stop it. Unused reserved credits return when usage is settled.

Pending credits are temporarily set aside for work in progress or usage still being checked. If a request is interrupted, final usage may not be known immediately. A pending reservation is not a final charge.

Auto-reload is optional for eligible paid accounts. Choose a threshold and pack, then save the setting to authorize automatic purchases as recorded usage reduces your balance. It can make repeated purchases and is not a monthly spending cap.

Yes. Open Profile → Plan → Manage to review cancellation. A scheduled cancellation keeps the plan active until the end of the billing period; check the effective date and remaining credits before confirming.

Yes. With an active Pro or Studio plan, choose Download .zip in Studio, or Options → Download .zip on a phone. The exported app may still need its database and connected services, so verify those features outside Studio.

Yes. You can use the app source you generate for your own projects and client work, including commercial apps, subject to RNBlocks terms and applicable third-party licenses. Review rights for assets, packages and content you add.

Keep the app and conversation open, note the visible error and check what completed before retrying. Use the troubleshooting guide to find the right next step, or contact support with reproducible steps and the approximate time. Keep passwords and API keys out of the message.