Live data from Hacker News

OUI-1: world's first model for Generative UI

openui.com

21–30 of 68 posts

Re: OUI-1: world's first model for Generative UI

#21

> Interfaces must be generated in under a second Why? Is two seconds too long? Would your other constraints be easier (usability and hardware spec) if this was longer? Does anyone actually need a UI generated in under a second?

The term "Generative UI" refers to a front-end design approach where an AI model dynamically builds a UI in real time instead of relying on static, hard-coded templates.

Re: OUI-1: world's first model for Generative UI

#22

Quite interesting to see no real comments here for 50+ minutes, so I will kick it off. I'm a huge believer in this future of software. Having the UI layer completely abstracted from pre-written code and dynamically generated "on the fly" based on the context of the user is, I believe, the future. Just think about the complexity of localization and how many IFs you had to write to solve different language versions, et…

this exactly the future we are working towards as well. You should checkout AppLess http://github.com/thesysdev/appless

Re: OUI-1: world's first model for Generative UI

#23

Do you hate the designer changed the UI of your favorite app so you have to relearn it every three months? Congrats! Now you need to relearn it every time you open the app.

Nothing stops you from caching known states and workflows, or simply making the "fast" part of your interface fixed. I think this could be genuinely useful for one-off cases for which no interface exists, or simply for interface prototyping and design.

Re: OUI-1: world's first model for Generative UI

#24

It should be possible to run on Mac via https://github.com/mmastrac/diffgemma , but I'm at rustconf right now and I can't download weights on hotel wifi easily.

let me try this out as well

https://github.com/mmastrac/diffgemma#custom-quantization has some instructions on (naively) quantizing the upstream model as well.

Re: OUI-1: world's first model for Generative UI

#25
The most interesting part about this for me is that they decided to create their own language or DSL for the task at hand. So it's not just a large language model; it's an LLM with its own language.

I have a feeling that the best AI systems to come will, in fact, be a complete package like this: a harness, a DSL, and an entire package designed to produce certain outcomes cheaper and faster.

And producing that complete package is why software engineering will not be obsolete.

Re: OUI-1: world's first model for Generative UI

#26

Do you hate the designer changed the UI of your favorite app so you have to relearn it every three months? Congrats! Now you need to relearn it every time you open the app.

I can think of one use case for this: Dashboards to answer one-off questions. Think PowerBI, Tableau, etc.

Re: OUI-1: world's first model for Generative UI

#27

Do you hate the designer changed the UI of your favorite app so you have to relearn it every three months? Congrats! Now you need to relearn it every time you open the app.

Another way to think of this is you just ship the UI DSL, and the user can get the app to customize it themselves with built-in guardrails. Everything should be LCARS at this point.

Re: OUI-1: world's first model for Generative UI

#29

Do you hate the designer changed the UI of your favorite app so you have to relearn it every three months? Congrats! Now you need to relearn it every time you open the app.

The goal of generative UI should be to make software more personal while preserving the workflows people already know. Two users might have very different interfaces, but each should have a consistent experience over time.

I can only imagine the troubleshooting and customer support experience. Yet another problem created by “ai” that’s probably only solvable with more “ai”

Re: OUI-1: world's first model for Generative UI

#30

Quite interesting to see no real comments here for 50+ minutes, so I will kick it off. I'm a huge believer in this future of software. Having the UI layer completely abstracted from pre-written code and dynamically generated "on the fly" based on the context of the user is, I believe, the future. Just think about the complexity of localization and how many IFs you had to write to solve different language versions, et…

I agree somewhat. An example might be a .md file describing a UI for commonly used tool that is invoked whenever you reference it. This could be a stripped down version of a complex UI for some software that has a lot of different uses (like 3D modeling programs and image editors) allowing the user to focus on the subset of work they do with it.
Post reply on HN