3 ms·

3 Fronts are mentioned: 1. Agentic systems 2. Digital core 3. Generative UI Generative UI seems interesting to note as it's presented here as a way to creat

by dpflan 2y ago

3 Fronts are mentioned: 1. Agentic systems 2. Digital core 3. Generative UI Generative UI seems interesting to note as it's presented here as a way to create personalized UIs. Which means... that Generative AI creates a UI for each user? What are the implications of such a world? How does support work with this? How does a knowledge base get created to educate customers? How do you have a standardized way of discussing the UI?

yawnxyz 2y ago
Yes! The simplest and most direct and useful implementation Generative UI is to have a settings / form react to the context — e.g. an email form, or a bunch of sliders. I have a zod-based form schema, and set of forms and schemas. If there's a new schema (e.g. if I want to add name and comments) I can just have the AI generate and save a new schema, and the UI will know how to handle the changes. This makes updating interfaces really easy. (this is personalized to the dev) For UIs generated per user, ideally you'd have a lot of guardrails around what it's able to generate and what the underlying data and use case is. I haven't built any of this in production yet, but I think accessibility may get a boost. Some video games already have a "verbose mode" for new players, and a "bare bones" mode for players who already get the mechanisms. One might consider building an "explanation" layer where some of the concepts can be explained to the user dynamically, and some more complex options can be either revealed under an "advanced mode" or when the UI determines the user "understands" the underlying concepts, as not to overwhelm them. I'm currently experimenting and designing/thinking through some bioinformatics (gene annotation) tools with this approach, but it's early days.
- gcr 2y ago
  This sounds exceedingly unintuitive. Users hate having settings change / appear and disappear. It sounds like it would make interfaces broadly unteachable and difficult to document.
- epiccoleman 2y ago
  > "bare bones" mode for players who already get the mechanisms. I've wanted this in monster hunter for years. Spare me the cutscenes and dialog and just gimme a menu full of quests so I can decide which monster I want to fight without having to listen to a damn audiobook.
- apsurd 2y ago
  sounds like a bike shedder's dream. While i think it's possible that contextualized UX has value, it's seem way too easy for builders to go ham doing what they love: building more things. i'm a cursor LLM editor convert. Pretty amazing. Thing is, being capable of building N versions of a thing doesn't mean it's a good idea. Technical debt has gone up dramatically on a team of 2. And its not realistic that higher iteration velocity will yield the greatest version. easy to say but you need data and users to test through all of them. that's not happening in real life.
- geogod42 2y ago
  you are not taking the concept far enough gen UI could look like a completely custom interface integrating hundreds of apps to one. that is if an Agentic system is completely multi-modal it can collect all digital information the user owns (in a safe way ofc) but that means when an agent generates a ui it is JUST to make decisions on the data is has access too. E.g. new email received asking for a file and a small change, agent finds the file and makes the change, then a UI is generated confirming the correct file and changes. this is what generative ui looks like to me, far off, but definitely in the future.

by dpflan 2y ago

yawnxyz 2y ago

Yes! The simplest and most direct and useful implementation Generative UI is to have a settings / form react to the context — e.g. an email form, or a bunch of sliders. I have a zod-based form schema, and set of forms and schemas. If there's a new schema (e.g. if I want to add name and comments) I can just have the AI generate and save a new schema, and the UI will know how to handle the changes. This makes updating interfaces really easy. (this is personalized to the dev) For UIs generated per user, ideally you'd have a lot of guardrails around what it's able to generate and what the underlying data and use case is. I haven't built any of this in production yet, but I think accessibility may get a boost. Some video games already have a "verbose mode" for new players, and a "bare bones" mode for players who already get the mechanisms. One might consider building an "explanation" layer where some of the concepts can be explained to the user dynamically, and some more complex options can be either revealed under an "advanced mode" or when the UI determines the user "understands" the underlying concepts, as not to overwhelm them. I'm currently experimenting and designing/thinking through some bioinformatics (gene annotation) tools with this approach, but it's early days.

gcr 2y ago
This sounds exceedingly unintuitive. Users hate having settings change / appear and disappear. It sounds like it would make interfaces broadly unteachable and difficult to document.
epiccoleman 2y ago
> "bare bones" mode for players who already get the mechanisms. I've wanted this in monster hunter for years. Spare me the cutscenes and dialog and just gimme a menu full of quests so I can decide which monster I want to fight without having to listen to a damn audiobook.
apsurd 2y ago
sounds like a bike shedder's dream. While i think it's possible that contextualized UX has value, it's seem way too easy for builders to go ham doing what they love: building more things. i'm a cursor LLM editor convert. Pretty amazing. Thing is, being capable of building N versions of a thing doesn't mean it's a good idea. Technical debt has gone up dramatically on a team of 2. And its not realistic that higher iteration velocity will yield the greatest version. easy to say but you need data and users to test through all of them. that's not happening in real life.
geogod42 2y ago
you are not taking the concept far enough gen UI could look like a completely custom interface integrating hundreds of apps to one. that is if an Agentic system is completely multi-modal it can collect all digital information the user owns (in a safe way ofc) but that means when an agent generates a ui it is JUST to make decisions on the data is has access too. E.g. new email received asking for a file and a small change, agent finds the file and makes the change, then a UI is generated confirming the correct file and changes. this is what generative ui looks like to me, far off, but definitely in the future.