There's a few subtle points here. One is that I don't think the article actually disagrees with you — it just assumes internet access is readily available for t

There's a few subtle points here. One is that I don't think the article actually disagrees with you — it just assumes internet access is readily available for the sake of argument, and moves on to explain why offline-first matters even despite that. The more interesting point is that "internet access is flaky" isn't necessarily a good argument for going offline-first. Rather, it only suggests that you need your client to be more resilient to being knocked offline in an online-first world. Rather, the article argues that an offline-first is interesting unto itself as a completely different architecture that's closer to a desktop application where the binary is delivered through a browser. Put differently — they're not trying to argue you should make Gmail work offline, but rather that you should consider structuring your application as Thunderbird inside the browser.