Abstract
Most institutional software deployed in African field settings fails for a shared, architectural reason: it assumes continuous connectivity that does not exist where it is meant to operate. This revision adds a scope section distinguishing the paper's architecture argument from a measured outcome; grounds "offline-first" in the published local-first software literature (Kleppmann et al., Onward! 2019) and the well-established CAP/eventual-consistency trade-off (Vogels, CACM 2009) — while being explicit that both were developed for personal and creative cloud apps, not institutional field software, so the architecture transfers but the original evidence base does not; places Flux's own unaudited field-deployment data (AccessWASH, BungeConnect) alongside regional connectivity statistics (GSMA's 13% Sub-Saharan Africa coverage gap and 60% usage gap, 2023) and Kenya's supply-side mobile-subscription data (Communications Authority of Kenya, June 2025), clearly separating what each does and does not measure; and adds one independent, peer-reviewed confirmation from a different African sector — a 2021 account of mobile data collection during an immunisation programme review across East and Southern Africa, where intermittent connectivity delayed submission and an offline-first queue prevented data loss. An earlier, unsourced claim about Kenyan rural power outages correlating with connectivity outages is now stated as a plausible, unverified mechanism rather than fact. Objections (including Flux's commercial interest in both products discussed), falsification conditions, limitations, and both appendices are added. Three measurements the argument needs and lacks — the share of African institutional software failures actually caused by connectivity-architecture mismatch, an independent audit of Flux's own field data, and the Kenya-specific power/connectivity correlation — are registered CITATION-NEEDED rather than estimated.