3 ms·

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 comp

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, 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.

Boxxed 26d ago
> 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. IFs! Oh no! Throwing all of this into a non-deterministic and expensive black box is making it less complex, you say?
zahlekhan 25d ago
this exactly the future we are working towards as well. You should checkout AppLess http://github.com/thesysdev/appless http://github.com/thesysdev/appless
- PhunkyPhil 25d ago
  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. To take this a step further: https://chatjimmy.ai/ 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)...
  - zahlekhan 25d ago
    Exciting times indeed
amazing_stories 25d ago
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.
c-hendricks 25d ago
How do you reconcile ... > 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.

Boxxed 26d ago

> 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. IFs! Oh no! Throwing all of this into a non-deterministic and expensive black box is making it less complex, you say?

zahlekhan 25d ago

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

PhunkyPhil 25d ago
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. To take this a step further: https://chatjimmy.ai/ 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)...
- zahlekhan 25d ago
  Exciting times indeed

amazing_stories 25d ago

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.

c-hendricks 25d ago

How do you reconcile ... > 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.