The Age of Install-less Apps
The build-review-install-update chain disappears. The server becomes the app.
Vol. 1
build
- Let's Handle State — Touch the Value, Not the ScreenTwo weeks ago the number board got buttons. Press one and the number moves. But who holds that number is the question. If the screen holds it, a second panel shows a different number. If the counter holds it, you can unplug the panel and plug it back in and the number is the same.DEV
- An LCD Maker Builds an HMI in 30 Minutes — The Panel Speaks Tools, the Screen Becomes a DefinitionThe panel's capabilities as tools, the screen as a definition, the runtime as the renderer. We lay out a sample where that whole chain actually runs, from beginning to end, and show how the packages mesh. The screens were not drawn — they were really rendered and captured.DEV
- Putting Up Your First Screen in Ten LinesBuilding a waiting-room number board. The screen definition is nine lines, and those nine lines are not inside the client. The server holds them as a file and hands them over on connect. That is what "no build, no install" means.DEV
- Start the Server — and Write Nothing to stdoutFirst in the mcp_server course. No tools, no resources — just a server standing up. There is one thing to confirm here: does a client connect and get an answer to initialize. And one rule that has to be set now or it breaks later.DEV