After some months, our old tracking domain is being decommissioned as of, well, right now in fact.
This will impact some people no doubt, however a much more expansive and instructional post for how to overcome this are here. Please drop us a line if you experience any real issues over on GetSatisfaction.com.Read More
Today we have released a new version of the appAnalytics SWC – version 0.04.0. You will need to
login to download it. If you have registered but not be activated this will happen today as well. While this update has been a long-time coming we hope that it has been worth the wait.
Before we get into what the changes are, a note to current users. The current tracking domain – my.appanalyticshq.com – will be decommissioned shortly. You will have a week to update your existing applications with the new SWC if you want to continue live tracking. Applications that are unable to reach this subdomain should continue to track locally, but their apps will need to be updated to get access to this locally stored data and send it on to the new tracking domains.
The goods news is that this should be the last time you will need to incorporate an updated SWC for some time. The solution has been re-architected to abstract much of the functionality into an encrypted payload which is able to be updated by us and pulled into your development environment. This process has been automated, meaning you won’t have to worry about whether you are working with the latest classes, appAnalytics now checks it’s version number and updates if required.
This allows us to rollout new functionality or bug fixes to the SWC without any end user involvement. All the developer has to do is keep abreast of the new functionality being delivered by the whole solution and take advantage of it. This means that we have to worry less about managing a release cycle in terms of the SWC and can now concentrate on updating the payload to quickly improve or fix issues in a way that is non-intrusive for everyone.
The new SWC is stripped down compared to previous versions, with almost all of the complexity now residing in the payload. The only real change that devs need to be aware of is that we have taken a decision to extend the parameters that can be passed through to the payload, and a small update to the tracking code used in your apps will be required.
The parameter set has previously been restricted to action, type, description but we have had a long discussion about including additional parameters such as “group” to allow for greater segmentation as we work through reporting suite enhancements. As we couldn’t forsee all such additions we have decided to allow for an array to be passed instead. Obviously anything can now be passed through, but only those parameters being expected by the tracking engine will be recorded – anything else will be discarded.
So, the new tracking code needs to follow this format:
AppAnalytics.track(["action", "type", "description"]);
Please note the inclusion of square brackets [ ] around the parameter group signifying that it is in fact an array. This is the only change you will need to make to use the new SWC and the functionality coming down the line.Read More
We are about to rip into the re-development of the reporting dashboard features and while we have some cunning plans of our own, what would you guys like to see included?
Some of the things on our list currently are:
- GeoLocation Data (installs, sessions, updates etc)
- Usage Segmentations
- OS capabilities
- Online vs Offline
- Session Times
Please feel free to drop us a line in the comments or post your ideas over at GetSatisfaction.Read More
The time has come for us to take a big step with AppAnalytics and we wanted to give you the heads up about what is going to happen over the next while.
Firstly thank you all for your feedback and active participation with what we are up to with this project. The data we have compiled has been invaluable in terms of approaching monetisation – which is still a way off to be honest – but also in terms of making decisions about infrastructure.
To that end, over the next week we will be decommissioning the existing my.appanalyticshq.com sub-domain in favour of splitting tracking and reporting functions. The reasons for this are many, but most importantly it provides us with flexibility in terms of scaling the application way beyond it’s current capabilities. We have found recently that too much load on the tracking system is impacting the reporting and we know as more users come on board this is going to have to change.
We also need to build into the application some protective measures for both AppAnalytics and specific users. To this end we have been working on a major revision to how the AppAnalytics SWC passes data to the tracking solution. These changes are significant and most importantly they provide us with some switches in terms of load balancing and throttling.
What we need you to be aware of is that the existing SWC will stop tracking when this sub-domain ceases. We know it’s a pain, but it’s pain we’d rather go through now to have a more scalable solution, then when we have SLA’s in place and commercial agreements with people.
This means that any applications you have in the wild will continue to track but use local storage up to a point. That point will depend on whether you decide to continue to use AppAnalytics in your apps or not.
If not, the applications in the wild will track out up to 1 million records then stop. For those that do decided to update their applications the news is better.
The new SWC will take into account the changes to the infrastructure, retrieve data from the local store and push it up to the tracking engine. This will mean that while those apps are offline, you are still recording behavioral data, just not seeing it in real-time. When your next release is made (and we’d suggest you force an update within the month) data will start to appear again in the reporting dashboard.
This will be the last major revision to the SWC for the next while. We are turning our attention to the reporting front-end and bringing a heap of new stuff online that will give you tremendous insights not previously possible.
We will announce the SWC update here in the next day or so and be aiming to make the domain switch early the week of the 18th October.
Please bookmark the new reporting domain to access your accounts. This domain is up and running already.
As usual, any feedback or issues should be logged over in GetSatisfaction and we’ll get to them as soon as we are able.
We are busy working on the next iteration of AppAnalytics and have made a decision to restrict entry to the Beta programme again for a variety of reasons. Ensuring continuity of service for existing Beta members is critical to what we want to achieve and as we work through some infrastructural decisions we don’t believe it is fair to threaten that by taking anyone else on board.
Please be assured that this will not affect Beta users that have currently deployed Apps in market. It shouldn’t dissuade anyone from registering either as we will be reviewing registrations on a case-by-case basis and activating new registrations once we are happy that our infrastructure can cope with the loads.
We expect to open the automatic registration up again as we approach the next major revision but until that time please bear with us :)Read More
As we move towards a more stable, scalable product our thoughts turn lightly to money. Specifically, how do we get this thing to pay for itself (that would be a nice start). Or better, actually become a product that has sufficient traction in terms of revenue to allow us to devote more time and resource to it’s growth and future development (we do have some pretty cool ideas we’d like to devote time to rolling out).
Our thoughts so far revolve around some of the common SaaS business models. Freemium, flat rate monthly or charging tiers based on items tracked (effectively similar to impression based charging), a combination of all? And what about price points? What are people prepared to pay on a re-occurring basis for access to the app?
We obviously have some ideas but in in true Web 2.0 style we are open to comments below from any of you.
Thanks in advance :)
Hi all we know this is the second lib release in almost as many days but this one is critical to the continued function of App Analytics. The current build, while stable, is not performing as we’d like. Essentially it is placing unnecessary load on our servers, affecting response times across the application.
So please get the updated SWC and apply it to your apps. It’s as simple as a re-compile and re-release from your end which we know is part of your normal development cycle, so it shouldn’t take too much of your time.
How do I tell which version of the App Analytics swc lib I have?
The easiest way to tell what version you are running is trace out the App Analytics version inside your application. The best way to do this is on the next line below where you start App Analytics put this line of code
and then run the Application in debug mode. You will see the version trace out in your console. If it isn’t the latest version (0.03.4), you need to upgrade.
As always please test your application with the new swc before releasing it. If you have any issues please let us know.Read More