Also remember to address globalization issues such as the timestamp of each

Also remember to address globalization issues such as

This preview shows page 160 - 163 out of 256 pages.

Also remember to address globalization issues such as the timestamp of each element. Does the app detect the time of an event according to the device's location, the device's settings or does it use a global time like UTC time 9 ? Some of the Mobile Analytics solutions will automatically record and report data elements to the server. It is worth checking what these elements are, how and when they are reported, and how they are formatted. Then you can decide whether you want to use and rely on these automatically- reported elements. Custom event tags augment predefined events, and many mobile analytics solutions provide ways for your app to gener- ate them. You may need to format the custom event messages. If so, pay attention to encoding of the elements and separa- tors; for instance they may need to be URL encoded 10 when they are sent as REST messages 11 . You may want to consider how often the app should report events to reduce the risk of flooding the available capacity of the analytics system, which might affect the reliability and accuracy of the delivered analytics data. One method to reduce the volumes of data processed by the analytics solutions is 9 en.wikipedia.org/wiki/Coordinated_Universal_Time 10 en.wikipedia.org/wiki/Percent-encoding 11 msdn.microsoft.com/en-us/library/live/hh243648
Image of page 160
Mobile Analytics 154 called sampling. Adam Cassar published an interesting blog post on this topic at periscopix.co.uk/blog/should-you-be- worried-about-sampling/. Adjusting Your Code You may need to declare additional capabilities required in order for the mobile analytics to function correctly when integrated with your app. For Android these are known as permissions. The analytics probably need Internet permissions so the events can be reported online, and location-centric permissions if the solution records the location of the phone. If your app already uses the permissions, you do not need to specify their use again. For iOS, UIRequiredDeviceCapabilities tells iTunes and the App Store what device-related features the app needs. It is implemented as a dictionary where the elements are speci- fied using keys. Keys include wifi, location-services and gps. For Windows Phone, capabilities are used to decide what the app uses. Localytics has a quickstart guide online 12 that in- cludes an example of setting the ID_CAP_IDENTITY_DEVICE capability. Handling the results There is a lag from when an app sends an analytics event to when the information is processed and made available to you. The lag, or latency, varies from near 'real-time' to many hours. You, and your business sponsors, need to decide how long you can afford to lag real-time events. Some analytics solutions provide an API to allow you to access the data. This may give you more greater scope to create 12 localytics.com/docs/windows-phone-7-integration/
Image of page 161
Mobile Analytics 155 custom reports. Several allow you to host the servers which provides you greater control of the data and how it is used.
Image of page 162
Image of page 163

  • Left Quote Icon

    Student Picture

  • Left Quote Icon

    Student Picture

  • Left Quote Icon

    Student Picture