AppAnalytics is one of the brand new features included in RAD Studio XE8.
Enabling AppAnalytics in your application will help you to understand how it's being used by your customers, in what OS versions, crashed sessions, and many other types of valuable information.
To get started you need to sign in the appanalytics server (http://appanalytics.embarcadero.com/) using your EDN account.
Once you're in, you can add your first application. After that, an Application ID will be generated. This is very important, as it is the ID that must be used in the TAppAnalytics component in your application.
Now it's time to add a TAppAnalytics component in the VCL or Multi-Device application. In my case, I've put it in a DataModule, to easily access it from different forms of my application.
And there's no need to do anything else to start gathering usage statics for the application. Here is an example:
This information is available for all registered users.
If you upgrade your registered account to a paid one (contact the sales department here for that), you will get a lot more really useful information.
As I've mentioned before, there's a section for the Crashed Sessions:
In the Flow Forms graphic, it's shown the "connections" between the forms in our application, and what "paths" are being more frequently used by our customers. For example, in the next image, it's possible to see that the Send e-mail form is shown most frequently from the Customers window, so I'd review that the usability of that process is fine, and also check that there are no usability issues when trying to use the functionality from other parts of the application.
With Custom Events you can also fine tune what you need to track. In my case I wanted to know what reports were used most, and which ones were barely used. To do this, I only had to call the TrackEvent method before showing a report, for example:
dm1.AppAnalytics1.TrackEvent('Reports', ReportName);
Looking at the sample results, I can see that the Report01 and Report02 are being used by my customers, but Report03 is rarely used.
And the final tab is the Advanced Data Analysis. I'm including an screenshot to show a preview of the data gathered:
Subscribe to this list via RSS
Blog posts tagged in Metrics
AppAnalytics is one of the brand new features included in RAD Studio XE8.
Enabling AppAnalytics in your application will help you to understand how it's being used by your customers, in what OS versions, crashed sessions, and many other types of valuable information.
To get started you need to sign in the appanalytics server (http://appanalytics.embarcadero.com/) using your EDN account.
Once you're in, you can add your first application. After that, an Application ID will be generated. This is very important, as it is the ID that must be used in the TAppAnalytics component in your application.
Now it's time to add a TAppAnalytics component in the VCL or Multi-Device application. In my case, I've put it in a DataModule, to easily access it from different forms of my application.
And there's no need to do anything else to start gathering usage statics for the application. Here is an example:
This information is available for all registered users.
If you upgrade your registered account to a paid one (contact the sales department here for that), you will get a lot more really useful information.
As I've mentioned before, there's a section for the Crashed Sessions:
In the Flow Forms graphic, it's shown the "connections" between the forms in our application, and what "paths" are being more frequently used by our customers. For example, in the next image, it's possible to see that the Send e-mail form is shown most frequently from the Customers window, so I'd review that the usability of that process is fine, and also check that there are no usability issues when trying to use the functionality from other parts of the application.
With Custom Events you can also fine tune what you need to track. In my case I wanted to know what reports were used most, and which ones were barely used. To do this, I only had to call the TrackEvent method before showing a report, for example:
dm1.AppAnalytics1.TrackEvent('Reports', ReportName);
Looking at the sample results, I can see that the Report01 and Report02 are being used by my customers, but Report03 is rarely used.
And the final tab is the Advanced Data Analysis. I'm including an screenshot to show a preview of the data gathered:
The CodeRage 6 Friday, October 21 (the last day of this year's CodeRage) session replay have been uploaded to CodeCentral. While you are downloading the repays, you'll have plenty of time to check out the Virtual Exhibit Hall and see the special offers from our technology partners. Many of their offers are good for the next several weeks. If you don't already have our XE2 products, you should immediately download the trials and try many of the techniques you learned this week at CodeRage. If ...
We each have a finite amount of time on this planet. I'm sure that you all want to enjoy every moment of every day, I do! Groucho Marx said, "Time flies like an arrow; fruit flies like a banana." John F. Kennedy said, "We must use time as a tool, not as a crutch". The Mick Jagger and Keith Richards of the Rolling Stones wrote the song, "Time Waits for No One." The Rolling Stones also recorded the song "Time Is on My Side".
There are many quotes involving time, the lack of time, wanting more...
- Page :
- 1