Show HN: Post-Interface Design – A manifesto on the abolition of UI

Re:Show HN: Post-Interface Design – A manifesto on the aboli... by andreabergonzi on Monday February 16, 2026 @11:54AM (#47037302)

Glad it resonated. You hit the nail on the head regarding agents being a 'workaround', that's exactly why I categorize them as the 'Transitional phase' rather than the destination. They are essentially bots trying to navigate a web that wasn't built for them.

Your point about the visual appearance changing dynamically is the 'Holy Grail' I touch on in the 'Generative UI' section. We are currently stuck designing static screens for dynamic problems.

I agree we haven't seen a true demonstration yet. Do you think that shift happens at the App level first (e.g., a dynamic Spotify), or does it require a whole new OS paradigm (a 'Generative OS') to work?

[ Parent | on HN ]

Re:Show HN: Post-Interface Design – A manifesto on the aboli... by dtagames on Monday February 16, 2026 @11:59AM (#47037373)

Good question! I'd say it happens at the app level first because the context of the OS is too big a surface to start with. But a RAG app for a specific vertical could have enough context to dynamically draw a custom UI for every user, given the constraints on what the app is generally about.

[ Parent | on HN ]

Re:Show HN: Post-Interface Design – A manifesto on the aboli... by andreabergonzi on Monday February 16, 2026 @12:05PM (#47037461)

That makes a lot of sense, it is definitely the safer place to start.

It implies that design systems are about to change fundamentally. Instead of shipping a library of static components, we'll need to ship a set of constraints and rules that tell the RAG model how it's allowed to construct the UI on the fly.

[ Parent | on HN ]