Echoing jlongster's thoughts, I have experiences this first hand working at Tact.ai (https://tact.ai https://tact.ai) in the sales domain, which forces us (well

Echoing jlongster's thoughts, I have experiences this first hand working at Tact.ai (https://tact.ai https://tact.ai) in the sales domain, which forces us (well, at least pre-covid) to think local-first if you want to succeed. Most salespeople are always on the go, travelling through areas of bad network, or in flights (which many salespeople consider wasted time because their tools all need a constant internet connection, and that's one of the domains where "time is money" is a core tenet). So when we started building, "local-first" was a strong differentiator for us and became a core philosophy for the company. For the app we have, 95% of functionality works perfectly well offine (except some features that need third party API interaction that we've not found a clean way to set up so far). Sure, it's so much easier to write a webapp and then add a webview on top of it and call it a "mobile app", but the effort (syncing data which can be edited in multiple places in an local-first world is a crazy engineering challenge) that goes into building a local-first app really pays dividends in the longer run.