> [Given] a method for chat applications to understand components exposed from the website in question [...] AI chat applications win, and so does the brand that gets to keep ownership of how it tells the story of its product to its users.

Never happening. The brand may "keep ownership of how it tells its story," but it loses its users. You have turned your tool into a series of widget in someone else's application, with no control whatsoever over how users interact with you. Want to show your user a notification? (Sure you do—I can't get away from the things.) Too bad. ChatGPT owns your users, and they only see what OpenAI wants them to see, which likely will not include ads for your premium features.

Don't mistake this for user freedom, either. Users still won't own their own tools. We're just moving from a model where each vendor separately leases you their tool to a model where every tool is leased via OpenAI, which curates them based on its own monopolistic whims.

Tech companies will not surrender control of their users so easily. They may integrate chatbot components into their apps, but they will not permit an inversion of control where their product becomes a component in a chatbot.

> You likely won’t expect users 5 years from today to navigate 5 pages deep

Of course I do. There's this fallacy that, because chatbots are useful for some things, chatbot interfaces must be the best at everything, and that's just not true. I don't go to ChatGPT to ask it for relevant tech news. I go here and browse the HN frontpage. Chatbots offer zero discoverability; search bars didn't replace page navigation, and chat bots won't either.

I think that the inverse thesis is true, you make websites more accessible (a11y, wgac, aria labels etc) for humans, then the interaction heuristics are clearer for agents functioning off browser-use or similar. If a screen reader can understand your site, then an agent can. Reinventing the wheel to facilitate the current state of agents makes the web worse for everyone, it's not a preemptive move, it's actually a decline in almost objective and measurable quality, and potentially one which removes access to the internet by people who just want to.. use the internet.

AI component libraries in your site make your web app even more easily consumed and subsumed by AI chat clients.

This not only kills pages, but it kills the concept of a browser where the user agent is a human, rather than making your pages be designed where the user agent is an AI agent.

That doesn't make me happy to experience because I'm guessing that after a generation or so, web designers will not only do mobile first designs with stupid amounts of white space and not taking advantage of the desktops greater screen real estate and precise mouse movements, but AI first websites will get so popular that browsing sites manually will look like trying to use a text only browser in the JavaScript world.

Easy for me to do a depressing take, but hopefully the bitter lesson of AI will help this particular projected future not come to pass because the AI will get smart enough that it will embed a browser right there in line and just render the window for the user, or it will otherwise gets good enough at screen scraping and UI automation that it can just use an existing browser, just like a human, the sites won't be dumbed down even further for AI consumption.

> In a world where we can type anything into a text box and get the information back instantly we are circumventing the need to visit websites altogether.

This is purely anecdotal, but the only people in my extended circle making this transition (to any extent) are the technically savvy; everyone else is slowly realizing how awful AI tools and "AI-first experiences" can be and are actively trying to avoid them.

I've noticed a change in technical blog articles in the past 2 years. Why do most contain phrases like "everything changes", "not behind (yet)" etc.?

If you have a valid point to make, you don't need to force FOMO on the reader.

- My gripe with posts like this is when you write stuff like this, you sound like a person who has never seen the outside of a tech circle

- My neighbor is a non tech guy. I want you to create this magic chat interface and make him use it

- He has to sit and think what to type first and he always has this fear what if I dont get an answer back

- Vast majority of the people in the world fall in this category

- Your AI replaces UI stuff aint happening for 20 yrs at the minimum. You ll need 2 to 3 full generations of people to adapt before making statements like these

I think the more realistic direction is exposing API / MCP-style interfaces for agents to interact with a product’s functionality, rather than shipping UI components that an AI client would render.

The "AI renders your components inside chat" idea feels very similar to Facebook’s old canvas apps. That model disappeared for good reasons: abuse, security, and loss of platform control.

It seems far more likely that AI platforms will provide their own interaction primitives (forms, pickers, confirmations, etc.) and simply call third-party tools behind the scenes. That lets the platform retain control over UX and safety, and avoids the risks of embedding arbitrary third-party UI.

I was a bit confused when I went to the json-render github repo, because there were no screenshots of what it looked like.

I found only two videos about it on YouTube. This is the better of the two, and illustrates the output: https://www.youtube.com/watch?v=vndn2vmSIbw

I don't know whether that video uses Kumo (UI library also from Vercel).

I like the direction this is taking, and I think the more radical and more coherent endgame is data ownership returning to us and AI's replacing website brands all together as the AI generates any UI we could ever want.

Today most websites offer interfaces for accessing the data that they hold hostage. However they are holding our data. We would prefer to have it back if we could, and AI will enable that. Our paradigm will shift this way eventually I hope.

Though it's true companies dont have an incentive to hand over data custody anytime soon, AI companies have already found a way around this in little ways and its a matter of time until it goes to where all the data we could ever want is within the AI cloud and our next task is simply taking back ownership of that (where local inference takes us).

Theres probably a middle ground where we allow an app to augment / enhance itself using deterministic behaviour but a user based soft request. If I as a user can ask for a feature, and have it work just for me, thats pretty cool.

Instead of progressive enhancement it can be progressive evolution.

> In a world where we can type anything into a text box and get the information back instantly we are circumventing the need to visit websites altogether

But without visits many websites will disappear. So where will AI get its information from in the future?

I do like that idea of allowing flexible component rendering, especially if you're building a your own app with chat UI. The one problem would be like always standardisation, will chatUIs need to be like browser and follow standards? Or do they need to render JS, CSS, HTML as a component? What freedom do chatUIs allow the components?

Even so, ask, what's the end goal of the user? Does it even make sense to worry about UI if we're think autonomous agents that sole goal is to accomplish something defined by the user?

> Imagine your own product. You likely won’t expect users 5 years from today to navigate 5 pages deep, apply filters and sort data just to try to derive the answer themselves… will you?

Yes, I do, because outside of tech circles, AI adoption is not as pervasive/ universal as the loudest voices keep suggesting. I’m not dismissing its value, but gentle reminder to spend more time around nontechnical people, listen to how they feel about the tech, and pay attention to how they engage with it when offered.

How is this different than MCP Apps that you pre-build for your org using something like https://creature.run

I like that MCP Apps just offer tools, and AI doesn't have to deal with JSON and generative UI. Basically, you can cache UI as an MCP App by generating it up-front, to constantly save on tokens and time, and let AI use tool calls which it is getting constantly better at.

When I use ChatGPT to do research, I expect it to justify itself by quoting from web pages and linking to those web pages. (I gave it explicit instructions to quote things, but unfortunately it will only do short quotes.)

This might be an extended web search, but it's still a web search. The documents need to exist. Maybe a lot of the surrounding boilerplate disappears, though?

> If AI wants to own the internet

As if. It's corporations that want to own _your eyeballs_.

It also kills any incentive to publish anything.

It completely removes the user from having any agency over the sources of information they are presented with.

> My hope is that you will embrace the change

Some people get so caught up with the technology they seem to forget they're charging straight into the most boring dystopia imaginable.

We’re going the other way where we are removing IP from public view.

Don’t count out on device, that’s where most of our focus is. If we can convert the voice / text to programatic commands on device, then we control the experience and don’t let the wolves through the gate.

I'm kind of hoping this kills traditional marketplaces since they're filled to the brim with ads and purposefully knee-cap search and filtering so you can't properly find anything.

Conversational commerce will let you shop on any website, with any UI you like, and without paying marketplaces a cut of every sale.

Outside of discovery and trust, what are they really bringing to the table anymore? Most sellers have their own websites with cart, product catalog, and payments already so AI that can tap into that API directly will render these marketplaces and middle-men obsolete given enough time.

Would you rather visit a website full of ads that doesn't answer your question and is written for SEO or get the answer instantly without any ads?

Eventually, after killing several websites by depriving them of revenue, ChatGPT will enshittify like everything else and starting adding ads.

There isn't even a question about that. Just think of Google for example.

Why Google's SERP has ads but Gemini does not? There isn't even a "they are making money with the data" argument here, because Google already has all the query data it could ever want. They just haven't added ads yet.

Eventually, Gemini will look like a SERP with 5 ad results, if it doesn't go to the Google graveyard like everything else.

So can I use this to make my pages completely unusable by AI agents, then?

> You’re not behind (yet) but in today’s world

Yes, yes. We will all be left behind unless we [PLACEHOLDER]. Sounds very convincing.

I’m interested in this space my thoughts so far;

The idea of representing UI as state goes back forever, I’m not that old but at least in the advent of the web, plenty of JSON -> UI specs or libraries have came into existence. If the specification is solid and a large portion of people agree upon it, I don’t doubt it will take over what we think of UI. (current contenders are json_render, a2ui etc)

The first benefit being that if I can describe my entire UI and the actions each component wants as json, theoretically, I can pass that file to any client to render be it mobile, react, a java swing app etc The responsibility of rendering becomes of anyone who wants to do it.

UI JSON -> UI Framework <- Design Tokens

Above is a simple way of describing how it would generally work. Where the UI framework can be whatever it wants to be as long as it knows how to connect up the UI JSON in a meaningful way.

Now for existing apps and their respective UI’s it’s never made all that much sense to describe how your components behavior in state, useful for some, and many have done it, but a hard pitch for others.

In the agentic era, the pitch is a lot more appealing.

- LLM’s are great-enough at writing JSON

- A lot of people are sharing the sentiment that they can just vibe code small apps for themselves. Hinting at they love the actual ability for full personalization.

Though having the user generate HTML and the rest all the time by LLM’s is more error prone, slow and costly.

The user can just ask an LLM to compose a composition of components in JSON laid out how they want and connected to the API’s they care about. (that can be rendered anywhere)

Personally, if I had a catalogue of 100 distinct services/API's, and I could ask an LLM to generate a UI in JSON that I can copy and paste anywhere to render it, I would be in heaven.

If I had subscriptions to services that; (fake services)

- EMAILR: Sent Emails

- BOOKLAND: Explore books

- DEEP_RESEARCHER: Researches Topic

I could ask an LLM to "With my services, EMAILR, BOOKLAND and DEEP_RESEARCHER and their attached tools.

Can you generate me a dashboard that lists out the top 20 BOOKLAND books, below each one added a button that posts the book title to DEEP_RESEARCHER when I click it. Also add a button below each book that uses EMAILR to email me them"

It would then return something like;

  {
  "view": "dashboard",
  "title": "Book Research Hub",
  "children": [
    {
      "type": "grid",
      "columns": 4,
      "source": { "service": "BOOKLAND", "action": "list", "params": { "limit": 20, "sort": "top" } },
      "each": {
        "type": "card",
        "children": [
          { "type": "text", "bind": "$.title", "variant": "heading" },
          { "type": "text", "bind": "$.author", "variant": "muted" },
          { "type": "image", "bind": "$.cover_url" },
          {
            "type": "button",
            "label": "Deep Research",
            "variant": "primary",
            "action": { "service": "DEEP_RESEARCHER", "method": "research", "params": { "topic": "$.title" } }
          },
          {
            "type": "button",
            "label": "Email me this",
            "variant": "secondary",
            "action": { "service": "EMAILR", "method": "send", "params": { "to": "$user.email", "subject": "Book: $.title", "body": "Check out $.title by $.author" } }
          }
        ]
      }
    }
  ]

}

Users could share their layouts and what they like and you could end up with a market place or sane defaults for those who don't want to bother with describing what they want. No longer do you have to rely on the UX team of the service for it to be laid out how you want.

There is a metric tonne of work that has to be done to make a specification that can handle more complex things. But I'd bet a lot of users will learn to love and appreciate that the 5% of features they care about they can finally just actually place how they want it to across all their disparate apps.