Category Archives: Google Analytics

What I’ve been working on

As I’ve said before, I’m a casual programmer, and therefore take breaks occasionally. The past week or 2 have been one of those breaks.

Most of my time recently has been on getting my Nexus 10, replacing my N10, rooting my N10… I think you see the trend. (And the holidays just passed, so there was some extra time with family/friends in there too.)

I have done a SMALL amount of programming in that time… I played with Google Analytics a bit to see some of the things that can be done there. So far I have only built it into the free version, but will likely be copying that work into the paid version before I release the next update (and adding to it, since there are parts of the app that are not accessible in the free version.)

With analytics I am collecting the following:

  • Screen views
    • What screens the user views, how many times each screen is viewed, and how much time is spent on each screen
    • This includes basic screens as well as settings screens
  • Clicks
    • How many times each button is clicked
    • How many times list items are clicked
      • List items include your list of preset messages, do-no-respond list contacts, and in the paid versions, schedules.
      • This does not send any information about what information is IN the list item, just the fact that you clicked it, and what type of list item it was (a message, a schedule, etc.)
    • How many times list items are long-clicked
      • See above item
    • How many times list items are edited/deleted from the long-click menu
      • See above item
Things that have not been built in, but likely will be before I release an update:
  • Settings
    • What settings are being changed, and how the settings are being used
  • How often the response message is changed
    • Again, no information about what the message contains will be sent, only the fact that the message has been changed
Things that are NOT collected as part of this process:
  • Any kind of identifying information
    • Things like age, gender, name, account names, passwords, etc. will NOT be collected from analytics, or in any other manner, and never will be.
“Personal” information that IS collected:
  • Location
    • When I was doing my testing Google Analytics was able to tell me what town I was in, probably based on IP address.
    • This is NOT an exact location. I can NOT see that you are using my app in McDonald’s on Main Street in New Orleans (I don’t know if such a thing even exists, it was just a collection of random places) I can only see that the app is being used in New Orleans.
    • I most likely will not do anything with this information, aside from possibly seeing which countries use that app the most.
Just an FYI – this is information that probably 90% of apps out there are collecting, so I am not doing anything that other developers aren’t already doing. The only thing that I’m doing different is that I’m being 100% straight up about the information that I will be collecting. No fine print, it’s all right here in a public blog in an easy to read bullet list.
I have also found an easy way to exclude my own devices from this collection. I don’t care how I interact with the app…. I KNOW how I interact with the app… what I want to know is how my USERS interact with the app, and what features/settings they use the most.
I will use this information to improve the features that are used most often.

Also on the list of changes I have made:

  • changed some more “Cancel” buttons into “OK” buttons
    • I kept some as “Cancel” when it made sense
  • Added a “Share App” option to the menu
    • This will open a share dialog, where you can share a link to the app in the Play Store via any installed app that receives a share intent (Facebook, Twitter, Messaging, email, etc.)
I have not really been working on any new features, just small improvements. The next new feature that I will work on (when I decide to start working on new stuff again) is the ability to send personalized responses to specific individuals. I talked about this in one of my previous posts. It’s the ONLY feature request that I’ve received from users, and I’ve had multiple people ask for it.
Personally, I’d like to get a widget working first. But nobody seems too worried about that right now except me, so I’ll put that on the back burner. (Plus I’ve tried a couple times already, and been unsuccessful with it.)
As usual: Any requests, comments, concerns, etc…. you know where to find me. I’d especially like to get some feedback on what you think of the analytic information I’m going to collect. So if you have anything to say about it, feel free to leave a comment.

Google Analytics

Yesterday I started playing around with Google Analytics, and figuring out how to build it into Auto Respond.

The versions that are out now do not include Google Analytics in any manner, but I am looking into possibly building it into future versions. That would mean that the paid app would once again need internet permission in order to send the data back to Google, but this would be the ONLY information sent and there would be no personal information transmitted.

For those who aren’t aware, Google Analytics helps developers understand how users are interacting with their products. It will tell me how many times specific screens are viewed, how many active users I have, and potentially which buttons and other elements are interacted with most often.

This information can help me understand how you, as users, interact with my app. It can tell me which things you use often, which things you never really use, whether you tend to click buttons more than list views, and possibly even what settings are used most often.

I’m not sure of the exact information I can get, as I have just started playing with it, but rest assured that I will NOT be able to see that John Smith opened the app x times, or click this button, or has these settings set. I simply get a report for ALL of my users and cannot tell the difference between interactions from one user to the other. (I do not need, or care about, statistics on a per user basis in order to get useful information.)

I can then use this information to improve the parts of the app that are used most often. If people tend to use the scheduler a lot, I can spend some extra time with new features to give you more of what you want. Or if people use the preset messages a lot, maybe I can add more information to the list view, or create new sorting options, etc.

Or, on the other hand, if people tend to not click on my list views, I can make it more obvious to the user that clicking on the object will cause some action.

Overall I’m very excited to see what I can do with this tool! And once it’s set up I think it can greatly help me improve interactions in my app. The ONLY downfall is that the paid version will require permission to access the internet, which I think is a small price to pay for an improved app.

Let me know your thoughts, and if you have any experience with Google Analytics, feel free to let me know how it worked out for you!

TL;DR – Google Analytics will potentially help me understand how my users use my app, and help me improve the user experience.