Use Android Vitals in the Google Play Console to Understand and Improve Your App’s Performance


28 comments

  1. This is very useful information, but does Google plan on applying these principles to their own apps? Google Play, Keep and Drive have very bad frametimes when loading content to the point they're annoying to use, but the Games app is just horrible and is just a stuttery mess that I avoid opening unless I really need to.

  2. I like the way how is Google explaining this to the developers as if they were dumb or never heard of it. We are aware, we care. Our customers don't.

  3. 2:05 from the Material Design Guidelines:

    "Avoid using floating action buttons for minor and destructive actions, including the following:
    – Archive or Trash
    – …"

  4. Half of 1 star reviews come from users blackmailing us for a feature request. Like "If you would add this I will put more stars."
    Jeez..

  5. Someone should forward these tips to Google. Gboard is eating away at my battery 100% of the time my phone is on. I managed to fix it for like a day by reinstalling, but today it started doing it again.

  6. This video was stuttering and hanging the entire time when played at or above 1.25x speed (other videos play fine at 2x). Google really needs to dogfood their best practices.

  7. #AskAndroidEmulator, today i got update android emulator, but the update make my emulator so glitch 😭

    https://stackoverflow.com/questions/45121828/android-studio-suddenly-got-gpu-driver-issue-when-running-emulator

  8. Hi I am beginner and i very passionate about how to develop android app so I create a project "My application" in android studio but I found problem in preview of "hello world" in preview section in android studio

  9. One of the most battery draining functions are "Runnable()" and "Timer()". Use "AsyncTask" instead of Runnable and your App will save battery. But since google doesn't provide a useful replacements for "Timer()", you have to manage it through some APIs over their servers and the like. This is not a real good solution, because the user has to be online, just for you as developer to trigger a method after a certain amount of time, although the smartphone has a clock for itself and there should be no use for this and a timer shouldn't drain the battery. There should be only ONE SINGLE Timer running on the smartphone, where all the values for all apps are being managed. But instead each app defines its own timer, and thus you have a massive battery drain, especially on smartphones with an old android version. So in my opinion it's more to google, that you optimize android libraries, so that I don't have to check through several kind of phones and APIs, and define their own way of data receiving through hardware or sometimes even just to calculate a kind of string format. That all should be done by the library. We developers shouldn't invent the wheel again with every application, that we write.
    And last but not least, a NEW VERSION should mean, that it's capable of dealing with the older versions. So if you have some new APIs, that are not capable of understanding or at least translating the older code into the new ones, then don't name it "A NEW API VERSION", but a "NEW LIBRARY" and don't name it android, but something else. The whole code of my very first application from 2012 is now fully deprecated and that's not the sign of a good planning, I'd say.

Leave a Reply

Your email address will not be published. Required fields are marked *