Implementation of an Offline-First Progressive Web App Architecture for Transactional System Resilience
bit-Tech · 10.08.2026 · 9 (1) · 1059-1070
DOI: 10.32877/bt.v9i1.4044 ↗Kurz gefasst
Fachartikel in der Zeitschrift bit-Tech, online erschienen am 10.08.2026. Verfasst von Nugraha Nugraha und 2 weiteren Autor:innen. Der Volltext ist frei zugänglich (Open Access, CC BY-SA 4.0).
Abstract (Originalsprache)
Transactional Point of Sale (POS) systems require continuous transaction capture, responsive user interaction, and low tolerance for queue loss under unstable connectivity. The Mangkasir web dashboard, developed using Next.js, previously followed an online-only workflow in which failed HTTP requests during network disruption could interrupt cashier operations and leave transaction payloads unsaved. This study aims to evaluate the architectural feasibility of an Offline-First Progressive Web App (PWA) strategy for preserving write-heavy POS transaction queues during controlled network failure scenarios. Using a prototyping development model, the architecture integrates Service Worker-based request interception, IndexedDB-based local queue persistence, and Background Sync-based asynchronous transmission after reconnection. The implementation was evaluated through Black Box Testing, load synchronization testing, and controlled multi-device concurrency testing. The results show that the proposed architecture successfully intercepted failed transaction requests, maintained interface responsiveness, and preserved 100% of locally queued transactions under the tested conditions. After connectivity was restored, the Background Sync mechanism synchronized queued payloads asynchronously, processing 100 transactions in 42.60 seconds without observed transaction loss in the evaluated scenarios. Multi-device testing further indicated that simultaneous offline queues from three devices were synchronized without detected duplication or race-condition errors. These findings support the feasibility of Offline-First PWA architecture for improving transactional resilience, but they should not be interpreted as evidence of complete operational readiness. Further validation is required for payment reconciliation, inventory consistency, server failure recovery, browser compatibility, interrupted synchronization, transaction cancellation, and the security of locally stored financial payloads.
Zitieren
APA
Nugraha, N., Somantri, S., & Rofiqi, A. (2026). Implementation of an Offline-First Progressive Web App Architecture for Transactional System Resilience. bit-Tech, 9(1), 1059-1070. https://doi.org/10.32877/bt.v9i1.4044
Vancouver
Nugraha N, Somantri S, Rofiqi A. Implementation of an Offline-First Progressive Web App Architecture for Transactional System Resilience. bit-Tech. 2026;9(1):1059-1070. doi:10.32877/bt.v9i1.4044
BibTeX
@article{Nugraha2026,
author = {Nugraha, Nugraha and Somantri, Somantri and Rofiqi, Ahmad},
title = {Implementation of an Offline-First Progressive Web App Architecture for Transactional System Resilience},
journal = {bit-Tech},
year = {2026},
volume = {9},
number = {1},
pages = {1059--1070},
doi = {10.32877/bt.v9i1.4044}
}
EUVIMED