The AppNatively App Editor is where your app actually gets designed – screens, navigation, look and feel, all of it. Build by hand with ready-made components, or connect an AI assistant like Claude or ChatGPT and describe what you want: its changes appear here while you watch, and you can adjust everything by hand. It’s the part of AppNatively most people spend the most time in, and the part that decides what your users actually see.
What you can do in the App Editor
Build screens by hand, or design them with an AI assistant and refine the result – most people use both, each for what it’s best at. The AI side has its own section: Design with AI (MCP). From there you build out the structural pieces: the pages that make up your app, the header that sits across them, the bottom navigation your users tab through, slide-out drawers like cart and filter, and a theme that sets your colors, fonts, and spacing everywhere at once.
The last few articles cover getting your work to users – what Publish actually does, how it differs from Save, and the one situation where a change needs a new store submission instead.
Before you start
The App Editor won’t open without a working website connection – your screens are built from your connected site’s content. See Website Connection if you haven’t set that up, or if you’re seeing a full-screen “Website Not Connected” message.