3 ms·
A much broader reach with low barrier to access, a potentially less fragmented repo, and control over your platform would all be reasons to go web first. No ins
by brailsafe 6y ago
A much broader reach with low barrier to access, a potentially less fragmented repo, and control over your platform would all be reasons to go web first. No install, more control over subscriptions, lower barrier to deployment, would all maybe be other benefits. Not that those things can't be had with native binaries, but it would require different kinds of complexity
- userbinator 6y agomore control over subscriptions Not exactly something users want.
- atat7024 6y agoBut yet something they've continued to give up year after year because they're not being taught how to manage their technology, they need the handhold stuff (SaaS).
- rualca 6y ago> Not exactly something users want. Not quite. Users want to get bugfixes and the latest and greatest without being bothered by updates and upgrades and popups and progress bars. Even with automated processes, app update fatigue is a problem. If your use pattern already involves reloading/redeploying the app at start, that fatigue goes away. What users do not want is losing features they care about, or see breaking changes in their workflow.