I completely agree. As an app developer, it gets very frustrating to see a certain percentage of users who are dealing with issues and not having a consistent a

I completely agree. As an app developer, it gets very frustrating to see a certain percentage of users who are dealing with issues and not having a consistent approach to solving their issues. It's definitely gotten to a point where we have 3 classes of devices (and thus users) similar to how PC software used to be (and probably still is). 1. Performance: These devices can run your app smoothly even with a large number of assets demanding computational/graphics processing. 2. Basic: These devices can open and run your app but it starts to lag when pushed to the limit. 3. Incompatible: These devices don't make the cut in terms of specs and it's worth not even allowing the app to be downloaded. The quickest way to deal with this is to eliminate the bottom wrung of devices by choosing only to deal with the more recent Android versions since older devices may not be able to upgrade. From there, it's probably worth excluding certain devices based on your app's performance trends (crashes, lags, customer complaints). Obviously, the most optimal solution is to continuously optimize your app to further include more devices.