Hacker News new | past | comments | ask | show | jobs | submit login

My thoughts exactly. I have two apps out on Google Play. They are full featured, stable, and people still like them. I just want them to to continue to work. But they don't. I need to constantly take away from my time developing new apps to fix my newly broken old apps. How many times, Google, are you going to try to "fix" the problem of apps draining battery in the background? It never seems to end.

On the flip side, my first programs that I wrote for myself in the 90's still run. Yeah, I know that DOS is emulated now, but MS made them still work, and I didn't even have to re-compile.

I have this conspiracy theory that Google is purposefully trying to make things difficult to get rid of developers that don't have a lot of resources.




I have the same problem.

I think Hanlon’s Razor applies -- this isn’t intentional, it’s just unfortunate mistakes.

I think the main driving factors are:

- Many Android APIs were badly designed from the start;

- Android was not designed for easy OS updates, so many users have old OSes;

- Google like Apple’s approach of aggressively deprecating old APIs, and try to do the same. But unlike Apple, they still have to deal with old OS versions, and their fundamental OS design is not as sound. The end result is what we see, messy and buggy APIs.


>> I have this conspiracy theory that Google is purposefully trying to make things difficult to get rid of developers that don't have a lot of resources.

I agree and Apple does this on iOS as well. It's a way of clearing out old apps.


Same




Guidelines | FAQ | Support | API | Security | Lists | Bookmarklet | Legal | Apply to YC | Contact

Search: