and google will be doing everything they can to grow incompatibility and make maintaining an open fork impossible. don’t forget that google employs devs for pay, but fork maintainers are doing it as a hobby, out of passion, while already working somewhere. It’s a bit similar to matrix, its homeservers and clients. the spec and the software evolves slowly, but its still too fast for alt implementations
Google can only do that if they can maintain grip on the market. This requires the likes of Samsung, who also contribyte to android, to move with them to their then propiatary solution.
Google is not going to win this just with their Pixels.
Google closing android would ruffle a lot of feathers so it definitely wouldn’t be a given they would come out of that on top.
Apple has no problem existing outside of Google’s sphere of influence.
And honestly if the android market would split and you’d get legitimately google-less phones with large app stores that google doesn’t control that would be fairly beneficial if you ask me.
This requires the likes of Samsung to move with them to their then propiatary solution. Google is not going to win this just with their Pixels.
I don’t see why samsung wouldn’t accept this change. do they make use of the AOSP project? if they do, wouldn’t they be able to make a deal with Google to have access to the code?
I mean.
They could go with google and most ideally change nothing, or stay with the open source project and try to cut out a slice of the appstore pie for themselves.
PostmarketOS can’t happen fast enough
LineageOS, & GrapheneOS hopefully will still be good for now
As a GrapheneOS user I’m with you on this. Hopefully this won’t negatively impact the development of GOS. I feel like it will though.
I wonder how this will affect Ubuntu Touch.
If google where to close android it’ll undoubtedly be forked. Pretty sure the likes of Graphene and Calyx will be fine for the forseeable future.
and google will be doing everything they can to grow incompatibility and make maintaining an open fork impossible. don’t forget that google employs devs for pay, but fork maintainers are doing it as a hobby, out of passion, while already working somewhere. It’s a bit similar to matrix, its homeservers and clients. the spec and the software evolves slowly, but its still too fast for alt implementations
Google can only do that if they can maintain grip on the market. This requires the likes of Samsung, who also contribyte to android, to move with them to their then propiatary solution. Google is not going to win this just with their Pixels.
Google closing android would ruffle a lot of feathers so it definitely wouldn’t be a given they would come out of that on top.
Apple has no problem existing outside of Google’s sphere of influence. And honestly if the android market would split and you’d get legitimately google-less phones with large app stores that google doesn’t control that would be fairly beneficial if you ask me.
I don’t see why samsung wouldn’t accept this change. do they make use of the AOSP project? if they do, wouldn’t they be able to make a deal with Google to have access to the code?
I mean. They could go with google and most ideally change nothing, or stay with the open source project and try to cut out a slice of the appstore pie for themselves.