Manifesto

Community-Driven Development.

How Vibalos actually gets built.

I'm not building Vibalos from roadmap slides or quarterly OKRs. I'm building it on the principle that has served me best as a vibe coder: disciplined dogfooding. Use it every day. Note every friction. Fix every bug. Add every missing feature. And every issue the community files on GitHub flows straight into the next build.

Eat your own dog food — with receipts.

I use AI tools every day, intensely. Here are the real numbers from 12 months of Wispr Flow — my dictation tool, same DNA as Vibalos: local, fast, always in the menu bar.

1,235,713
Words dictated
in 12 months
115 wpm
Speaking pace
Top 33% globally
49 days
Current streak
Longest: 285 days
34,552
AI prompts
93% of all dictation

Source: my own Wispr Flow insights. Vibalos gets the same intensity — every day, every bug, every feature.

How the loop runs.

From issue to release in the tightest possible cycle.

01

Issue or discussion on GitHub

You file a feature request, bug, or question on the public repo. Issue templates guide you — I usually reply within 24-48h.

02

Triage onto the roadmap

I check the tracker daily. Whatever I also need — which is plenty — lands on the roadmap immediately. What doesn't fit gets an honest explanation.

03

Build in the daily driver

I build features in the Vibalos instance I use myself. If it scrolls past me, it doesn't ship. If it works, I know by lunch the next day.

04

Release via Sparkle, immediately

Auto-updates via Sparkle, signed with EdDSA. You usually get the next version within the same week — sometimes the same day.

What you get, what I won't promise.

Promised

  • → Reply on every issue (24-48h pre-launch, fastest possible after)
  • → Frequent releases — multiple per week during active development
  • → An honest "no, this doesn't fit the vision" when warranted
  • → Lifetime updates for your license, one Mac
  • → No cloud, no telemetry, no accounts — today and in the future

Not promised

  • · A specific release date for any given feature
  • · A support SLA with response-time guarantees (solo dev)
  • · Open source — not for now (see the repo README)
  • · Multi-Mac license (might come as a second tier, but not today)
  • · Windows or Linux — Mac-only by design

Ready to shape it?

Open an issue or start a discussion — the roadmap is listening.

Watch on GitHub