My account got closed for inactivity while I had multiple apps published. Google does not understand the concept of a finished app apparently, and requires you to continuously push updates or else you permanently lose your account with no way of reopening it.
That has nothing to do with what I was saying on my comment, and there is a reasoning on Google and Apple's attitude, it isn't only money grabbing.
For starters, there are many "done" apps that are like Swiss cheese in terms of security.
And that would have been fine, if Google hadn't tried to shove the Google Play Store ecosystem down everyone's throat by throwing up barriers for side-loading apps and such.
When APIs get replaced they won't work anyway.
People love to bash how Microsoft manages Windows, yet they keep forgetting that Microsoft is one of the few OS vendors that actually keeps the APIs around, instead of having a deprecation process, finalised by actually removing the APIs, or hard forcing the new behaviour.
bramhaag · · focus · HN ↗
pjmlp · · focus · HN ↗
Apple does the same thing.
Alternative are having applications in 2026 that use POSIX like in UNIX System V, or Win32 like in Windows 95/NT 3.51.
weikju · · focus · HN ↗
If only……
pjmlp · · focus · HN ↗
m4rtink · · focus · HN ↗
pjmlp · · focus · HN ↗
For starters, there are many "done" apps that are like Swiss cheese in terms of security.
jsiepkes · · focus · HN ↗
And that would have been fine, if Google hadn't tried to shove the Google Play Store ecosystem down everyone's throat by throwing up barriers for side-loading apps and such.
rbits · · focus · HN ↗
pjmlp · · focus · HN ↗
People love to bash how Microsoft manages Windows, yet they keep forgetting that Microsoft is one of the few OS vendors that actually keeps the APIs around, instead of having a deprecation process, finalised by actually removing the APIs, or hard forcing the new behaviour.
<a href="https://developer.android.com/guide/app-compatibility" rel="nofollow">https://developer.android.com/guide/app-compatibility