Blog

The Clientless Thesis

thesisarchitecturemcp

The last generation of software treated the app as a destination.

Install it. Open it. Navigate it. Learn the workflow. Adapt your work to the interface the developer decided to ship.

That model made sense when the browser and mobile app store were the main universal software surfaces.

It makes less sense in a world where people already work inside chats, IDEs, widgets, dashboards, documents, and AI workflows.

Clientless is the name for the reversal: the client disappears as the center of the app, and the useful pieces of software become capabilities that hosts can assemble into personal interfaces.

The app decomposes

The important change is not that UI is represented as JSON. Developers have done that for a long time.

The important change is that the app stops being the primary package. A product can expose search, approval, configuration, forecasting, preview, comparison, and monitoring as capabilities. A host can combine those capabilities into the interface the user needs now.

That interface might live inside ChatGPT for one decision. It might be saved as a recurring team workflow. It might appear later as a widget. It does not have to become a traditional app.

Hosts become composition surfaces

The ideal host is not a second product implementation.

It should understand capabilities, render interface streams, forward actions, enforce security boundaries, and let users save what is worth keeping. It should not quietly recreate every fixed app inside a new shell.

This is why Clientless feels like the next step after Electron, Tauri, and app stores. Those systems moved completed apps across platforms. Clientless moves capabilities across hosts.

Why developers should care

Developers will still build hard things: permissions, action contracts, schemas, validation, visual components, domain rules, data access, and integrations.

The change is the deliverable.

Instead of shipping one completed destination, developers publish the capabilities users can call, combine, and turn into personal interfaces.

That is the platform shift.