I'm experimenting with this balance now -- I built and launched a small analytics service (basic web tracking) that uses the web UI for sign-up through Cloudflare Access and provides minimal instructions on connecting your agent to MCP.
There's minimal reporting post-login about the sites you're tracking, but site setup, configuration, and reporting is all done through MCP with your agent. It's working for my minimal needs right now (traffic over time, plotting visits on a map) and is a good way to figure out how I want to do reporting rather than building a more general purpose reporting interface.
First of all, it comes down to product positioning. Most of the apps I build are for my own work or collaborative reasoning tasks. Sometimes I build not just apps, but also web services and assorted small tools. My philosophy is to minimize UI as much as possible and keep interfaces lean. Anything that can run in the background stays out of the user’s view — that’s the product perspective. But when I build an app to accelerate my own research work, I tend to go for more complex UI layouts, laying out the full research workflow visibly on the interface.
Developers should provide a documented CLI for all their programs. Anything that is clickable should be MCP-able.
I do not think applications will be only headless. MCP will be an alternative user(agent) interface not a full replacement.
Do you really think that we have to get a LLM subscription just to use a program, that probably has a subscription.
More over, 5 years ago , software developer needed : wikipedia, stackoverflow an and IDE to develope software, now suddenly they cannot live without at $200 subscription to develop a variation of ( video games, custom harness, custom RAG, custom CRUD).
Someone said in 2 years, most developers skill will shrivel so much that the next computer will come with only (yes / no button)
I'm experimenting with this balance now -- I built and launched a small analytics service (basic web tracking) that uses the web UI for sign-up through Cloudflare Access and provides minimal instructions on connecting your agent to MCP.
There's minimal reporting post-login about the sites you're tracking, but site setup, configuration, and reporting is all done through MCP with your agent. It's working for my minimal needs right now (traffic over time, plotting visits on a map) and is a good way to figure out how I want to do reporting rather than building a more general purpose reporting interface.
First of all, it comes down to product positioning. Most of the apps I build are for my own work or collaborative reasoning tasks. Sometimes I build not just apps, but also web services and assorted small tools. My philosophy is to minimize UI as much as possible and keep interfaces lean. Anything that can run in the background stays out of the user’s view — that’s the product perspective. But when I build an app to accelerate my own research work, I tend to go for more complex UI layouts, laying out the full research workflow visibly on the interface.
MCP - power users
UI - initial interactions with the product
Developers should provide a documented CLI for all their programs. Anything that is clickable should be MCP-able.
I do not think applications will be only headless. MCP will be an alternative user(agent) interface not a full replacement.
Do you really think that we have to get a LLM subscription just to use a program, that probably has a subscription.
More over, 5 years ago , software developer needed : wikipedia, stackoverflow an and IDE to develope software, now suddenly they cannot live without at $200 subscription to develop a variation of ( video games, custom harness, custom RAG, custom CRUD).
Someone said in 2 years, most developers skill will shrivel so much that the next computer will come with only (yes / no button)
UI when there’s paying customers.