> ## Knowledge Base Index
> Fetch the complete knowledge base index at: https://staging.chrisp.chat/sitemap.xml
> Use this file to discover available pages before exploring further.
> Pure-Markdown content can be obtained by appending a '.md' suffix to the content URLs listed in the sitemap (without the trailing slash).

# Why is the mobile experience set up as a progressive web application?

The mobile platform is built as a ****Progressive Web Application (PWA)**** to ensure it remains accessible, sustainable, and cost-effective—especially in low-resource or government-owned environments.

Key benefits of using a PWA:

* ****Lower development and maintenance costs****: One responsive codebase works across mobile and web, avoiding the need for separate Android/iOS apps.
* ****Instant updates****: Changes are pushed to all users without requiring downloads or app store approvals, reducing delays and version mismatches.
* ****Accessible on low-end or shared devices****: PWAs require minimal storage, no installation, and run in the browser—ideal for low-cost devices.
* ****Cross-platform compatibility****: PWAs function across all major browsers and operating systems, reducing testing and support effort.
* ****No app store overhead****: Governments and implementers avoid the complexity of managing developer accounts or paying licensing fees.
* ****Easier for governments to maintain****: Built with standard web technologies, PWAs are more manageable for local IT teams without specialized mobile development skills.
* ****Offline support is still possible****: PWAs can cache dashboards and data for use in low- or no-connectivity environments.

This approach aligns with the platform’s long-term goal of sustainable, scalable access to critical data—anytime, anywhere.