Well as an Android dev, if you didn't already have a deprecation strategy in place, then that's not really a commercial standard app IMO. Since forever, at leas

Well as an Android dev, if you didn't already have a deprecation strategy in place, then that's not really a commercial standard app IMO. Since forever, at least for networked apps, we need to be able to deprecate APIs, and know which client versions we explicitly test and support etc. (It's easy to do, along the lines of: simple HTTP call to check latest and minimum supported app version at start up, or once a day or whatever; compare with current app version; then nag, force or do nothing as appropriate). This might turn out to be a helpful feature from Google... then again it might turn out to be half implemented, have a confusing user experience, not work properly for most usecases, and mainly serve to confuse new developers with yet another thing to learn, when all they needed to do was a bit of HTTP and layout work. 8 years doing Android, I'm 50:50 about most of Google's "help" until I've seen it in action.