@fdroidorg here's a classic #Google tactic: use "open source" to get devs hooked, then gradually slip in proprietary bits. #AOSP's core apps move ever more towards proprietary, and they also do this with libraries like com.google.ar:core https://github.com/google-ar/arcore-android-sdk/issues/1538
@eighthave @fdroidorg I'm pretty sure that the only reason Android is open source to begin with, is that Google didn't create Android. They just bought the project to not have to start from scratch, so they could have any chance to compete with Apple and iOS at the time, who already happen to be a rather popular thing back then.
@hund @fdroidorg Google did buy Android, but it was proprietary then, and Google open sourced it. They were tactical, doing that to get developers' attention, given all the other mobile platforms were proprietary then. Now Android is the biggest platform in the world, and Google controls it, and they want more control. So they go proprietary.
@vesperto @eighthave @fdroidorg I'm sometimes pondering possibilities of using the same EEE strategy in a "reverse" direction, i.e. for pulling people into Free Software. I'd love to try doing it esp. for email some day, but I think I might not have enough free time in my life for this, between work, peopleware, and other projects.
Email's probably the worse place to start (and thus the most needed):
I'd go with messengers.
@vesperto @eighthave @fdroidorg I wanted specifically to start with an email _client_ with some innovations I have on my mind, then possibly adding friendly encryption and also maybe transparently integrating other messenger systems. But, as I said, my ETA currently is +Infty... (Unless I somehow get to be financed to work on stuff like this. But even then some projects with a saner ETA are pragmatically higher on my list. In fact, planning a half-year sabbatical for one soon.)