I have been working on a small tool called Orivo.
The idea came from a very simple problem I kept running into: sometimes I do not need a full project setup just to test a small frontend idea.
Sometimes I only want to build a quick UI section, try a layout, make a small HTML/CSS/JS prototype, and send it to someone for feedback.
For bigger projects, using a full local setup makes sense. VS Code, Vite, GitHub, Vercel and all the usual tools are great for that.
But for small prototypes, the setup can sometimes feel bigger than the actual task.
So I built Orivo as a simple browser workspace for frontend prototypes.
It is not meant to replace VS Code, CodePen, StackBlitz or any other tool. Those tools are already good at what they do.
I wanted Orivo to focus on a smaller use case:
building and sharing small frontend prototypes quickly.
What it does
Right now Orivo includes:
HTML, CSS and JavaScript editing
live preview
project-based workspace
shareable links
snapshots
export to HTML, JSON and ZIP
The goal is to keep the workflow simple:
Create a project.
Write some HTML, CSS and JS.
Preview it.
Share it.
Export it if needed.
That is basically the whole idea.
Who I think it could help
I think it could be useful for:
frontend developers testing small ideas
freelancers creating quick client previews
students learning HTML, CSS and JavaScript
designers experimenting with UI sections
small teams that need to show a simple frontend concept
It is not built for large production apps.
If a project needs routing, backend logic, authentication, testing, deployment pipelines, or a full framework setup, then a proper development environment is still the right choice.
Orivo is more for the smaller moments when you just want to build and show something quickly.
One thing I learned
While building it, I realized that adding features is easier than removing them.
It is tempting to add everything: frameworks, npm packages, AI, database support, team features, deployment and more.
Some of those ideas might be useful later, but I tried to keep the first version focused.
The question I kept asking was:
Does this make small frontend prototyping faster?
If not, I tried not to add it yet.
I would like feedback
I am still improving the product, so honest feedback would help a lot.
If you work with frontend prototypes, how do you usually share them?
Do you use CodePen, StackBlitz, CodeSandbox, GitHub Pages, Vercel previews, screenshots, Loom videos, ZIP files, or something else?
And what usually annoys you in that workflow?
If you have a minute, you can try Orivo here:
I would especially appreciate hearing what feels confusing, unnecessary, missing, or slow.
That kind of feedback is more useful to me than just positive comments.
Thanks for reading.
— Dilshod
Top comments (1)
Small question for frontend developers:
When you need to share a quick HTML/CSS/JS prototype with a client or teammate, what do you usually use?
CodePen, StackBlitz, Vercel preview, GitHub Pages, screenshots, Loom, ZIP files, or something else?
I’m trying to understand real workflows, especially for freelancers and small teams.