In previous posts I wrote on how to add Azure Mobile Engagement features in Windows 8 and Windows 10 applications. AME is a fairly comprehensive suite that provides different capabilities to know the behavior of users when they use our apps.
When we access the Dashboard we can see some interesting metrics like
- Number of active users in an app in a period of time
- Location of the users when using an app
- Type of connection, Wireless, LAN, 3G, etc.
- Average time of interaction in a view in an app by user
These “metrics of use” are achieved, initializing the agent of Engagement when you start the app and then changing the inheritance to use EngagementPage instead of Page. Another option is to respect the types based on our apps and the Load() on each page, make a call using the SDK as I mentioned in the previous post.
Within the SDK, we also have the possibility of recording times for specific activities as when we got a file on the cloud, we process a photo with the Oxford project, launched a process in batch, etc. For this type of scenario, we can work with JOBS. The best way to understand how a Job is to see an example in an app and monitor in real time is recorded when the start and end of it.
The code to start and finish a Job is quite simple. In the active instance of agent, we only have to invoke operations StartJob () and EndJob().
The only important data to take into account is that the ID of each job must be unique. If a Job does not mark it as completed, when the user’s session to close the App, to be finalized by the same.
From here, you just have to start using the information that is recorded in AME. As an example, in the following chart we can see the average time of the Jobs registered in a test app for the last 30 days. The times in which groups are
-10 to 30 seconds
We also have another view in grid mode, or even export to Excel
In next post I will continue giving some love to Azure Mobile Engagement.
Saludos @ Barcelona