Sorry, not familiar with Android core. For your example, how would it work without proprietary technologies? AFAIK, Android uses GCM for notifications. Adding integrations for it don't seem to make much sense in core open source Android as that will make you tied to Google's ecosystem.
Both are serving the same purpose, for different apps. Even before we get to network connections and servers (the things that might make sense to be proprietary), without Google's ecosystem the local side has a bad UX and requires hacks.
That is just because they are not using something like https://bubu1.eu/openpush/ and instead implementing their own push services. This is not a problem with Android but with the apps.
I was speaking about _local_ notifications, not push: some clock / reminder apps never fire notifications or way too late. I think it's because the OS aggressively shutdown apps running in background.
It doesn’t have to do anything, but if it doesn’t support what are considered standard features of a phone today in an open manner, it’s hard to take AOSP seriously as an open platform.
Also worth noting that when someone does build on top of AOSP, they are at the mercy of Google’s roadmap for the closed versions of Android.
The fact that this is possible is something I have commented about on this very forum for years. It is trivial for the Amazons and Huaweis of the world to build an API like this that supports Google's FCM, Amazon's ADM, etc. and provide a library for developers to use that will let them easily deploy push-enabled apps on devices across all ecosystems.
It is already usable. Nobody would claim that a Linux distro isn't open just because it doesn't have a built-in push API. You can build one on top for other apps to use, and you can do the same on Android. This is notably different from iOS.
You're essentially suggesting that Android should have Tor built in. The point is that it's possible to use other push services on Android and has been done, just like it is possible to use Tor on Android. There is no reason that AOSP itself needs to implement Tor any more than Windows or AOSP needs to provide a push API. Both are possible to implement on top of the platform and have been implemented on top of the platform.
This is unlike iOS, which is the real broken platform.
Push messaging is a service, just like anonymous proxies are a service. It doesn't make sense to put them into a platform if they can be built on top of the platform. It would make sense to put something like this into iOS because it can't be built on iOS. It doesn't make sense to put it into AOSP.
Earlier you said AOSP had a framework for push notifications, a statement found to be false when checking the links you provided.
Now you say it doesn’t make even sense to put this feature in the platform, confirming that you were lying when you said it already was part of the platform.
AOSP has a framework to support multiple backends. It's called the Service framework. With it, you can build a library to simplify dealing with backends, and I pointed you to one such library.
> Now you say it doesn’t make even sense to put this feature in the platform
Of course it doesn't make sense to build that library into the platform.
> Why are you talking about iOS?
iOS doesn't provide the ability to make this possible, which is probably why you are so confused.
Do you still claim it’s already usable? If not, why did you say it is?
You say: “Of course it doesn't make sense to build that library into the platform.”
I agree, but nobody is talking about building that library into the platform. The comment you are replying to is talking about the feature, not that library:
“Now you say it doesn’t make even sense to put this feature in the platform”
Do you think it makes sense to put this feature into the platform?
> Do you think it makes sense to put this feature into the platform?
How many times do I have to tell you that it doesn't?
Do you think AOSP should have a framework specifically for uploading photos to a photo sharing service in the background? That is another standard feature for smartphones. Of course not, it just needs the ability to support uploading photos to multiple services, and people can build libraries on top of the platform to make it easier. This is notably another thing that is not possible on iOS.
> You pointed me to an abandoned codebase.
And another one that isn't abandoned.
> Do you still claim it’s already usable? If not, why did you say it is?
No. I assumed it was because they had already announced it. Any developer who would like it can simply finish the library themselves.
We seem to be in agreement except for your wacky ideas of how much should be in the platform vs. how much should be built on top of the platform.
If they do the same with Fuschia, they'd better make it closed sources then.