Logo
ScienceStack
Table of Contents
Fetching ...
Sign In

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

Rahul Patel

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.

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

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.

Paper Structure

This paper contains 38 sections, 7 figures, 3 tables.

Table of Contents

  1. Introduction
  2. Background and Related Work
  3. The Android Dominance Narrative and Its Costs
  4. Hypermedia-Driven Development and HTMX
  5. Progressive Web Applications and the WebView Pattern
  6. Self-Hosted Intranet Deployment
  7. Django for Institutional Systems
  8. System Architecture
  9. Overview
  10. Module Decomposition
  11. Role-Based Access Control
  12. HTMX Integration Patterns
  13. The WebView APK: Android Studio as a Packaging Tool
  14. Motivation
  15. Implementation
  16. ...and 23 more sections

Figures (7)

  • Figure 1: Three-tier hypermedia architecture of the IIT Gandhinagar campus management system. All components run on the campus intranet via Docker Compose. The optional WebView APK layer provides Android home-screen installation without any native application logic.
  • Figure 2: Six-step HTMX hypermedia request--response cycle. The server returns rendered HTML fragments directly to the browser's DOM, eliminating the JSON serialisation, client-side template rendering, and RecyclerView adapter binding layers required by native Android SDK development.
  • Figure 3: Module-wise source code volume measured from the deployed IIT Gandhinagar repository. Python accounts for 64.5% of the codebase; no Kotlin or Java is present.
  • Figure 4: Round-trip latency: Native Android SDK (estimated) vs. HTMX web app (measured on campus 100 Mbps LAN). WebView APK performance was statistically indistinguishable from direct browser access ($p > 0.05$, $n = 50$).
  • Figure 5: HTTP payload: full page reload versus HTMX partial fragment ( hx-swap). Labels show percentage reduction achieved.
  • ...and 2 more figures