X1 is an AI app builder that takes you from an idea to an iPhone app you can publish on the App Store. Instead of trying to generate the entire app from one prompt, X1 guides you step by step. It asks focused questions, designs each screen for you to review and edit, then builds the app in stages. Preview and test it on your iPhone as you go. When it’s ready, X1 prepares your App Store listing, screenshots, and submission. No coding required.
@barnaby_lloyd The "ask focused questions approach" is exactly for the situation you typed out. It actually starts right at the beginning in the idea phase, where X1 has a proper back and forth with you and does a feasibility pass on what you're describing, so contradictions and unclear bits get caught before anything gets built. When something's unclear or two requirements clash, X1 flags it and talks it through with you instead of quietly picking one and running with it.
It'll surface the contradiction, explain the tradeoff and let you decide, and for the smaller stuff (the decision on whats small and whats not is on you btw, its not a point of failure in X1, we accounted for that lol) that's obvious or easy to change later it just makes a reasonable call and keeps moving so you're not stuck answering a hundred questions.
The whole point is catching the ambiguity early, through that back and forth, before it turns into a bunch of assumptions baked into your app that you only notice 20 changes down the line.
Report
I like the idea of reviewing each screen before building! can users completely customize the generated designs?
@imogen_wallace Absolutely. You can customize pretty much every part of the generated design theme, fonts, colors, spacing, styles, individual components, and the smaller UI details too. The generated screens are meant to be a starting point, not something you’re locked into.
@abod_rehman Definitely more back-and-forth. We try to only ask when the answer would meaningfully change the app or create downstream decisions. If something is obvious or easy to change later, X1 just makes a reasonable call and keeps moving.
The questions are also based on your app and previous answers, so it shouldn’t feel like filling out the same form every time. The goal is basically to catch ambiguity before X1 turns it into a bunch of assumptions you discover 20 changes later.
@justin2025 That’s exactly the failure mode we’re trying to avoid.
If you pivot, X1 treats the old decisions as things to re-evaluate, not sacred memory. It updates the plan/underlying decisions, figures out what actually needs to change, and keeps the parts that are still valid instead of rebuilding everything from scratch.
The goal is for memory to preserve context, not trap you in it.
Report
this is an interesting take on AI app building! does X1 support apps that require login and personalized user data?
@olivia_bennett7 Yeah it does. Auth and per user data are core to most real apps so X1 handles that path directly, supporting apple sign in right off the bat. It sets up user accounts on the backend so each user gets their own data, then wires the screens to that instead of faking it with placeholder content. It also treats those as real product decisions, so it'll ask how people should sign in and what data belongs to a user, then build the flows around it. You end up with something that actually persists and personalizes, not just a demo that looks logged in lol
I’ve used X1 in the weeks leading up to this launch and it’s great. Their approach to building production grade iphone apps is both unique and actually got me to a finished / polished app.
@alan_dweck man this means a lot. honestly the best part of building X1 has been seeing someone actually get all the way to a finished app instead of getting stuck at the “almost there” stage lol. appreciate you taking the bet on us early 🫡
the ask focused questions approach sounds smart! what happens when a user gives X1 an unclear or contradictory requirement?
x1
@barnaby_lloyd The "ask focused questions approach" is exactly for the situation you typed out. It actually starts right at the beginning in the idea phase, where X1 has a proper back and forth with you and does a feasibility pass on what you're describing, so contradictions and unclear bits get caught before anything gets built. When something's unclear or two requirements clash, X1 flags it and talks it through with you instead of quietly picking one and running with it.
It'll surface the contradiction, explain the tradeoff and let you decide, and for the smaller stuff (the decision on whats small and whats not is on you btw, its not a point of failure in X1, we accounted for that lol) that's obvious or easy to change later it just makes a reasonable call and keeps moving so you're not stuck answering a hundred questions.
The whole point is catching the ambiguity early, through that back and forth, before it turns into a bunch of assumptions baked into your app that you only notice 20 changes down the line.
I like the idea of reviewing each screen before building! can users completely customize the generated designs?
x1
@imogen_wallace Absolutely. You can customize pretty much every part of the generated design theme, fonts, colors, spacing, styles, individual components, and the smaller UI details too. The generated screens are meant to be a starting point, not something you’re locked into.
Triforce Todos
Curious how X1 decides what to ask you vs. what to just assume. Does it feel like a real back-and-forth or more like a form?
x1
@abod_rehman Definitely more back-and-forth. We try to only ask when the answer would meaningfully change the app or create downstream decisions. If something is obvious or easy to change later, X1 just makes a reasonable call and keeps moving.
The questions are also based on your app and previous answers, so it shouldn’t feel like filling out the same form every time. The goal is basically to catch ambiguity before X1 turns it into a bunch of assumptions you discover 20 changes later.
Mom Clock
What happens if you want to pivot halfway through, does it rebuild cleanly or does the "memory" start working against you?
x1
@justin2025 That’s exactly the failure mode we’re trying to avoid.
If you pivot, X1 treats the old decisions as things to re-evaluate, not sacred memory. It updates the plan/underlying decisions, figures out what actually needs to change, and keeps the parts that are still valid instead of rebuilding everything from scratch.
The goal is for memory to preserve context, not trap you in it.
this is an interesting take on AI app building! does X1 support apps that require login and personalized user data?
x1
@olivia_bennett7 Yeah it does. Auth and per user data are core to most real apps so X1 handles that path directly, supporting apple sign in right off the bat. It sets up user accounts on the backend so each user gets their own data, then wires the screens to that instead of faking it with placeholder content. It also treats those as real product decisions, so it'll ask how people should sign in and what data belongs to a user, then build the flows around it. You end up with something that actually persists and personalizes, not just a demo that looks logged in lol
Beacons
I’ve used X1 in the weeks leading up to this launch and it’s great. Their approach to building production grade iphone apps is both unique and actually got me to a finished / polished app.
x1
@alan_dweck man this means a lot. honestly the best part of building X1 has been seeing someone actually get all the way to a finished app instead of getting stuck at the “almost there” stage lol. appreciate you taking the bet on us early 🫡
x1
The best product you can use for shipping real working iOS apps without knowing how to write a single line of code