Live Stats

Google Analytics data

As I mentioned earlier, here's the latest google analytics data over the period that I've been logging.

Popularity by page.

The above image shows a figure for the total number of hits tracked for each page or screen in the app that a user can look at. Although there are only a number of activities or screens that are re-used in the app implementation, when ever the data for a different game type it is tracked as if it were a separate page on a website.

Mmmmmm... pie.

The above chart shows the game results look up relative to each other game type. Lotto is a clear dominator.

Stats over time per page.

These graphs plot the number of page tracks over time which is interesting, as a clear trend of when people actually use the app can be seen. If you note that the graph spike on Wednesdays and Saturdays for the Irish lotto. EuroMillions turns up on Fridays, however interestingly people checked Euro Millions results more on Saturday. The number of people visiting each page actually reflects pretty I think on how many people play each game from my experience selling lotto in my previous retail job.

Live stats

The last image is the live tracking section of google analytics. This is the most I've witnessed people using my app at a single point in time, although it's entirely possible that there have been more people using it at once and I just hadn't seen it. It's interesting watching as individual clicks on pages scroll across the screen in real time. Obviously it's better to see in video format than a still image, as the interface is animated.

Lotto Checker stats, now with analytics results!

It's been an interesting few days with the inclusion of google analytics, however downloads is quickly approaching the 5000 marks, and with the inclusion of google analytics I now have a better idea of how people are using the app. The first day I updated my app to include analytics I saw that on Saturday 746 people started my app, with 452 on Sunday. I updated the app on Friday, so I would imagine that a lot of these hits were due to people checking out the app to see if there was anything new. I will have to observe the numbers over a longer sample period to gauge the weekly trends. It will be interesting to see next weekend and on Wednesday if the trend matches this Weekends usage, as the Irish lotto games are on Wednesdays and Saturdays.

I'm also looking at the pages that people are viewing. There were a total number of 1872 pages tracked on Saturday night, 778 of which were Lotto. An interesting observation is that my app has had more page view tracks than this blog has had in the number of months I've been posting to it. There were quire a large number of Lotto checks on Sunday as well at 498, probably because people might have resorted to checking numbers the day after the draw.

One of the most interesting parts of google analytics is the way in which you can present the data. The live data tracker is also quite impressive, where you can witness page events being tracked in real time on a sliding graph. It also gives you insight in to how many users were on the app at any given time.

I'm going to get back developing my Driver Tools app this week and try and get some debugging done on the graph information. There are a number of other design features I would like to review also, however I can't think of them at the minute. I'll have an update later on in the week.

Lotto Checker 1.5

I updated the lotto checker app today with the session class that I wrote for the Driver Tools app. It contained all the functionality for tracking the activities a user will start in my app. In the lotto checker app, I track when the app is started up, and when ever a user displays the results for a game, that is also tracked. This will help me in deciding on what an how I use analytics in the Driver tools app, and it will give me a better idea of how used my lotto checker app is, so that I can improve different aspects of it in the future.

The total number of downloads for my Lotto Checker app now stands at 4,373 total installs (users) and 3,028 net installs (devices).

Android market update

First of all, my lotto checker app has surpassed 3000 downloads.

Secondly, I saw the following image posted on the Android development blog. It appears that the number of apps downloaded from the android market place has almost doubled since June. That's some pretty impressive growth

First week in new job!

Last Monday I started a new job with Realex Payments as an Integration and Support Analyst. It has been an exciting week becoming familiar with my new role in the company, but unfortunately I hadn't had much time to work on my android projects lately. My weekday consists of an early start out in Monkstown which involves an hour of sitting in traffic every morning. After work after about another hour of sitting in traffic I battle falling asleep on the couch at home, so I'm usually too tired to work on projects in the evening. I do however have weekends off which is new to me, because of my previous job. I plan to make full use of this perk and get some solid development time in on the weekends that I now have off.

This weekend I'm planning on getting the back end of the app set up with a few classes for storing information about different things. I'll do a bit of reading tonight so that I'll be ready to get stuck in tomorrow and hopefully I'll have something worth adding to the project by tomorrow night.

Also, a quick stats update for the lotto checker app. I'm currently at 1859 installs and 1461 active installs. This is a 78.59% success rate with users, and my impression would be that a lot of UK users probably download my app due to the fact that it is featured in the top 30 in the productivity section of the android market with out realising that it is targeted at Irish users for Irish lotto results. I'll have a look at the UK lotto website and see if that may be something to incorporate in to the next iteration of that project.

Driver Tools

I've decided to get back in action developing apps with a brand new app. The reason I'm starting on a new app while I'm still testing and publishing updates for my last app is because I'm starting a new job on Monday which involves driving across town quite a distance every morning and then back again in the evening. I want to develop a driver tools app which will log fuel economy over time and it will contain a bunch of other tools for a driver to be able to adapt their driving style for a more economic drive. I feel this tool will be useful to me in the upcoming weeks as I drive to work.

Some of the things I would like the app to feature are graphing of fuel economy over time, tire pressure calculators and wheel size stats, route tracker which compares different routes on fuel economy and individual car profiles. This will mean that I'll be using APIs such as the GPS API and the databases API which is a side to android I have not yet used.

I've got an idea for the user interface design. I'm going to tab each of the functionality activities in tabs which I'm using this tutorial for. The methodology I'm going to approach this project with will be heavily orientated around good user interface design, robustness and security. I am also going to create two versions of this app, one of which will be free with ads the other will contain a bit more functionality and will not contain ads. I'll divided up the functionality and decide on how much I'll release for free once I've I'm in beta testing and I think I might release a beta on the market and update it until it is at an acceptable level of functionality to release a premium version.

In other news, my lotto checker app surpassed 1280 installs with just over 1000 active users today.

Android market update

I was in the middle of a post about what I'm currently coding at the minute, which shall be posted soon and I thought I'd give a quick update about my Lotto Results app that I uploaded a couple of days ago. So I decided to post a completely separate update for it.

According to the android developer console, so far I have had 75 total installs, 53 of which are actively installed. If I use the percentage of people who have installed my app and not uninstalled it having deemed it not worth using, I have a success rate of 73.9% which is not too bad at all.

Other stats include that the most of the users are using Android 2.3.3+ at 60.4%, Android 2.2 is second at 26.4% and Android 2.1 is only 11% of the user base. The last 2.2% is made up of a combination of Android 2.3, Android 3.0 and Android 3.1.

Mobile Devices by percentage of installs.

Rank	Device	User Share
1	Samsung Galaxy S2	15.1%
2	HTC Desire S	11.3%
3	HTC Desire	11.3%
4	HTC Wildfire S	9.4%
5	Samsung Galaxy Ace	7.5%
6	HTC Sensation 4G	5.7%
7	SEMC Xperia X8	5.7%
8	HTC Wildfire	3.8%
9	Samsung Galaxy Mini	3.8%
10	Samsung Galaxy S	3.8%

As can be seen in the the above table, 15.1% of installs were on a Samsung Gallaxy S2, with 11.3% of installs on HTC Desire S and HTC Desire each. HTC Wildfire S has 9.3% and Samsung Galaxy Ace has 7.3%. This gives me a lot of important information about what kind of screen size I am deploying to which will help me further in designing my user interface.

I would like to publish an update with the ticket checking functionality as soon as possible, so that hopefully I will be able to get more downloads and increase my install/uninstall ratio further.