--- title: What vibecoders build on Vibecodr | Games, tools, art, and experiments description: A tour of what vibecoders actually build with vibe coding on Vibecodr: creative coding, games, little tools, data visualizers, interactive fiction, and experiments — each a live app anyone can open, remix, and follow. canonical: https://vibecodr.space/use-cases --- # What People Build ## Games, tools, art, and weird little experiments. Vibecodr is where people ship the runnable stuff: a physics toy, a tiny tool, a generative sketch, an interactive story, a half-finished idea worth poking at. If it runs in a browser, it has a home here — and a link anyone can open in one click. Not a category of builder so much as a place for live software with people around it. Publish what you made, let people run and remix it, and keep evolving the same vibe instead of losing it in a pile of dead links. ## Start here ### Creative coding: Generative art, shaders, and sketches that move. Flow fields, particle storms, audio-reactive canvases, a single weird WebGL idea at 2am. Press play and the thing is alive on the page — no setup, no 'download to view,' just the sketch running for whoever opens it. ### Games & toys: Playable prototypes people can actually play. A physics puzzle, a tiny roguelike, a one-button arcade game, a fidget toy you cannot stop poking. Share the link and someone is playing in seconds — then forking it to add their own level. ### Little tools: Small utilities that beat a spreadsheet. A unit converter, a regex tester, a color-palette picker, a JSON formatter, a 'does this fit in a tweet' counter. The kind of tool you would normally bookmark — except this one you can open, use, and change. ### Data & visualizers: Datasets you can feel, not just read. Turn a CSV into a chart that breathes, an interactive map, a sortable table with real annotations, a sound you can scrub through. Numbers become something a person can poke at and understand by using. ### Interactive fiction: Stories, zines, and explainers you click through. A choose-your-path story, a scrollytelling piece, a playable explainer for a hard idea, a love letter as a tiny website. Words plus interaction, living at a link instead of trapped in a PDF. ### Experiments & apps: Half-ideas and little internal apps that earn their keep. A standup timer for your team, a habit tracker just for you, a proof-of-concept you will throw away next week, a thing you built only to see if it could work. Some stay toys; some quietly become real. ## How it works in practice ### It runs at a link: Publish once and it is a real app on its own page. Whatever you made opens instantly for anyone, on any device — the working thing, not a screenshot of it. That alone is enough for a lot of vibes. ### People remix it: Others fork your build and take it somewhere new. A toy becomes ten variations, a tool gets a feature you would never have added, and the credit stays attached to you the whole way. ### It keeps evolving: BUMP IT ships the next cut to the same page and link. One public home for the project instead of a graveyard of near-identical links. Older cuts stay around, and the people following it just see it get better. ### It earns a backend: Add a Pulse the day the project actually needs one. When a vibe wants saved scores, a webhook, a scheduled job, or a private API key, drop in a Pulse — and never before. Most things never need it; the ones that do do not have to start over. ## Keep exploring - [Examples: Explore live vibes](https://vibecodr.space/discover) - [The model: How it works](https://vibecodr.space/how-it-works/index.md) - [Backends: The power of Pulses](https://vibecodr.space/power-of-pulses/index.md) - [Scale: Plans](https://vibecodr.space/plans/index.md) ## FAQ ### What can I actually build here? Anything that runs in a browser: games, generative art, little tools, data visualizers, interactive stories, prototypes, internal apps. If it is HTML, a React component, a static site, or a whole repo, it can become a live vibe people open in one click. ### Do I need to know how to code? No. If you can paste what an AI assistant wrote, you can publish a working vibe and share it. And if you do code, nothing is hidden — bring a whole repo and wire up a real backend. ### What if it is just a tiny experiment, not a real product? Perfect. Most of what people ship here is small on purpose — a toy, a sketch, a half-idea. Putting it in front of people while it is alive and changing is the whole point. Some stay toys; some grow up. ### Can I build serious, production-ish tools too? Yes. Plenty of vibes are genuinely useful day to day. Start with the working browser experience, learn from real use, and add a Pulse for secrets, storage, or scheduled work when the project earns it. ### What happens when someone remixes my vibe? They get their own copy to build on, and the link back to your original stays visible. You keep the credit, and your idea keeps moving forward in the open instead of getting quietly copy-pasted into the void. ## Closing note The short version: if the best way to understand your thing is to open it, poke at it, and maybe remix it, Vibecodr gives it a public home with people around it. Start tiny, share the link, and add a backend only the day the project earns one.