3 ms·
It seems very analagous to a FLOSS-only desktop experience (for a while I think Fedora Linux was one). It was not a polished user experience, and certainly som
by aray 13y ago
It seems very analagous to a FLOSS-only desktop experience (for a while I think Fedora Linux was one). It was not a polished user experience, and certainly some things were lacking, but when I used it I was able to accomplish all the things I needed done (and face it, most of those can be done by the web browser anyways).
The other reason I have hope for this is most of the non-FLOSS functionality is available at least in some form in web apps, or in a F-Droid application. Google Maps, Gmail, Twitter, Facebook, etc all have pretty good (capable, functional) mobile web applications, and all you need FLOSS for is the web browser.
- micampe 13y agoWhat is the difference then if you are still using proprietary services that run proprietary code, just on a different CPU? You are not gaining anything from the change other than the inconvenience of "pretty good" web applications instead of local native applications: you still can't modify them or verify their behavior.
- aray 13y agoIt depends on what your goals are. If you want a system that's only running open-source-built code on your device, but are willing to have your device interact with devices running proprietary software, then mobile web applications are fine. If you only want to interact with devices and services that are using open source software, then you're likely not to miss e.g. Google Maps application in the first place.
- micampe 13y agoYes, of course, but that’s a tautology. What would the first goal achieve over running the Twitter app on my phone?
- IgorPartola 13y agoSecurity, for one. It is much harder for a web app to key log your phone than to a native app.