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.<p>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.<p>And producing that complete package is why software engineering will not be obsolete.
I agree. I'm waiting for someone to invent a programming language designed for LLMs where for a given partial program p and candidate token t it's possible to tell whether p+t can be the prefix of a correct program or not so that t can be excluded from the LLM's probability distribution at generation time, so the LLM can only generate correct programs. Or something like that.
Do you hate the designer changed the UI of your favorite app so you have to relearn it every three months?<p>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.
I can think of one use case for this: Dashboards to answer one-off questions. Think PowerBI, Tableau, etc.
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.
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”
> The goal of generative UI should be to make software more personal while preserving the workflows people already know.<p>These are inherently contradictory statements.<p>When people actually did research instead of vibe-coding, they learned it the hard way.
Chat Ui killed the GUI star. language is The ultimate UI. I guess you still need graphs (mainly so you can have dramatic moments in movies), but that's it
That's why I have my own model restyle the delivered UI to my preferred UI.
You missed the point, it's not for you to write.
[dead]
Remember when everything was iSomething? The original iPod and iPhone created the real trend then.<p>Seems like many AI products ride the same wave now. Open WebUI, OpenHands, OpenUI. I am a bit more dubious about this affiliation, though.
OpenAI, OpenAPI and now OpenUI. Explain this to a non tech person...
It should be possible to run on Mac via <a href="https://github.com/mmastrac/diffgemma" rel="nofollow">https://github.com/mmastrac/diffgemma</a>, but I'm at rustconf right now and I can't download weights on hotel wifi easily.
Quite interesting to see no real comments here for 50+ minutes, so I will kick it off.<p>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.<p>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.<p>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).<p>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.<p>So much room to grow in this space.
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.
How do you reconcile ...<p>> I hate when UI teams constantly redesign perfectly fine software<p>... with ...<p>> 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<p>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.
this exactly the future we are working towards as well.
You should checkout AppLess
<a href="http://github.com/thesysdev/appless" rel="nofollow">http://github.com/thesysdev/appless</a>
Great link, I haven't seen that before. I saw someone at Microsoft make an "OS" that was just copilot chats per-window, generating the HTML. I recreated it and it's not great, but it's a fun toy that _feels_ transformative, unlike almost every AI product ever made besides the fundamental chat interface.<p>To take this a step further: <a href="https://chatjimmy.ai/" rel="nofollow">https://chatjimmy.ai/</a><p>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)...
> 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.<p>IFs! Oh no! Throwing all of this into a non-deterministic and expensive black box is making it <i>less</i> complex, you say?
Generative UI is unsolved because current models do not have taste and end up generating the same kind of slop.<p>I'm amazed that this blog doesn't even have a single screenshot/photo of the kind of UI they can generate.<p>Focusing on benchmarks in this domain feels very wrong.
Gen UI is meant to be design agnostic, the output is just the content and the form. It is on the implementation, agentic or human to make it look good.
There's an image in the article and a full website with more media is just 1 click away. Instead you resorted to typing 272 characters not including ENTER, and I doubt that was easier than clicking the logo to visit the homepage.<p>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.
Someone steel man the case for users actually wanting to be a UI designer for the application they pay you for.
GenUI isn't about designing cosmetic "skins." (Usually, anyway. I guess it could be used for that)<p>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 <i>mostly</i> fits an existing workflow but that remaining 20% is an annoyance, or maybe even a dealbreaker?<p>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.<p>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.<p>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...
> Interfaces must be generated in under a second<p>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.
In Generative UI, the interface needs to built in realtime based on context and intent of the user. Hence the constraints. Ideally we are targeting sub 500ms to compete with current software.
I get annoyed if a webpage takes longer than 1-2 seconds to generate right now. You don't?
[dead]
Oui ma chérie
Please for the love of god have a human write something that you expect other humans to read
Oh no.
oh, you eye?