From idea to iPhone app
with David Alonso, Bloom
From idea to iPhone app
Show Notes
There is a moment in every founder's journey where they realize the map they were given was wrong. The old map said: have an idea, find a developer, wait months, launch, iterate. David Alonso, co-founder of Bloom and ETH Zurich robotics graduate, is handing founders a new map - one where the distance between idea and working product is measured in minutes, not months.
David didn't plan to build Bloom. He planned to build robots. But somewhere between reinforcement learning research and quadrupeds, he fell in love with the tight feedback loop of app development. He and his co-founder went through Y Combinator, closed a $3.5 million round before Demo Day, and built a product that left investors texting their friends mid-demo saying it was the best tech demo they had ever seen.
This episode is the story of what happens when you decide the bottleneck is not code. It is imagination.
The Core Problem Bloom Is Solving
Building a mobile app used to take David and his co-founder four months from idea to having it on someone else's phone. For a non-technical founder, the timeline was effectively infinite. Bloom collapses that timeline to minutes by combining three opinionated technology choices:
- •Expo as the front-end framework - one codebase deploys to web, iOS, and Android simultaneously.
- •Convex as the backend - real-time sync between devices out of the box, full type safety, and a database that works without configuration.
- •App Clips as the distribution layer - an underutilized Apple feature that lets anyone open a fully native app from a single link with no App Store visit, no TestFlight, and no invite code.
When Ryan built a caffeine tracker live during recording using two words as a prompt, the app came back with intake logging, a seven-day history chart, an FDA recommendation display, and an editable database. In about three minutes.
Frameworks from This Episode
These frameworks have been added to the AI for Founders Frameworks Library. Filter by David Alonso to find them.
The Garden of Apps
Stop renting software. Start growing it. One database you own, connected to every app you build.
- •Audit your SaaS stack: which tools hold data you should own but don't?
- •Build a unified database that all your apps read from and write to.
- •Replace scattered SaaS platforms with custom apps sharing one data source.
- •Your workout data, expense tracker, habit logger, and AI assistant can all share context.
- •Full code access and full data portability - no paywalls, no lock-in.
The Founder Operating System
Use the same platform for your product and your internal tooling - then eventually let it run operations.
- •Build your user-facing app and your internal tooling on the same stack.
- •Prototype new features as standalone apps, validate with real users, then merge into your main repo.
- •Eventually deploy virtual employees that handle operations within the same environment.
- •One platform: your product, your ops, your team.
The Opinionation Advantage
Being more opinionated than your competitors is a feature. Constraints enable reliability.
- •Choose a constrained stack and commit to it - fewer variables means fewer AI mistakes.
- •Complex features like real-time sync become one-prompt operations when the stack is purpose-built.
- •Non-technical users benefit most: they don't need to understand the architecture at all.
- •Evaluate your own product: where is your constraint actually a competitive advantage?
The Creator Economy for Software
What YouTube did for video, AI app builders will do for software. The ceiling is orders of magnitude higher.
- •Media democratization created formats that didn't exist before - vlogging, TikTok, Reels. Software democratization will do the same.
- •The new app formats AI tools will unlock don't have names yet. Build early.
- •The addressable market is 7 billion phones, including billions who have never had laptop access.
- •Ask: what would you build if you could ship an idea in 3 minutes instead of 4 months?
Founder Experiment: Build Your First Internal Tool This Week
Pick one internal tool your team currently pays for or is debating adopting - a time tracker, expense logger, password manager, meeting notes tool. Instead of signing up for another SaaS product, open Bloom and describe what you actually need in plain language.
- 1Identify one internal tool you are currently paying for or evaluating. Give it three non-negotiable requirements.
- 2Open Bloom and describe the tool in one or two sentences. Add your three requirements as constraints.
- 3Let the agent build. Don't touch the code - just describe what's missing or wrong and iterate.
- 4Share the result with one teammate via the App Clip link. Watch them open a native app from a single tap.
- 5Note: how long did it take? What does this app do that the off-the-shelf version doesn't? How does it feel to own the data?
Stretch goal: Look at your SaaS bill and ask: what else on this list could I build in an afternoon? The answer might surprise you.
Tools from This Episode
Bloom
AI-powered mobile app builder. Go from a text or voice prompt to a native iOS, Android, and web app - with authentication, real-time backend, and App Clip sharing - in minutes. $3.5M raised. Best tech demo investors had ever seen.
Key Terms
These terms have been added to the AI for Founders Glossary. Search by David Alonso to filter them.
Q&A
What is Bloom and what does it do?
Bloom is an AI-powered app builder that lets anyone - no coding experience required - create fully native mobile apps for iOS, Android, and web by typing or speaking an idea. The app includes authentication, a real-time backend, and instant sharing via App Clips, all generated automatically.
How is Bloom different from Lovable, Replit, or Cursor?
Bloom is more opinionated. It is built exclusively on Expo for the front end and Convex for the backend, giving its AI agent clear guardrails that produce more reliable results. Lovable does not support native mobile apps. Replit offers less backend opinionation. Cursor requires managing your own stack entirely. Bloom's App Clip sharing experience - going from a build to a native app on a stranger's phone in seconds - has no direct equivalent.
Can I own my code and data in Bloom?
Yes. Bloom gives users full access to their source code, downloadable as a zip file or synced to GitHub on the pro plan. All data is visible and editable through Bloom's built-in database viewer. You are never locked in - you can always modify the code or export it.
How does App Clip sharing work?
When you build an app in Bloom, you share it via a single link. When someone taps that link on an iPhone, iOS loads an App Clip - a lightweight native container - and Bloom side-loads your app into it. The recipient gets a fully native experience with no App Store visit, no TestFlight, and no invite code. Updates propagate to all users nearly instantly.
What is the vision for Bloom beyond app building?
David describes Bloom evolving into a founder operating system - a platform that hosts not just a company's user-facing product but all internal tooling, connected to a shared data layer. The long-term vision includes virtual employees handling business operations from within Bloom, and a personal computing model where individuals own a unified database connected to a garden of custom apps, replacing commercial SaaS entirely.
How did Bloom raise $3.5 million before YC Demo Day?
The fundraising was driven by the live demo. David would build something in a few prompts, send a link, and the investor would have a fully functional native app on their phone seconds later with real-time sync visible between devices. Investors described it as the best tech demo they had ever seen and made direct introductions to other investors mid-week.