Android
DROID DOES
Welcome to the droidymcdroidface-iest, Lemmyest (Lemmiest), test, bestest, phoniest, pluckiest, snarkiest, and spiciest Android community on Lemmy (Do not respond)! Here you can participate in amazing discussions and events relating to all things Android.
The rules for posting and commenting, besides the rules defined here for lemmy.world, are as follows:
Rules
1. All posts must be relevant to Android devices/operating system.
2. Posts cannot be illegal or NSFW material.
3. No spam, self promotion, or upvote farming. Sources engaging in these behavior will be added to the Blacklist.
4. Non-whitelisted bots will be banned.
5. Engage respectfully: Harassment, flamebaiting, bad faith engagement, or agenda posting will result in your posts being removed. Excessive violations will result in temporary or permanent ban, depending on severity.
6. Memes are not allowed to be posts, but are allowed in the comments.
7. Posts from clickbait sources are heavily discouraged. Please de-clickbait titles if it needs to be submitted.
8. Submission statements of any length composed of your own thoughts inside the post text field are mandatory for any microblog posts, and are optional but recommended for article/image/video posts.
Community Resources:
We are Android girls*,
In our Lemmy.world.
The back is plastic,
It's fantastic.
*Well, not just girls: people of all gender identities are welcomed here.
Our Partner Communities:
view the rest of the comments
Funny thing is that Google does the same thing all the time. Back when Microsoft released Windows phone, they had made a few really amazing apps. One of them was their email app. Google went out of their way to ensure Gmail would never work on it past the basic functions of reading and sending email. They also pretty much forbid YouTube from working on windows phones.
The email thing stuck out the most because Google announced they were dropping support to whatever protocol Microsoft was using to communicate with Gmail servers, then Microsoft announced they would use a different protocol and next week Google went "oh right we are also dropping support for this other protocol".
That's fair. As a developer that has been burned by Google dropping support for shit they created, I can't say for certain it was malicious or just Google being Google.
They used to create a ton of tools and protocols and drop support a couple years later because it wasn't worth it to them to maintain it. Lots of pet projects used to get promotions, but no budget for sustained support.
A big client onboarding and exposing major flaws could absolutely shine and unwelcome light and force them to take a critical eye and come to the conclusion of "yeah, everyone that worked on that has moved on, it'd take too many resources to revive it, and it's just going to help our competitor anyway. Our business need for it is gone because does similar things. Cut the cord"
It sucks, and isn't an excuse. I stopped using Google dev tools because of it long ago. Very unreliable. But I don't think it's the same intent as Apple by a long shot.
Yep. Apple may be shits for hand in this, but no one should kid themselves into thinking Google is the “good guy” in this. The only reason they are trying to play the interoperability and open standards card is because they have tried everything else and it has fallen on its face.