It's not about speed for me. Reading faster forces me to focus, while my mind wanders off when I read slowly.

I read fast and then stop to think about it.

What I took from this is that you have a really engaging writing style. Was interesting to read from start to finish.

I share your opinion about the quality of vibe coded apps. It's definitely not something you can pull off with 0 programming knowledge at this moment. I don't know how the quality of LLM written code will change in the future, but I do believe a lot of custom apps that basically just store and display data can already be easily one-shotted.

The more complex the app becomes, the harder it will be to maintain it with vibe coding. Personally I have chosen to just create specialed apps, that do one thing well, to avoid that complexity.

You don't get localStorage persistence though.

I had the same problem, regarding localStorage synchronization. For that I made htmlsync.io, but only really worth it for people who have many local apps like that and really need the localStorage sync.

This is pretty cool! What kind of users are you targeting? Technical folks or those dipping their toes into dev with vibe coding?

Thanks! Pretty much, yes. Also if you are a dev and just don't want to spin up a server for every simple app you vibe code, you could find this useful.

To be honest, I wanted this for myself and felt guilty not making something more serious out of it since I liked the idea.

You can do that with htmlsync.io

Thank you, I'll take a look.

To be completely honest, I don't see how this is more useful than adding a sync layer to localStorage. I did make a service that does that at htmlsync.io and am genuinely curious how this solution is better.

Just like with https://tiddlywiki.com/

Your notes are the HTML file! You can keep it in your documents folder, sync it via any service, track it in version control, etc. It’s for folks who know what the filesystem is, don’t know how to host a server (or don’t want to), but want a website-like experience. Works offline, too!

So like, Obsidian, but for HTML?

The file itself provides both the dynamic functionality and data storage, but you need an engine (like obsidian) to make the data persistence and dynamic parts work together. I.e. if there is a button that adds a task to a todo app, your engine modifies the HTML file with the new content.

I finally also recalled this project (tiddlywiki), but CMIIW, the statefulness of the hyperclay is only for developers, the end user will get the same conventional html. Without some kind of common solution/protocol/standard on the browser side that would allow persistence it's not so exciting. Theoretically there might be some kind of simple protocol that would save html file versions on the server based on the cookie, but there are so many ways this can go wrong

This is really cool. About to try it out!

I build something along those lines as well. My problem was that I couldn't synchronize localStorage data, so I made htmlsync.io.

Can you share the paper mentioned in the demo video?

I have been doing something very simillar!

Instead of giving it a VPS, I just made a tool that allows synchronization of localStorage data.

I now just upload the HTML it generates and have an app instantly.