Frequently Asked Questions
How do I get started?
10-minute Integration Guides for Android, BlackBerry, iPhone/iPad and Windows are available on the integration page. Here you will also find binaries and source code for the client libraries and the appropriate licenses.
What impact does Localytics have on my application performance?
The Localytics libraries are designed to be as unobtrusive as possible. In most cases data collection consists of a low priority thread appending a string to a database which is a quick operation. Data are batched and application developers can choose how often they want these uploads to happen. The uploads themselves occur on a separate low priority thread and will not block the application.
What if my user doesn’t have a network connection?
Localytics requires a network connection for uploading to data collection servers. If users do not have network service when running an application then all data are stored in a queue for uploading later. If the queue fills, Localytics stops collecting data until the queue is cleared.
How much memory does Localytics consume?
Localytics data are written to persistent storage immediately after they’re recorded. This way, collected data does not need to remain in RAM which allows Localytics to have a very minimal footprint. On disk, the storage is determined by how many events are tagged. Most sessions fall below 2 kilobytes in size.
How much larger does Localytics make an application?
The actual value varies depending on platform and specific circumstances, but all of the Localytics client libraries only use resources such as databases and network connectivity which are used by the operating system and already available to all applications.
Does Localytics collect data in the background while my app is running?
No. All data collection happens when the developer calls Localytics APIs. This makes it much easier to test the integration and guarantees that Localytics will never impact your application by collecting data at an inopportune time.
How often does the library send data to the server?
As a developer, you choose when the library uploads data. The recommendation on most platforms is to upload data once at the start of the application, and again when the application exits. Events between uploads are stored in a queue on the device. It is very easy to have the library upload more or less frequently, matching the needs of your application.
Is it possible to delete or reset analytics data?
Once data are received and processed, they can’t be selectively deleted. Partly for this reason, we recommend creating two app id’s, one for development and one for production. This will keep your development and testing data separate.
Is it possible to grant administrative or viewing privileges to other users?
Yes, through the My Applications tab it is possible to modify app permissions and invite others to join, or extend access to existing account holders.
Can I combine my Android/BlackBerry/iOS/Windows Phone apps with the same key?
While technically possible, we highly recommend that you separate your apps for each platform with separate keys. This makes testing, development and analyzing the data on a per platform basis more organized and less cumbersome.