Apps
iPhone, iPad, Mac and Android apps: screens, features, design, builds and fixes.
How Apps worksAn AI team on your computer. It turns an idea in plain language into a game for Steam, iPhone or the browser, or an iPhone, Mac, Android or web app. Then it writes the store listing, runs the launch and reads your sales reports every morning.
Invited beta on macOS. Windows and Linux are coming soon. Apps built with Neo are on the App Store.
One sentence becomes concept art, then a game that runs: Godot, Unity or Unreal for Steam and PC, iPhone, Android or the browser.
Built, installed in the simulator and played, start to finish. These are those recordings.



Othertoolsstopwhenthecodecompiles.NeostopswhenyourappisintheAppStore,onGooglePlay,online,orexportedforSteam.
You never pick a module. Neo reads the request, picks the right one, and says why. When it is unsure, it asks instead of guessing.
Every picture below is Neo itself. One chat drives every module; you watch the team and approve the money.

After every build Neo opens what it made in a real browser, simulator or emulator, uses it the way a person would, and films it. These are those recordings, unedited.
No hunting through files. Point at the part of the running site, app or game you want different, and Neo changes that part.
Boxes, arrows and a few words on a canvas are enough. Neo reads the sketch and builds the level, the page or the app.
Browse examples built on the patterns top designers made popular: motion, layouts, colour, type and game feel, for the web, iPhone and Android. Each one runs live. Copy the prompt, copy the code, or tell Neo to use it in your project and it fits your colours and fonts.
Filter by iPhone, Android or the web, or by motion, layout, colour and type. Every card plays live.
Open one to watch it run, see where it fits, and read the code for SwiftUI, Compose, React Native or the web.
Copy the prompt for any AI chat, copy the code, or send it to Neo. It reads your project’s palette and fonts and fits it in.
A real recording from the Neo app: the grid, the iPhone filter, Copy prompt, then Use in my project for an Android app, with its own colours in the message. Click to enlarge.
The library updates from one signed feed, so every Neo user sees the same examples. Updates are free.
Anythingthatspendsmoney,publishessomethingordeletessomethingstopsandasksyoufirst,withthepriceonthebutton.
All 18 modules, each one moving: a real recording from the app where we have one, otherwise a recreated panel of the same turn. What it does, what you type, and what you have at the end.
Describe the app in one sentence. Neo answers with a card of choices (iPhone, iPad or Mac, the kind of app, the look, the features) with its own suggestion already picked, so you can just press Build. The team writes a native SwiftUI app, a Kotlin app for Android, or one React Native codebase for both phones. Every build is compiled, installed in the simulator or emulator and toured screen by screen before you see it.
How Apps worksA real recording from the Neo app. One sentence, the choices card, the build, and the app running in the iPhone simulator.
You never pick one. Neo reads the request, picks the right module, and says why.
iPhone, iPad, Mac and Android apps: screens, features, design, builds and fixes.
How Apps worksGame projects: characters, sprites, animation, tilesets, effects, levels, builds.
How Game Dev worksGit, GitHub, code search, tests, changelogs and code review.
How Code and repo worksSupabase and PocketBase; Firebase, Neon, Nhost and Upstash in beta: tables, access rules, settings, webhooks.
How Backend and database worksPictures, video, sound, music, icons, logos and 3D models; the gallery and documents.
How Media and gallery worksGoing live and the cloud: Vercel, Cloudflare and Fly.io; Netlify, AWS, GCP, Azure and Sentry in beta.
How Deploy and hosting worksApp Store and Play Store submission, TestFlight, ASO, store details, market research, legal pages.
How App Store and ASO worksStripe or Lemon Squeezy checkouts in what you build, subscriptions, billing, plans and licences.
How Payments and licensing worksAd creatives, ad films, social posts, publishing and campaign plans.
How Ads and social worksA virtual influencer: persona pictures, talking videos, reels, a consistent look.
How Influencer (Persona) worksPush and email campaigns for your users, and notification settings.
How Push and email worksSales, downloads, revenue, app analytics, daily and weekly reports, unusual changes.
How Analytics and sales worksKanban boards, to do lists, sprints, teams and feedback.
How Tasks and team worksNeo's agents: memory, skills, training data, local models and workers.
How Agents, models and training worksFlows: step by step processes and approval requests.
How Flows and approvals worksTalk to your sessions from your phone: speech, dictation, spoken replies.
How Voice console worksConnections and keys, your account, updates, logs and costs.
How Settings and system worksLotsoftoolsmaketheproduct.Nobodyhelpsyousellit.
Neo keeps working after the build. It calls back the people who ask, researches your market, and runs the checks you would forget.
Say the sentence and Neo answers with concept art. Pick one and it becomes the project’s canon: every sprite, tile and scene after that matches it. The game is built in Godot, Unity or Unreal and released for Steam and PC, iPhone and Android, or the browser.

Three paintings with a pitch each. The one you pick sets the palette and style.

The hero, drawn with the six locked colours and the silhouette from the canon.
Work in progress, shown as it is today.
Ashen Sutra, an action RPG in development. Characters, fights and skills in real animation.
Ten levels and a boss. Halloween all October, dusk over the hills the rest of the year: the same levels, a new look, switched by the date.
Collect original player cards, pick a formation, scout the opponent and watch the match play out live.

A 2D pixel action platformer built through Neo’s game module and lane workflow. Next Fest is the target.
A fox in an autumn forest. Every run, jump and dash is animated, and the Owl King is right behind you.

The concept chosen on a Neo card became this project’s canon. The hero sprite was made from it in one turn.
If you can describe it, the team can build it, and tell you honestly where it is still in beta.
Native apps with subscriptions, push notifications and App Store submission. Three are on the App Store today.
Full stack web apps with auth, payments and real time features. One click to Vercel or Cloudflare, Netlify in beta.
Native or cross platform Android builds with Google Play publishing. In beta: builds work, publishing is being proven.
2D and 3D games from concept art to a playable level. With Godot, Neo edits the scene live. Released for Steam, phones or the browser.
REST and GraphQL APIs with auth, rate limits and docs. Databases with security rules, deployed where you host.
Assistants, chat features, pipelines and bots built into your product, using cloud models or ones that run on your computer.
Coding is step two of eight. Here is the whole road an app or a game travels inside Neo: what happens, which modules work, what you approve, and what you hold at the end of each step.
You describe the product in one message. Neo researches the market and the competitors and drafts a short product brief. For a game, it paints three concepts and locks the one you pick as the visual canon.
Anything that spends, publishes or deletes stops and asks first, with the price on the button. Your yes is tied to that exact call, once.
The agents work without your API keys in reach, and most of their work runs in a sandbox on your computer that cannot read your private folders.
Every site and app is scanned before it ships. A secret key in the code stops the release and says where it is.
Code stays on your computer. Data lives in your own Supabase and hosting. Bring the Claude or ChatGPT plan you already pay for.
Everyone else sells the moment code appears on screen. Neo’s job ends when your product is in customers’ hands.
Other tools stop when the code compiles. Neo stops when your app is in the App Store, on Google Play, online, or exported for Steam, icons, legal pages and screenshots included.
A marketing team writes and checks the listing, makes launch clips and posts, plans campaigns. An account manager reads your daily reports and flags what changed.
Concept art, then a locked visual style, then matching sprites and tiles, then the game in Godot, Unity or Unreal (live in the editor with Godot), released on Steam, phones or the browser.
Any step that spends money, publishes something or deletes something stops and asks you first, with the price on the button. Estimates come from real measured calls.
Code and data stay on your computer. Plug in the Claude or ChatGPT and Codex plans you already pay for, so heavy use doesn’t cost you twice.
What went wrong and how it was fixed becomes a rule the team checks next time. The tenth app ships faster and cleaner than the first.
Checked against each product’s own documentation in September 2026.
| Neo | Lovable | Bolt.new | Replit | Cursor / Claude Code | Codex | Superapp | Rosebud AI | |
|---|---|---|---|---|---|---|---|---|
| Web apps | Writes code* | Writes code* | ||||||
| Native iPhone and Mac apps (Swift) | Expo, code only | Expo | Writes code* | Writes code* | ||||
| Android apps | Beta | Expo, code only | Expo, no Play publish | Writes code* | Writes code* | |||
| Games in a real engine (Godot, Unity, Unreal) for Steam, phones, web | Writes code* | Writes code* | Partial | Browser only | ||||
| Submits to the App Store for you | Guided | |||||||
| Store listing checked against review rules | ||||||||
| Launch clips, social posts, campaign plan | Partial | |||||||
| Reads your daily sales and crash reports | ||||||||
| Price shown before every paid step | ||||||||
| Runs on your computer, uses your own AI subscriptions | Runs locally | CLI runs locally, ChatGPT plan | Mac app | |||||
| Watch the team work, role by role |
The fastest way to a web app with a database. Its output is a website or a PWA; getting into the App Store needs a third party wrapper.
Neo builds the native iPhone and Mac app itself and submits it.
Web apps plus cross platform mobile through Expo. Bolt hands you the code (no signed build); Replit walks you through submission, iOS only.
Neo builds native Swift apps, handles the store, and keeps working after launch.
Superb tools for developers. Their agents write and edit the code across your project; you run it, build it and ship it.
Neo is for the person who wants the product. It also uses those same models under the hood.
OpenAI’s coding agent, in the terminal, the IDE and the cloud. It writes and edits code, runs tests in a sandbox and can open pull requests.
Neo can put Codex on your team as the coder, then takes the build to the store, the launch and the daily reports.
The closest competitor: native Swift apps and automated App Store submission, with ASO tools.
Neo adds games in a real engine (Godot, Unity, Unreal), web and macOS, cost approval on every step, your own AI accounts, and reporting after launch.
Make a game by chatting, and it runs in the browser. No native export, no engine project you own.
Neo builds in Godot, Unity or Unreal: you own the project and release to Steam, phones or the web.
* The agent writes and edits the code, and can run it and its tests. Building the store binary, submitting it and running the launch stay with you.
“Expo” means cross platform React Native, not native Swift. Something changed? Tell us and we’ll correct the table.
The team uses the services you already have an account with. Nothing is published to them without your approval on screen.
Neo is a Mac app, but every action is also a command. Script it, put it in CI, or drive it from your phone.
The one chat, the office, the cards, the Godot canvas. Runs the orchestrator on your machine; your code never leaves it unless you publish.
Every module as a command with --json output: start a turn, approve a step, check readiness, read a report. Uses the same bearer token as the app.
Voice console: talk to your running sessions from the iOS app, get spoken replies, approve steps on the go.
Neo’s orchestrator runs on your computer. Heavy work like local models, builds and batches of assets can be handed to other machines you own: a second Mac, a Linux box, a cloud GPU, even an iPhone running the Neo app in worker mode. Each one takes tasks over a private connection and returns results. Nothing is exposed to the internet.
What it means for you: a small studio can run big local models without renting servers, and the cost of AI generation drops to electricity for the jobs that fit on your own hardware.
Status: the iOS worker mode and the mesh exist and are tested in house. They ship after the macOS beta, so the panel in the app says “coming soon” today. We only list it because it is real.
Designed, built, published and marketed through Neo.
This site, neotheapp.com, was built and deployed by Neo as well. Games in progress are in the Games section.