u/Chemical_Emu_6555

I connected my project to Vercel via CLI, clicked the “Enable Analytics” button…

and instantly got real user data.

Where users came from, mobile vs desktop usage, and bounce rates.

No complex setup. No extra code.

That’s when I realized: 69% of my users are on mobile (almost 2x desktop).

It made sense.

Most traffic came from Threads, Reddit, and X — platforms where people mostly browse on mobile.

So today, I focused on mobile optimization.

A few takeaways:

• You can’t fit everything like desktop → break it into steps

• Reduce visual noise (smaller icons, fewer labels)

• On desktop, cursor changes guide users → on mobile, I had to add instructions like “Tap where you want to place the marker”

AI-assisted coding made this insanely fast. What used to take days now takes hours.

We can now ship, learn, and adapt much faster.

That’s why I believe in building in public.

Don’t build alone. I’m creating a virtual space called Build In Live, where builders can collaborate, share inspiration, and give real-time feedback together. If you want a space like this, support my journey!

#buildinpublic #buildinlive

I built a product management tool for solo builders called Vibounder, would love your feedback.

Most PM tools like Linear or Notion are designed for teams. As a solo builder, I found them too heavy and slow. I wanted something lightweight that actually fits how we build today, especially with AI in the loop.

So I built Vibounder: an AI-native workflow that takes you from idea → structure → execution.

Here’s how it works:

1. Lean Canvas (Start with thinking, not coding)
A lot of indie builders jump straight into building without validating the fundamentals: business model, competition, channels, etc. Vibounder guides you through this first, so you don’t waste time building something no one needs.

2. User Stories (Clarity over chaos)
Yeah, it sounds boring, but knowing what not to build is just as important. Vibounder turns your Lean Canvas into structured user stories with acceptance criteria, like a proper agile team (but powered by AI).

3. Kanban Board (Focus on now)
Vibe coding is great, but it’s easy to get lost. Vibounder generates a Kanban board directly from your strategy and user stories, so you always know what to work on next — without losing context.

4. PRD (Better inputs → better outputs)
A PRD makes or breaks your MVP. Vibounder generates good one for you based on everything above, so you get a solid foundation by default.

5. MCP (Coming soon)
I’m working on syncing the Kanban board in real time as you build, so updates happen automatically instead of manually tracking everything.

It’s still an MVP, so there’s a lot to improve.

I’d really appreciate your feedback, especially from other solo builders:

Does this workflow make sense?
What feels unnecessary or missing?
Would you actually use something like this?

I’m also testing a real-time feedback tool where I can see your cursor and exactly where you leave comments (free to use).

No mobile version yet, desktop only for now.

Thanks in advance 🙏

Day 9 — Building in Public: Mobile First 📱

[Feedback Request] AI-native PM tool for solo builders