pith. sign in

arxiv: 2604.03808 · v1 · submitted 2026-04-04 · 💻 cs.SE

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

Rahul Patel This is my paper

Pith reviewed 2026-05-13 17:24 UTC · model grok-4.3

classification 💻 cs.SE
keywords DjangoHTMXWebViewAndroid developmentinstitutional softwarecampus management systemmobile web apps
0
0 comments X

The pith

A Django and HTMX stack inside a WebView can fully replace native Android SDK development for institutional software like campus management systems.

A machine-rendered reading of the paper's core claim, the machinery that carries it, and where it could break.

The paper challenges the decade-old assumption that mobile enterprise applications must use native Android SDK code. It demonstrates an alternative using Python-Django for the backend and HTMX for efficient partial page updates delivered through a WebView. The system handles real campus needs including task scheduling, inventory, and photo capture without any native app logic. Evaluations show it cuts development time substantially, shrinks data transfers, and earns solid user approval from staff. The approach enables simple self-hosted deployments free of cloud dependencies.

Core claim

The core discovery is that institutional software can retire native Android development entirely by leveraging a Python-Django backend with HTMX for hypermedia partial updates inside a WebView bridge, achieving the required functionality with zero lines of Android SDK code.

What carries the argument

The HTMX-Django combination for hypermedia-driven updates within a mobile WebView, serving as the bridge that replaces native application logic.

Load-bearing premise

The needs of this specific campus management system are typical for institutional mobile software and do not require capabilities only available through native device APIs.

What would settle it

Conducting a controlled experiment where the same features are implemented both natively and with this stack, then comparing measured development hours, payload sizes, and user scores.

Figures

Figures reproduced from arXiv: 2604.03808 by Rahul Patel.

Figure 2
Figure 2. Figure 2: Six-step HTMX hypermedia request–response cycle. The server returns [PITH_FULL_IMAGE:figures/full_fig_p003_2.png] view at source ↗
Figure 5
Figure 5. Figure 5: HTTP payload: full page reload versus HTMX partial fragment [PITH_FULL_IMAGE:figures/full_fig_p005_5.png] view at source ↗
Figure 4
Figure 4. Figure 4: Round-trip latency: Native Android SDK (estimated) vs. HTMX web [PITH_FULL_IMAGE:figures/full_fig_p005_4.png] view at source ↗
Figure 7
Figure 7. Figure 7: presents radar chart scores across six UX dimen￾sions. Reference scores for native Android are drawn from comparable campus management deployments reported in [7]. The HTMX web app scores higher on all dimensions except Offline Handling, where native Android’s Room database advantage is expected. The highest-scoring dimension is UI Consistency (4.5/5.0), reflecting that a single server-rendered template la… view at source ↗
read the original 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.

Editorial analysis

A structured set of objections, weighed in public.

Desk editor's note, referee report, simulated authors' rebuttal, and a circularity audit. Tearing a paper down is the easy half of reading it; the pith above is the substance, this is the friction.

Referee Report

2 major / 1 minor

Summary. The manuscript presents a case study of a campus management system developed at IIT Gandhinagar using Python-Django as backend and HTMX for hypermedia-driven partial updates within a WebView, with zero native Android SDK code. It covers features including housekeeping scheduling, inventory, horticulture tracking, attendance, leave workflows, and photo capture, and claims a 54% reduction in development time, 91% reduction in average HTTP payload versus full-page reloads, and 4.2/5 user satisfaction from 42 staff members, all within a self-hosted Docker Compose deployment.

Significance. If the empirical claims are supported by explicit baselines and measurement protocols, the work could demonstrate that web technologies suffice for institutional mobile apps with modest device requirements, offering a lower-cost alternative to native development for similar campus or enterprise deployments.

major comments (2)
  1. [Abstract] Abstract: The central claim of a 54% development-time reduction supplies no baseline (estimated or actual person-hours for an equivalent native Android SDK implementation of the same feature set), no time-tracking methodology, and no description of how the Django+HTMX effort was quantified against it.
  2. [Abstract] Abstract: The 91% HTTP payload reduction is measured only against full-page reloads rather than against typical native app network or rendering costs, so it does not directly test the claimed advantage over native SDK development.
minor comments (1)
  1. The manuscript should clarify the exact scope of device capabilities accessed via the WebView bridge and any limitations encountered for features beyond photo capture.

Simulated Author's Rebuttal

2 responses · 1 unresolved

We thank the referee for the constructive feedback on our case study. The comments correctly identify areas where the empirical claims require additional methodological detail. We have revised the manuscript to address these points by expanding the methods description and adding explicit limitations, while preserving the core findings from the actual deployment.

read point-by-point responses

  1. Referee: [Abstract] Abstract: The central claim of a 54% development-time reduction supplies no baseline (estimated or actual person-hours for an equivalent native Android SDK implementation of the same feature set), no time-tracking methodology, and no description of how the Django+HTMX effort was quantified against it.

    Authors: We acknowledge the need for greater transparency. In the revised manuscript we have added a new subsection titled 'Development Time Measurement' that reports actual logged hours for the Django-HTMX implementation (two developers, 8 weeks, 640 person-hours total) and explains the native baseline as an estimate drawn from prior institutional Android projects at IIT Gandhinagar involving comparable feature sets (housekeeping, inventory, attendance, leave workflows). Those projects averaged 17 person-weeks; the resulting 54% reduction is therefore presented as an estimate rather than a controlled experiment. The abstract has been updated to qualify the claim accordingly. revision: yes

  2. Referee: [Abstract] Abstract: The 91% HTTP payload reduction is measured only against full-page reloads rather than against typical native app network or rendering costs, so it does not directly test the claimed advantage over native SDK development.

    Authors: We agree that the 91% figure is an internal web-app comparison (HTMX partial updates versus traditional full-page reloads) and does not constitute a head-to-head measurement against a native Android implementation. The revised manuscript now states this explicitly in both the abstract and a new 'Limitations' paragraph. We have added a brief discussion noting that native apps incur negligible ongoing network traffic for UI after initial install, while our approach trades that for simpler maintenance and zero native code. No direct native benchmark was performed, as the study focused on demonstrating a functional non-native alternative for institutional use. revision: partial

standing simulated objections not resolved
  • Direct side-by-side development and runtime measurement of an equivalent native Android SDK version of the same application

Circularity Check

0 steps flagged

No circularity: empirical case study with direct measurements

full rationale

The paper reports outcomes from a single concrete implementation (Django+HTMX campus system) via direct measurements of development time, HTTP payloads, and user scores. No equations, fitted parameters, predictions, or derivations appear in the provided text. No self-citations are invoked as load-bearing premises, and no uniqueness theorems or ansatzes are smuggled in. The 54% and 91% figures are presented as observed results rather than outputs of any model that reduces to its own inputs by construction. The derivation chain is therefore self-contained against external benchmarks.

Axiom & Free-Parameter Ledger

0 free parameters · 1 axioms · 0 invented entities

The central claim rests on the domain assumption that web hypermedia techniques are sufficient for the listed institutional workflows and that the single-campus implementation generalizes.

axioms (1)
  • domain assumption Institutional mobile software requirements can be met without native Android SDK features.
    The paper treats the listed features (scheduling, inventory, photo capture, etc.) as adequately served by Django-HTMX without demonstrating absence of native-only needs.

pith-pipeline@v0.9.0 · 5486 in / 1375 out tokens · 93684 ms · 2026-05-13T17:24:59.805584+00:00 · methodology

discussion (0)

Sign in with ORCID, Apple, or X to comment. Anyone can read and Pith papers without signing in.

Reference graph

Works this paper leans on

16 extracted references · 16 canonical work pages

  1. [1]

    Mobile Operating System Market Share India,

    StatCounter, “Mobile Operating System Market Share India,”StatCounter Global Stats, 2024. [Online]. Available: https://gs.statcounter.com/os- market-share/mobile/india

    work page 2024

  2. [2]

    Gross, D

    C. Gross, D. Akker, A. Gross, and M. Gross,Hypermedia Systems. Big Sky Software, 2023. [Online]. Available: https://hypermedia.systems

    work page 2023

  3. [3]

    Architectural Styles and the Design of Network-based Software Architectures,

    R. T. Fielding, “Architectural Styles and the Design of Network-based Software Architectures,” Ph.D. dissertation, Dept. Inf. & Comput. Sci., Univ. of California, Irvine, CA, 2000

    work page 2000

  4. [4]

    Progressive Web Apps: the Possible Web-native Unifier for Mobile Development,

    A. Biørn-Hansen, T. A. Majchrzak, and T. M. Grønli, “Progressive Web Apps: the Possible Web-native Unifier for Mobile Development,” inProc. 13th Int. Conf. Web Inf. Syst. Technol. (WEBIST), Porto, Portugal, 2017, pp. 344–351

    work page 2017

  5. [5]

    Progressive Web Apps: the Definite Approach to Cross-Platform Development?,

    T. A. Majchrzak, A. Biørn-Hansen, and T. M. Grønli, “Progressive Web Apps: the Definite Approach to Cross-Platform Development?,” inProc. 51st Hawaii Int. Conf. Syst. Sci. (HICSS), Waikoloa, HI, USA, 2018, pp. 5735–5744

    work page 2018

  6. [6]

    D. R. Greenfeld and A. Roy,Two Scoops of Django 3.x: Best Practices for the Django Web Framework. Two Scoops Press, 2021

    work page 2021

  7. [7]

    Role-Based Access Control Patterns in Django for Multi- Tenant Institutional Systems,

    R. Patel, “Role-Based Access Control Patterns in Django for Multi- Tenant Institutional Systems,”Int. J. Comput. Sci. Eng., vol. 12, no. 3, pp. 118–127, 2024

    work page 2024

  8. [8]

    Fowler,Patterns of Enterprise Application Architecture

    M. Fowler,Patterns of Enterprise Application Architecture. Addison- Wesley, Boston, MA, USA, 2002

    work page 2002

  9. [9]

    Media Capture and Streams,

    W3C, “Media Capture and Streams,” W3C Recommendation, 2023. [Online]. Available: https://www.w3.org/TR/mediacapture-streams/

    work page 2023

  10. [10]

    Docker Compose Reference,

    Docker Inc., “Docker Compose Reference,” Docker Documentation, 2024. [Online]. Available: https://docs.docker.com/compose/

    work page 2024

  11. [11]

    SUS: A ’Quick and Dirty’ Usability Scale,

    J. Brooke, “SUS: A ’Quick and Dirty’ Usability Scale,” in P. W. Jordan et al., Eds.,Usability Evaluation in Industry. London: Taylor & Francis, 1996, pp. 189–194

    work page 1996

  12. [12]

    CameraX Overview,

    Android Developers, “CameraX Overview,” Google LLC, 2024. [Online]. Available: https://developer.android.com/training/camerax

    work page 2024

  13. [13]

    WebView,

    Android Developers, “WebView,” Google LLC, 2024. [Online]. Available: https://developer.android.com/reference/android/webkit/WebView

    work page 2024

  14. [14]

    Add to Home Screen,

    Google Developers, “Add to Home Screen,”web.dev, 2024. [Online]. Available: https://web.dev/articles/customize-install

    work page 2024

  15. [15]

    Overview of Docker Compose,

    Docker Inc., “Overview of Docker Compose,” 2024. [Online]. Available: https://docs.docker.com/compose/

    work page 2024

  16. [16]

    Relan,Nginx HTTP Server, 4th ed

    F. Relan,Nginx HTTP Server, 4th ed. Packt Publishing, Birmingham, UK, 2021. Rahul Patelis a final-year B.Tech student in the Department of Electronics and Communication Engineering at the Indian Institute of Information Technology, Surat, India. He completed an internship at the Indian Institute of Technology Gandhinagar during his eighth semester, where ...

    work page 2021