Platform-agnostic (API first)

Decouple service logic from user interfaces to enable delivery across any channel.

Definition

Platform-agnostic design means building services where the core functionality, data, and business logic are separated from the front-end presentation layer. Instead of building a "website" or an "app," teams build a set of robust, standardized APIs that can power any interface—whether it’s a web portal, a mobile app, a kiosk, or a third-party integration. This principle ensures that government services are not locked into specific technologies or channels. By treating the API as the primary product, entities ensure that their services can be easily consumed by other government departments, private sector partners, and future emerging platforms without rebuilding the core system.

Impact

Adopting a platform-agnostic approach future-proofs government services, allowing them to scale and adapt to new technologies without costly redevelopment. It creates a flexible ecosystem where data and services flow freely between entities, enabling true interconnectivity and fostering innovation by allowing external partners to build new experiences on top of government foundations.

Good Design

Decouples user interfaces

Separates the front-end user interface from the underlying business logic, ensuring that updates or changes to one layer do not break the other.

Exposes core functionality

Makes all core service capabilities available through documented, standardized APIs before building any specific front-end screens or apps.

Ensures channel consistency

Maintains consistent data and business rules across all channels (web, mobile, service counter) by relying on a single, shared source of truth.

Enables seamless integration

Allows other government entities and private sector partners to easily consume service capabilities, fostering a connected ecosystem.

Standardizes data exchange

Uses consistent data exchange formats to ensure full compatibility and interoperability across the entire government network.

Prioritizes developer experience

Treats APIs as products that require clear documentation, versioning, and active support to ensure they are easy for other teams to use.

Related resources

Further resources relating to how we aim to be platform agnostic when we work.

Related service principles

Our service principles that relate to platform-agnosticism.