serverdriven

Server-driven is an architectural pattern in which the server plays a central role in determining the user interface, user flows, and business logic that govern an application. In a server-driven approach, the client is typically a thin rendering layer or a small runtime that fetches instructions, rather than a full client-side application that contains the UI logic. This contrasts with client-driven architectures where the UI is defined primarily on the client.

Implementation patterns include the server returning structured UI definitions (for example, JSON or XML) that describe screens, components, actions, and data requirements, which the client renders. Another variant involves the server returning markup (HTML) or templated instructions that are filled by the client. Some systems also use remote procedure calls or event streams to guide navigation and behavior. The common thread is that the server maintains the authority over the UI and flow.

Benefits include centralized control and consistency across platforms, simpler updates to UI and business logic, easier experimentation and A/B testing, and improved security by keeping sensitive logic on the server. It can also reduce the complexity and capability requirements of clients, making it attractive for limited devices or cross-platform apps.

Challenges involve increased latency due to round trips, reliance on network connectivity, and potential performance and scaling concerns on the server. Developer tooling, debugging, and testing can be more complex. Versioning of UI definitions and handling offline scenarios require careful design.

The term overlaps with server-side rendering, remote UI, and declarative UI patterns, but is distinct in that it emphasizes the server as the primary source of UI decisions rather than just pre-rendered pages. It is used in various contexts such as mobile apps, web portals, and enterprise dashboards.