# Diverse, Inclusive Innovation ## Overview *(What to aim for)* DPI should not just be innovative in itself, but also enable diverse innovation by public and or private ecosystem of users. A DPI’s technical architecture should allow others (public and private innovators) to build solutions and services using the DPI at scale (akin to highways or the Internet) via tools such as open APIs (instead of DPI providers building the entire solution in a monolithic fashion). Enable innovation both by ‘**challenger**’ market players in the ecosystem and by **incumbents**. **A digital back-end shouldn't presuppose a single digital front-end.** Enable both the core DPI architecture and a diversity of innovative ecosystem-created solutions to power **multi-modal** access: across online, semi-online (low bandwidth connectivity), and offline modes; self-service and assisted modes; and in smartphone, feature phone, and no-phone modes. * For instance, payment systems or identity systems shouldn't presuppose just one mode of authentication (e.g., online API based) and allow for offline or semi-online modes (QR codes, local SDKs that can perform face authentication, etc.). his is essential to catalyse private innovation that doesn't merely target an elite connected population in a country, but also innovates to solve the challenges of diverse populations who speak multiple languages and have varying levels of digital literacy, thus reducing the impact of a digital divide. The principle also addresses both scale, adaptability and sustainability over time. Private innovation can be leveraged both in building the DPI (for instance, in driving private partners to enroll individuals into an identity system) and in usage of the DPI in a wider digital economy to offer solutions (for instance, banks or private players using an identity e-KYC to offer a service like opening a bank account). Public- and private-sector adoption and innovation should be **voluntary** and **demand-based** rather than mandated by authorities. This tends to create sustained usage over time. ## **Technical Tools *****(How to achieve it)*** * [ ] Open Application Programming Interfaces (APIs) * [ ] Digital signatures (Public Key Infrastructure) * [ ] Digitally signed QR codes (available offline) * [ ] Machine readability of documents * [ ] Reusable Software Development Kits (SDKs) * [ ] Data and other Standards * [ ] Multi-modal access ## **Societal Outcomes *****(Why it matters)*** * [ ] Inclusion * [ ] Scale * [ ] User Choice * [ ] Resilience * [ ] User-centric solutions --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.cdpi.dev/the-dpi-wiki/dpi-tech-architecture-principles/diverse-inclusive-innovation.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.