I'm not the OP, but there are some changes to background execution limits that can have a fairly large impact on older-than-Oreo apps if you build against SDK 26:
You've been able to avoid dealing with these changes for a while now by simply building against an older SDK, but Google is in the process of restricting the ability to put any app built with an older SDK on the Play Store. I think you already can't list new apps that use an older SDK, and existing apps won't be able to update to new APKs using older SDKs starting in November.
FWIW, I understand why they made the changes here, and they are user-positive, and just abandoning Android over them seems like an incredible overreaction, but speaking as someone who has been updating an older app to deal with these changes, there are some real pain-points here if you're bringing forward an older app.
> existing apps won't be able to update to new APKs using older SDKs starting in November
So, some developers will probably defer handling the changes until November, and then if there is some critical bug (security or otherwise) they won't be able to just fix the bug without also building the rest of the app with the new SDK as is, broken/untested even if it compiles?
https://developer.android.com/about/versions/oreo/background
You've been able to avoid dealing with these changes for a while now by simply building against an older SDK, but Google is in the process of restricting the ability to put any app built with an older SDK on the Play Store. I think you already can't list new apps that use an older SDK, and existing apps won't be able to update to new APKs using older SDKs starting in November.
FWIW, I understand why they made the changes here, and they are user-positive, and just abandoning Android over them seems like an incredible overreaction, but speaking as someone who has been updating an older app to deal with these changes, there are some real pain-points here if you're bringing forward an older app.