Hacker News new | ask | show | jobs
by zepto 2024 days ago
An open platform would have a framework that supports multiple back ends.
2 comments

This would be definitely nice to have but why does core Android itself need to have support for every feature?

We can have open source OSs on top of Android that build with a specific service set. Sort of how Ubuntu builds over Debian.

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.

To clarify - I should have said: “it’s hard to take AOSP seriously as an open phone platform”
It already does. https://bubu1.eu/openpush/

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.

Already does?

“The OpenPush project aims to create ... Development is still ongoing.”

Doesn’t sound like it from the website.

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.
Is it already usable?

The repo says it is unfinished, and commits seem to have stopped a year ago. It looks like it has been abandoned.

Has it been used in production somewhere?

Here's yet another option that does essentially the same thing but doesn't provide a reference implementation for self-hosted push server. https://github.com/onepf/OPFPush/tree/master/samples/pushcha...

I wouldn't be surprised if Amazon has their own internal implementation of the same thing to use in their Android apps.

So, no. It’s not already usable and there are no complete alternatives you can point to.

You speculate that Amazon may have an internal framework for this, but so what? Even if your guess was correct, that’s not AOSP, and it’s not open.

Your statement that AOSP ‘already does’ this simply isn’t true.

It seems like you don’t distinguish between things that are possible in principle, and things that are actually true.