The Last APK: Retiring Android SDK Development for Institutional Software Using Python-Django, HTMX, and a WebView Bridge

TL;DR

This paper demonstrates that a campus management system built with Python-Django and HTMX can replace native Android SDK development, reducing costs, payload, and development time while maintaining user satisfaction.

Contribution

It introduces a web-based approach for institutional mobile applications that eliminates the need for native Android SDK development, using a Django-HTMX stack.

Findings

Development time reduced by approximately 54%.

HTTP payload decreased by 91% compared to full-page reload.

User satisfaction scored 4.2 out of 5.

Abstract

The assumption that mobile enterprise software requires native Android SDK development has persisted for over a decade, but for institutional deployments, this assumption is not merely outdated: it is economically wasteful and technically unnecessary. This paper presents a campus management system built during an internship at the Indian Institute of Technology Gandhinagar (IIT Gandhinagar), covering housekeeping task scheduling, inventory management, horticulture tracking, worker attendance, multi-stage leave workflows, and client-side photo capture with automatic compression. The core stack uses Python-Django as the backend framework and HTMX for hypermedia-driven, mobile-responsive partial DOM updates, containing zero lines of Android SDK application logic. The entire system runs as a self-hosted Docker Compose deployment with no dependency on any external cloud service. Through architectural analysis, HTTP payload measurement, and user experience evaluation with 42 campus staff, we demonstrate that the HTMX-Django approach reduces development time by approximately 54%, reduces average HTTP payload by 91% versus full-page reload, and achieves user satisfaction scores of 4.2/5.0.