FAQ
Questions, answered straight.
Native iOS. Human-feeling. Built in minutes on real Macs — with proof you can review and source you keep.
What is Native Made, in one line?
Custom, scalable, human-feeling native iOS apps built in minutes. Today that means one idea → agents → a real Xcode compile. At scale it’s a portfolio generation and validation platform — so teams can explore dozens of directions without burning cognitive capacity or Mac hardware.
Is this really native iOS, or another web wrapper?
Native SwiftUI, compiled with Xcode on real Mac hardware. No embedded browser, no React Native bridge, no cross-platform shell. You leave with a standard Xcode project — the same kind of app you’d open and ship yourself.
Will the apps feel human-built, or like generic AI output?
Human-feeling is a hard requirement, not a slogan. Apps should follow a logical path, keep layout errors minimal, and land above “AI slop” — HIG-aligned patterns, intentional typography and assets, not a one-template look. The quality bar is: planned functionality works, navigation makes sense, and product teams can review proof without guessing.
Who is this built for?
Teams and operators who need high-volume MVP generation under real constraints — limited attention across many products, and limited Mac fleet for parallel builds. It’s also for founders and studios who want a polished native MVP without standing up an iOS team first. The common pain: too many directions to try, not enough bandwidth or hardware to try them.
Do I need a Mac?
No. Builds run on hosted Macs in the cloud. That removes the hardware bottleneck so you can work from anywhere, and so volume isn’t capped by your office RAM or local Xcode fleet. You still download a full Xcode project when you want to continue locally.
What do I get as proof that it actually built?
Not a mockup deck. A successful run gives Simulator screenshots of the main screens, run and build logs, and a downloadable Xcode project. If it doesn’t compile, the run fails out loud — we don’t dress up a broken build as a preview.
Can I explore many app directions quickly?
That’s the north star: explore dozens of directions in minutes, then scale the ones with signal. Alpha ships the single-project flow end to end. Niche batching and shared scaffolding per niche — generating variants fast while saving credits — are on the roadmap for portfolio-scale teams.
How much do I have to specify up front?
Minimal input by design. Describe the niche and the idea in plain language. Integrations and API keys only when you need them. Agents handle planning, design, and SwiftUI; the Mac handles the compile. You review proof and keep the source.
Who owns the code, and can I maintain it later?
You do. Exports are plain Swift in a standard Xcode project — open it, change it, ship it. There’s no runtime lock-in to Native Made. That matters for long-term maintenance: the app isn’t trapped in a generator; it’s a real codebase you can keep.
What does it cost?
Pro is $49/month for 3 app generations. Max is $200/month for 10. Every plan includes the full agent pipeline, hosted Mac compiles, screenshots, and Xcode export. Cancel anytime — exported source stays yours.
Still curious? Run one build.
The pipeline explains itself better than any FAQ.