My point about Play Services was that, despite Android being OSS, it is not sufficient to just set up AOSP. People still want to use apps, so you have to get a copy of Play Services. But Play Services is a Google blob, phoning home and the works. The higher-level stuff is what "matters" to people.
If Play Services were open source, then someone could release forks of that which patch out the questionable parts of it (just like Chromium/Chrome, in reverse). Efforts could be combined on the open source parts of things, so that we don't spend our lives rewriting battery-efficient geofencing services.
the gain from running on Android is that you can concentrate on higher-level value-adds first, to build adoption of your stack.
You could build out some cross-platform thing too, it's just that Android tends to make things a bit easier for swapping things out.
Sailfish sounds like a good option for this, but what I'm reading is that the people making Librem are spending a lot of effort building out a new OS mostly from Linux?
If Play Services were open source, then someone could release forks of that which patch out the questionable parts of it (just like Chromium/Chrome, in reverse). Efforts could be combined on the open source parts of things, so that we don't spend our lives rewriting battery-efficient geofencing services.
the gain from running on Android is that you can concentrate on higher-level value-adds first, to build adoption of your stack.
You could build out some cross-platform thing too, it's just that Android tends to make things a bit easier for swapping things out.
Sailfish sounds like a good option for this, but what I'm reading is that the people making Librem are spending a lot of effort building out a new OS mostly from Linux?