Show HN: Generate Web Interfaces from Data

This is interesting. So here, your app generates data, and you use AI to decide how to render those data.

This is similar to, but not the same as, the approach taken by json-render: https://github.com/vercel-labs/json-render

The latter assumes AI generates the data AND picks the components it will use from your predefined library.

If I'm reading this correctly, caching only happens if I give it a stable cache key? If that's true, this just seems like an insanely bad decision. I've seen waaaay to much bad React code to think that that isn't a massive foot-gun.

1. That combined with hot reloading just makes me think some jr dev is going to forget to put that there while they're building something locally and burn through their LLM budget without even knowing it.

2. What happens if the cache key changes. Is there any way to migrate from one key to another? Let's say I'm using user ids as the cache key and you need to do a migration that changes the format of the key, is the existing design just gone forever?

3. Does anyone even want a non-deterministic UI? Don't get me wrong, it's a cool for a demo, but I can't think of anything that would annoy me more than coming back to a website and every week it looks different.

Sorry to be a downer, but man, I just really struggle with this. If this is just kind of a cool hobby project then you can ignore #3, but for 1 and 2 I really feel like it'd be a better to do something like have a data attr for the prompt and then have component generation be something a user kicks off through a script or something.

Generative UI has a lot of potential, and some of the ideas here are interesting, but the positioning as a developer tool (for folks that can just generate stable UI using claude code already) seems odd to me. What's the expected use case?

I'm interested in exploring the ideas here for on-the-fly output based on user intent. It reminds me a bit of the schema model I used for the LangView experimental library (https://x.com/rupertmanfredi/status/1653780093712633859).

The magic eight ball of UI.

Not usable enough? Just refresh! No, we don’t know how many times you’ll need to do that.

I was hoping this might be a syntax or very very lightweight markup that could feed LLM generation of UI rather than just roll the dice to see what UI gets generated every time.

But why would anyone do this? The UI will obviously change unpredictably on every generation, there's no way to deliver quality control if the UI is generated on the fly.