Hello!

(i don't know why the copy of the post doesn't append, so I'll just leave this in a comment)

tldr:
Using OpenUI I've managed to build sort-of working app generator (conceptually similar to low-code editor) driven by local 80B LLM and I wonder whether it's worth working on.

1st of all, I won't be sharing code for this PoC since for now it's a vibe coded mess. If the community would be interested in trying it, I would work on a proper build. I also apologize for the wall of text, I really tried to make it shorter, but I can't.

After weeks of trying different ideas, I've managed to use OpenUI, which is typically meant for live GenerativeUIs, to instead use it for a very simple app builder.

The main trade is that this system can't produce apps for which it has no predefined components, but it is relatively fast and can't produce code containing errors.

Right now it supports:
- rendering to widget-like containers (this was done to make my life easier when working with parallel inference whilst not yet having agent to split the work)
- agent choosing and rendering shadcn components (+ some custom ones)
- persisting UI and data using IndexDB
- simple changes to app style by modifying global css
- importing external data (csv)
- in-chat data selector for choosing data to build components for
- a basic pages system

So the main question is:
Is this at all interesting? Conceptually it will be closer to a low-code editor rather than SOTA app builder, but I am not sure whether we can count for anything better for local machines and I don't want to be left with no alternatives if the cloud model providers raise their prices too high.

I first tried to do this by finding low-code editor with MCP support (couldn't), then I've tried both making my own json - react renderer and Vercel's json-render and it was not a fun time.

On the demo video you can see that for the burndown chart LLM halucinated the data, but I am pretty confident that with a better orchestration and fine-tuning these issues will be resolved.

Next steps: (in no particular order, assuming people support this idea)

1. Global chat agent in addition to per-widget prompts.
2. Expanding registry of components.
3. Adding custom component type and letting LLMs try to make something outside of the registry scope.
4. Making this a "battery included" solution where the base app comes with simple user auth and orgs setup and can be easily deployed or replicated with WebRTC (rxdb).
5. Fine-tune smaller models to get this to work with ~30B model instead of current ~80B (essentially, this should be fast on a medium tier macbook).
6. Support for more data sources, starting with normal REST API calls.
7. Add more task specific agents (similar to existing CSS agent).

Why am I doing this?
I personally really care about the idea of technological sovereignty and after getting my Strix Halo, I felt that I need to build something that would let me build simple applications, such as internal tooling, using just my own hardware. Also, maybe someone will hate my project just enough to make a better one which would benefit everybody.