Tips, updates, and stories for vibe coders.
We're retiring the Docker self-hosting path for the VibePing dashboard. The SDK stays open-source and is being relicensed MIT. Here's the honest version of what's changing and why.
Week 2 recap — Next.js migration, funnel analysis API, AI feedback widgets, loading skeletons, and our test suite hit 219 tests across the monorepo.
How VibePing tracks what matters without cookies, fingerprinting, or consent banners. A look at the technical choices behind cookieless analytics.
Pageviews tell you who showed up. Custom event tracking tells you what they actually did. Here's how to use vibeping.track() to measure signups, CTA clicks, and checkout funnels in your vibe-coded app.
Google Analytics is the default choice. But for indie developers shipping with Lovable, Bolt.new, or Cursor, it might be the wrong one. Here's an honest comparison.
Your Lovable app looks fine. No error screens. No crashes. But users are bouncing, signups aren't converting, and you have no idea why. Here are the 5 silent killers.
A step-by-step guide to adding analytics, error tracking, and web vitals monitoring to your Lovable app — with a single script tag.
Bolt.new lets you ship fast, but you're flying blind once it's live. Here's how to add analytics, error tracking, and web vitals to any Bolt.new app with one script tag.
Stop juggling Google Analytics, Sentry, and UptimeRobot. One line of code gives you analytics, error tracking, and uptime monitoring.
LCP, CLS, FID — what they are, why Google cares, and how to track them in your vibe-coded app without reading a single spec document.
VibePing's first week recap — we built an SDK, dashboard, 5 API endpoints, AI-powered insights, and shipped it all to production. Here's everything that happened.
You built an app in 30 minutes with Lovable. But do you know if anyone's using it? If it's crashing? If your signup flow works?
Why we built the analytics platform vibe coders actually need.