Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

> Traditionally, end-users were non-technical and would be stuck with whatever the application developer gave them. But now every user has an LLM too.

Interesting point.

I keep coming back to the idea that users could request changes, and they could be experimentally deployed immediately.



Thank you. There was a lot to extensions that was bit of scope for the essay, which I would love to go deeper on in later writing.

Some open questions I had as I thought through extensions:

We talked about the data abstraction side: when you expose data, it's easier for end-users to build extensions. But there are questions on UIs and data modeling.

UIs: How cool would it be agents could "enter" into applications and change the UI? In one sense this hard, but at least a demo feels in reach. What if an app exposed the UI components that it was built out of? This would let the agent remix them.

Data modeling: Exposing data works, but what if users want to store extra information? Maybe each user could spin up their own separate "extra" database.




Consider applying for YC's Fall 2026 batch! Applications are open till July 27.

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: