I've been running the betas since more than a year without any problems whatsoever. (If you don't need push obviously)
I've been running the betas since more than a year without any problems whatsoever. (If you don't need push obviously)
I definitely struggle to udnerstand why IMAP IDLE is critical for a release.
Edit: Oh, probably a minSDK force - i.e. the cost of standing still in mobile development.
The functionality is present in the latest stable version, but needs to be reimplemented in the new version. As a user I would be upset if the app was updated and that feature taken away, even if it was only temporary.
Edit: oh, randomly spotted this:
> A major factor was the API level requirement by Google Play. It required us to make changes to internals of the app in order to be able to publish updates via the Play Store.
I don't get the problem. Why not do a release? If google doesn't want the hard work and updates yet, fine, you can still tag a new release and people can use f-droid, download the apk, whatever right? (I'm using it via f-droid, thought most people would be doing that since it's an open source client with graphics from the 2009, the kind of thing you only use as foss fan).
Historically, Apple gives you about a year before you have to compile against the latest SDK, and Google gave you a lot longer.
However, recently, both have become more aggressive about requiring new versions to be compiled against the latest SDKs.
Thus you can't do a "proper" release without moving up to the latest SDK.
Compiling against the latest SDK often breaks things, especially for an app which does a lot of things in the background.
This is part of the "cost of staying still" in mobile app development, which is both hard to predict, and can be very expensive.