Expo AI @ IntDev
Hi, I'm Brent.
And, I’m an addict. I've been addicted to building for over 30 years.
This is my fourth presentation product.
This talk is a flow.
Running off my iPhone.
No laptop.
30 years building.
MountainZone.com
SkiResorts.com
Mobliss - early mobile content
Treemo -> Treemo Labs
FlowVella → 500K users
Flow Kiosk → museums & retail
Last year I came to IntDev to start it.
“FlowboardAI.” Presentation app reimagined with AI.
Prompt-to-presentation. AI image gen. 1st pass working quickly.
Then last April, life had other plans.
I set it down.
So I built other things.
CompliQuick - security compliance and training for small teams. tahc.ai - live + AI customer chat. Replaced Drift.
Went deeper with AI tools. Mostly Claude Code, last summer. Against 30 years of knowing how to build.
Same room. Same idea. A year later, sharper.
Was ready to finish what I couldn't before.
Now it's Flow2.
February 2026.
Mobile viewer epiphany. Four weeks through Switzerland, France, Santa Cruz.
Building on my phone. For my phone.
Mobile isn't a smaller screen.
Mobile IS the Presentation
So I deleted the desktop editor.
On purpose.
Built portrait-native from scratch.
What a Flow2 flow is
Not slides you shrink.
Screens you scroll.
Built for the device in your hand.
TikTok for presentations
How I build with AI.
SSH → VPS → tmux → Claude Code.
Termius in my pocket. Terminal on the laptop. Build at home. Build at IntDev.
I don't build just at a desk anymore.
On a chairlift. In the woods. Walking.
Wherever. Doesn't matter.
The bottleneck isn't typing.
It's knowing what to build.
AI has changed the game and the craft.
AI inside the product.
AI creates the flows.
Gemini or OpenAI do the image gen.
AI assists. You finish.
This flow? Claude and I discussed, then drafted it via MCP. I shaped every screen.
A true UI. Drag, type, restyle. Not just a chat box.
Most MCP presentation tools are write-only.
Flow2 lets the agent see the screenshot.
Then fix it.
Demo Time
Flow2 creation
MCP Edit
VPS show/tell
Steal these.
How I actually drive Claude Code.
The mechanics
Spec first. Always.
design-system.md → one source of truth.
Doc every session. (CLAUDE.md + linked docs.)
/clear after a feature.
claude -r (is a savior - you can resume a session)
After every feature, ask it:
“Does this match the design system?”
“What's your confidence in this implementation?”
Under 95% → review and revise.
Same room.
Started here a year ago. Set it down.
Came back and finished it.
Still addicted to building.
Now, we start the telling.
flow2.co
