4 ms·

>Trying to keep up with the Google treadmill of required changes is extremely difficult for someone with a side project (I don't know if FairEmail is full time

>Trying to keep up with the Google treadmill of required changes is extremely difficult for someone with a side project (I don't know if FairEmail is full time for its author). Example: I need to rewrite large portions of my app to use scoped storage, but even using the example code from the Google API docs already gets flagged as deprecated. I mean, I sympathize, but that's sort of the agreement you make if you want to be in the Play Store, right? Like, if you don't have time to maintain your app, that's totally OK -- but at least you have other methods of distributing your app if you want. But if you want to use Google's distribution platform, following their rules for what is and isn't allowed seems fair.

chimprich 4y ago
> following their rules for what is and isn't allowed seems fair It depends on how you look at it. That is literally the deal, yes, but it's a poor deal for developers of free apps. We make Android's platform more valuable, for free, and in return we have to constantly rewrite our apps because of poorly-thought out policies that keep changing. The suspicion is that many of these changes are unnecessary and a result of Google's notorious "promotion-driven development". I think the most annoying aspect of it is that Android changes so often and so fast that they can't even keep their own documentation in sync.