📌 I built a code snippet manager because I kept losing my own code (MVP live)

#webdev #productivity #showdev #development

Over the last 18 days, I built something small called SnipRepo — a clean, fast way for developers to save, organize, search, and manage their code snippets.

I didn’t plan to turn it into a product. It started because I was constantly running into the same problem:

I’d write a useful piece of code… use it once… and then lose it forever inside old repos, random notes, or unsynced files.

Eventually, the frustration piled up enough that I just built my own solution.

This post isn’t a “launch announcement.”
It’s simply me sharing what I built, how I built it, and what I learned along the way.

If you're a developer who deals with a lot of snippets, this might resonate with you.

🚀 What SnipRepo does (MVP scope)

Here’s what the MVP includes today:

Save snippets with title + description
Tag system for quick organization
Search by title, content, or tags
Syntax highlighting
Clean, minimal UI focused on speed

Pro-only features

Version history
AI features (summaries / explanations)
Embed snippet
No snippet limit

It’s intentionally simple — it solves the exact pain I had.

🛠️ Tech stack & architecture

I kept the stack lightweight so I could ship fast:

React + Vite for the frontend
Supabase for auth, database, RLS, and storage
PostHog for event tracking
TailwindCSS
Syntax highlighting via Prism

Everything is modular and easily replaceable.

🔍 What I learned building this MVP

Building tiny tools is underrated You don’t need a big idea — just a painful problem, even if it’s your own.
Clean UX beats heavy features Developers don’t want complexity. They want speed, clarity, and control.
Launching is scarier than building Shipping publicly feels 10× scarier than writing code. But feedback > perfection.
Free tiers matter a lot
A simple usage limit gave me:
cleaner UX
easier onboarding
better conversion path

📸 Screenshots