Why I Built Snipps: A Place for Experiments

I built Snipps because I like the moment when an idea becomes something you can see and use. For a long time, that moment felt reserved for people who already knew how to code. You had to learn the languages, understand the tools, and get comfortable with all the small details between wondering if something could exist and making it work.

AI has changed that distance. People who never thought of themselves as programmers are now making tiny apps, playful tools, visual experiments, and things that do not have a name yet. They are turning “I wonder if…” into “look what I made.” I find that genuinely exciting.

The code is how the experiment gets made, but the experiment is what people come to share.

Experiments need a home §

Many of these creations disappear almost as soon as they are made. They stay inside a conversation, sit in a local folder, or live at a temporary link with no context. They are often too small, strange, unfinished, or personal for a portfolio. They are not products, and they do not need to become products to be worth making.

That in-between space is what interests me. A tiny interaction can teach you something. A rough idea can give someone else a starting point. A visual toy can make another person curious enough to try building their own.

I wanted a place where those things could be shared while they are still alive: somewhere you can see the result, understand the idea, and try changing it without starting from an empty file.

Why Snipps §

Snipps is a social playground for experiments. You can make a Snipp, share it with other people, and discover what they are trying. If something catches your eye, you can fork it and make it yours while keeping a clear connection to the original person and idea.

That loop—make, share, discover, change, learn—is the part I care about most. The editor and preview help an experiment exist, but the people around it are what help it travel. A Snipp can be a finished demo, a useful technique, a first attempt, or a question someone is exploring in public.

What belongs here §

Maybe it is a tiny app that solves one problem, a button with an unexpectedly nice animation, a visual experiment, a small website for a very specific interest, or a tool you made to understand something better. Maybe it is simply the first version of an idea you are not sure about yet.

You do not need a polished portfolio, a startup plan, or years of experience. You do not have to know exactly what you are building before you begin. Snipps is for the things that are useful, playful, curious, or just worth showing to someone else.

Sharing an experiment also makes the process a little less solitary. Someone might notice a detail you missed, explain a different approach, or take the idea somewhere you would not have taken it yourself. Even a quiet, unfinished project can become part of a conversation.

It is not a replacement for the tools teams use to ship production software. It is a smaller, lighter place for making things visible and giving them room to grow. The goal is to make editing pleasant, discovery meaningful, and make it easy to build on one another’s work without losing where an idea began.

Come play with it §

I built Snipps because I think making things should feel like a playground—especially now that more people can take part. I am still figuring out what Snipps should become, and I expect the best direction will come from the experiments people choose to share.

If you have made something small, odd, useful, or unfinished, bring it along. Share the thing you tried. Fork something that makes you curious. Let someone else change it and see where the idea goes next.