OUI-1: world's first model for Generative UI(openui.com) |
OUI-1: world's first model for Generative UI(openui.com) |
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.
It too is just software
Seems like many AI products ride the same wave now. Open WebUI, OpenHands, OpenUI. I am a bit more dubious about this affiliation, though.
The html/css/js or a react app built by an LLM is not Gen UI.
...i like.
---
- Design system / Component lib
- Live view of what components, tokens, other things... on the left side of the screen.
- You're in the meeting and talking while talking and transcribing and doing the full duplex voice. You say, "Find what tables and customizations we have available" and the list starts to filter to tables and customizations.
- "Let's add that table to the page; left side; 3/4 width of page. Headers should be static for vertical scroll, ..."
- The table is added to the page.
- "Nah, i don't like it. Let's change that table component to have larger headers..."
yes, i like--let's see what Astra Pro pops out with.
Having said that, imo, Gen UI only makes sens as a presentation layer - not controls. Unless LLM will be using a set of very well defined and homogenic components like table, forms, small widgets.
Imagine a very small LLM embedded into a MetaMask equivalent where you just specify the task you want to do - ie, "I want to send USDT on mainnet", "I want to import the token at address 0x..." - and the wallet assembles the UX for this task for the human to execute.
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, etc. in the old PHP code. A lot of that complexity can simply disappear.
Having dynamically built UI won't only be better for the user experience, it can actually allow us to create much more personalized experiences (I hate when UI teams constantly redesign perfectly fine software).
Interestingly, this will open up a completely new consumption interface, because I believe there will be a UI predefined by the creator of the application (your day 1 user experience) that will then evolve into a more personalized experience over time.
So much room to grow in this space.
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?
I'm amazed that this blog doesn't even have a single screenshot/photo of the kind of UI they can generate.
Focusing on benchmarks in this domain feels very wrong.
Typing this comment also did not solve your problem, because that would require the author to read your comment, add more screenshots and it would require that you revisit it.
I don't know what media you are talking about. It's all slop worse than current slop.
It's generally for letting users customize the own workflows. How many times have you, or one of your users, liked a piece of software because it mostly fits an existing workflow but that remaining 20% is an annoyance, or maybe even a dealbreaker?
This is probably more common for businesses. They have existing procedures. and they want your software to fit into their existing processes and workflows... not the other way around.
GenUI is far from a one size fits all approach or magic bullet, but it can address a lot of those situations that either would have been dealbreakers, annoyances, or change requests. I suppose it can also help with user retention; once they've put the time and effort into customizing your product they theoretically are less likely to switch to a competitor.
Existing OpenAI/Anthropic models seem to already handle this pretty well. As you might expect, letting users describe their own UI is pretty easy. The hard part is making it work and making sure they don't escape their sandbox...
Of course pushing users toward subscription services they don’t need is part of the design goal. So I guess something where the user vibecodes up their own UI will not become standard. But we can dream.
It's also the only sentence I read on that page before closing it, of course.
Congrats! Now you need to relearn it every time you open the app.
IFs! Oh no! Throwing all of this into a non-deterministic and expensive black box is making it less complex, you say?
To take this a step further: https://chatjimmy.ai/
Imagine AppLess running a model as good as qwen at 20,000 tok/sec. It would be generated in a shorter amount of time as downloading a webpage right now. If this works out the consequences are kind of scary. The end of SaaS, the end of software being the moat or the property of companies, the embolstering of data protection (since that's fundamentally what code operates)...
> I hate when UI teams constantly redesign perfectly fine software
... with ...
> 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
In this scenario there's still no guarantee that the UI won't randomly change. There's no guarantee that the ui generated for the user will be the same visit to visit.
These are inherently contradictory statements.
When people actually did research instead of vibe-coding, they learned it the hard way.