Google has a new way to call out poorly made Android apps

Those general categories may sound familiar if you’ve been following the news out of I/O. They’re in line with Android O’s “vitals,” areas where Google is focusing efforts to improve overall Android device performance. According to Google project manager Fergus Hurley, the company will find more areas to key in on eventually but these required the most attention. Anyway, Google is specifically concerned with six “vital” metrics now — pardon the brief diversion into highly geeky territory. It’s all about the percentages of users that…

  • got the “Application not responding error”
  • experienced at least one app crash
  • had an app keep their device awake for more than an hour
  • experienced an app that woke up their device more than 10 times an hour
  • saw the app run at slower than 60 frames per second
  • ran into “frozen,” laggy frame rendering

Obviously, technical limitations mean some devices are more prone to those issues than others. Even so, this more explicit line of communication has the potential to up the quality of the Android app ecosystem as a whole. After all, developers who fall short on any of these fronts aren’t just doing screwing over their businesses. They’re muddying up the entire ecosystem. At this point it’s not clear whether habitual re-offenders will see their apps removed from the Play Store, but one thing is clear: developers who can’t hack it will start to see their apps’ rankings changed.

Google announced back at the Game Developers Conference in February that how well an app performed would have an impact on its “promotability” — in other words, an app that falls below the 25 percent threshold in any of those metrics will probably start sinking into obscurity. Sure, it’s just one of many signals Google uses to figure out how apps get ranked — it’s just about time they held app creators to some more stringent standards. Who knows: it just might help them rack up a few billion more users.

For all the…

Read the full article from the Source…

Back to Top