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.
@rivendell_chorro Thanks! 🙏 The ones that really push it are the apps doing heavy lifting on the device itself, like a sports app that takes an uploaded video and runs detection on it, tracking every joint frame by frame to break down someone's mechanics.
Or the live ones, think a fleet platform pulling real time GPS off a bunch of drivers, optimizing routes across dozens of stops and firing geofence alerts as vehicles move. That stuff stacks a lot of hard problems into one app, on device vision or live data, a real processing pipeline, and a web of integrations behind it that all has to stay in sync and still feel seamless to the user.
Getting those to come together through the step by step build instead of one giant prompt has been easily the most satisfying part so far 💪
Report
Congrats @manil_lakabi1 How's it different from Rork in practice? Both promise real iOS apps without code.
@boyuan_deng1 Yeah, surface level the promise is similar. The biggest difference is how X1 thinks about building the app.
We try to emulate how a strong product team actually works: figure out what should happen, make the product decisions, design the screens, build that piece, test it, then move on.
AI accelerates each of those steps instead of pretending they can disappear.
So rather than “describe your whole app and hope the model gets it right,” X1 works through it with you piece by piece and keeps those decisions connected as the product evolves.
That’s really the bet: AI should compress the product development process, not remove it.
Report
I like that you are asking for brutal feedback! what kind of feedback has surprised you most during development?
@james_carter35 Well there hasn't been much pushback on this new way of building an AI builder, most people are genuinely intrigued by the more controlled approach.
But honestly, during early development the thing that surprised me most was how much people pivot mid build. I kind of assumed folks would come in with a fixed idea and follow it through, but what actually happens is they get a few milestones in, see it running on their phone, and go "actually, no, let me change this core thing." and at one point it was frustrating to see people start with building an e-commerce system and pivot to a live streaming app for some reason (it still triggers a form of PTSD when I remember dealing with that lol) At first that felt like worst case.
But it's really a byproduct of the thing X1 is actually built around, which is keeping all the context of your app present without it eating up or plaguing your future decisions. Once that context holds, a pivot stops being scary, because changing one core thing updates what depends on it instead of quietly breaking the rest of the app. So it reframed how much that foundation matters.
Quick question: How does this compete with Rork? https://rork.com and glaze by raycast https://www.glaze.app/ ? how do you differentiate? or a better question whats better or different with x1?
@conduit_design Glaze is a bit different since it’s focused on Mac apps. Rork is the closer comparison.
The easiest analogy is building a house.
Rork is more like telling a really fast construction crew, “Build me a 6-bedroom house,” and they start building.
X1 first asks who’s living there, where the bedrooms should go, what matters to you, etc. Then it makes one blueprint and builds the house piece by piece against that blueprint.
Both can build the house. Our bet is that the blueprint + process matter a lot once you start changing things.
If you move a bedroom later, X1 should understand that the plumbing, hallway, electrical, etc. might need to change too instead of just moving one wall.
Report
the ask focused questions approach sounds smart! what happens when a user gives X1 an unclear or contradictory requirement?
@barnaby_lloyd If something is unclear, it asks a narrower question. If two requirements conflict, it surfaces the conflict and makes you choose before it keeps building.
The rule we’re trying to follow is basically: assume the cheap/reversible stuff, ask about the decisions that can break the app later.
Report
Congrats on the Launch! I know from building mobile apps that the biggest return on your build comes from the iOS app users. Is this why you chose to focus on iOS only?
Report
could X1 take an existing app idea and help redesign the entire user experience from scratch?
Congrats! 👏 quick question : What was the hardest type of app you’ve built with X1 so far?
x1
@rivendell_chorro Thanks! 🙏 The ones that really push it are the apps doing heavy lifting on the device itself, like a sports app that takes an uploaded video and runs detection on it, tracking every joint frame by frame to break down someone's mechanics.
Or the live ones, think a fleet platform pulling real time GPS off a bunch of drivers, optimizing routes across dozens of stops and firing geofence alerts as vehicles move. That stuff stacks a lot of hard problems into one app, on device vision or live data, a real processing pipeline, and a web of integrations behind it that all has to stay in sync and still feel seamless to the user.
Getting those to come together through the step by step build instead of one giant prompt has been easily the most satisfying part so far 💪
Congrats @manil_lakabi1 How's it different from Rork in practice? Both promise real iOS apps without code.
x1
@boyuan_deng1 Yeah, surface level the promise is similar. The biggest difference is how X1 thinks about building the app.
We try to emulate how a strong product team actually works: figure out what should happen, make the product decisions, design the screens, build that piece, test it, then move on.
AI accelerates each of those steps instead of pretending they can disappear.
So rather than “describe your whole app and hope the model gets it right,” X1 works through it with you piece by piece and keeps those decisions connected as the product evolves.
That’s really the bet: AI should compress the product development process, not remove it.
I like that you are asking for brutal feedback! what kind of feedback has surprised you most during development?
x1
@james_carter35 Well there hasn't been much pushback on this new way of building an AI builder, most people are genuinely intrigued by the more controlled approach.
But honestly, during early development the thing that surprised me most was how much people pivot mid build. I kind of assumed folks would come in with a fixed idea and follow it through, but what actually happens is they get a few milestones in, see it running on their phone, and go "actually, no, let me change this core thing." and at one point it was frustrating to see people start with building an e-commerce system and pivot to a live streaming app for some reason (it still triggers a form of PTSD when I remember dealing with that lol) At first that felt like worst case.
But it's really a byproduct of the thing X1 is actually built around, which is keeping all the context of your app present without it eating up or plaguing your future decisions. Once that context holds, a pivot stops being scary, because changing one core thing updates what depends on it instead of quietly breaking the rest of the app. So it reframed how much that foundation matters.
DiffSense
Quick question: How does this compete with Rork? https://rork.com and glaze by raycast https://www.glaze.app/ ? how do you differentiate? or a better question whats better or different with x1?
x1
@conduit_design Glaze is a bit different since it’s focused on Mac apps. Rork is the closer comparison.
The easiest analogy is building a house.
Rork is more like telling a really fast construction crew, “Build me a 6-bedroom house,” and they start building.
X1 first asks who’s living there, where the bedrooms should go, what matters to you, etc. Then it makes one blueprint and builds the house piece by piece against that blueprint.
Both can build the house. Our bet is that the blueprint + process matter a lot once you start changing things.
If you move a bedroom later, X1 should understand that the plumbing, hallway, electrical, etc. might need to change too instead of just moving one wall.
the ask focused questions approach sounds smart! what happens when a user gives X1 an unclear or contradictory requirement?
x1
@barnaby_lloyd If something is unclear, it asks a narrower question. If two requirements conflict, it surfaces the conflict and makes you choose before it keeps building.
The rule we’re trying to follow is basically: assume the cheap/reversible stuff, ask about the decisions that can break the app later.
Congrats on the Launch! I know from building mobile apps that the biggest return on your build comes from the iOS app users. Is this why you chose to focus on iOS only?
could X1 take an existing app idea and help redesign the entire user experience from scratch?