Appnatively
Appnatively
Knowledge Base
Go to Studio
Knowledge Base
Go to Studio
Getting Started
Welcome to AppNativelyCreate your first appFinding your way around the Studio dashboard
Website Connection
Connect your website to AppNativelyInstall and update the required pluginChoose which plugins power your app“Website Not Connected” – what it means and how to clear itFix a failing or dropped connection
App Editor
Build your app with AI chatWrite prompts that get the screen you wantUndo an AI change you don’t wantEdit screens and components by handManage your app’s pagesDesign your headerDesign your bottom navigationAdd and edit drawersManage your themeHow your changes reach your usersSave vs. Publish – what each one doesWhen a new release is requiredWhen AI gets it wrong
Splash & App Icon
Set your app iconAdd Android Adaptive Icon layersDesign your splash screenRecommended image sizes
Publishing Setup
What you need before your first buildSet your app’s name, slug, and package IDAdd Android credentials and your keystoreAdd iOS certificates and provisioningConnect Google PlayConnect the App StoreSet up Firebase Configuration
Build & Deploy
Connect GitHub before you buildBuild your app – and submit it to the storeFix a failed build
Push Notifications
Create and send a push campaignTrack campaign performanceNotifications aren’t arriving
Integrations
Connect a third-party service

When AI gets it wrong

AI chat gets most requests right, but not every single time. When a result isn’t what you expected, it’s rarely worth starting over from scratch – a small adjustment usually gets you there.

Common reasons a result misses

  • The prompt was vague. “Make it better” leaves a lot open to interpretation. See Write prompts that get the screen you want.
  • The prompt asked for conflicting things. Requests that pull in two directions at once – for example, describing a layout and then asking for something that contradicts it – tend to produce a compromise instead of either.

How to recover

1. Undo, then try again

If the result isn’t usable at all, undo it and re-prompt with more detail. See Undo an AI change you don’t want.

2. Or just describe the correction

If the result is close, a short follow-up prompt describing exactly what’s wrong is usually faster than starting over – “the button is too small” or “wrong image” works fine.

3. Or switch to manual editing for fine detail

For small, precise adjustments – exact spacing, a specific pixel-level tweak – hand-editing is often faster and more reliable than describing it in words. See Edit screens and components by hand.

FAQ

When a new release is required
Splash & App Icon
Was this page helpful?
On this page
Common reasons a result missesHow to recover1. Undo, then try again2. Or just describe the correction3. Or switch to manual editing for fine detailFAQIs it better to write one long, detailed prompt or several short ones?+Should I report results that seem consistently wrong?+