3 ms·
Perfectly fair response. I think your examples are also good evidence that people like native software, or at least the appearance of a cohesive platform. Appar
by smoldesu 3y ago
Perfectly fair response. I think your examples are also good evidence that people like native software, or at least the appearance of a cohesive platform. Apparently "non-native" apps like an SPA or WASM tool will probably turn most normal users off. Good enough native support can make a web client redundant, even if 'native' means Javascript with OS-native controls.
To counter that though, I think we have to define SaaS concretely and ask what a more service-driven world would look like. I consider SaaS to not only be the paid components of an OS, but also the "free" services like Google and the App Store. Holistically speaking, our OSes are saturated with services; Find My, Android Notify services, OCSP/Microsoft/Google telemetry, online certificate signing, and even 'assistants' that fail to assist without internet. What more could we possibly put online?
It's a bit of a rhetorical conclusion to leave things on. I'll certainly see worse examples in my lifetime, but the status quo is bad enough in my opinion.
- fulladder 3y agoI agree with you about the absurd degree of service saturation. I've discovered many things I cannot do without an Internet connection because one trivial step in the process absolutely requires communication with some network endpoint. I found one app where, if you block it's ability to send analytics reports back to Mixpanel, it will run 3 or 5 times but after that refuse to run again until an Internet connection is available. I thought it was absurd since it proves the developers actually considered offline use cases, but decided that they couldn't allow that to go on indefinitely. Anyway, sure, let's leave it there and see where things are in 5 years. It'll be interesting to find out!