Do you have an integration guide to get me started?
A 10-minute Integration Guide for Android, BlackBerry and both the iPhone and iPad are available on the Localytics Wiki. On the wiki, you'll 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 Client libraries are designed to be as unobtrusive as possible. In most cases data collection consists of appending a string to a file which is a quick operation. Data are batched and application developers can choose how often they want these data uploaded. The uploads themselves happen on a separate thread and will not block the application.
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. In this case a single upload happens, sending up all the batched data each time the application is run. However, it is very easy to have the library upload more or less frequently if desired.
What if my user doesn't have a network connection?
Localytics requires a network connection for upload 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?
All 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 for an application which already loads the resources required to connect to the Internet, a typical integration will typically add about 5 kilobytes to the total binary size.
Does Localytics run in the background while my app is running?
No. All data collection happens on the calling thread when the developer calls the 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. Uploads do happen in the background, but only when the developer makes an upload call, and the thread terminates as soon as upload is complete.
What does Apple's Developer Agreement for iPhone 4 mean to my ability to use Localytics?
It's in the best interest of both Apple and app publishers to have the highest quality and most successful apps available on the iPhone and iPad, and that requires app analytics. The industry expects that developers using analytics for those purposes will see their apps approved. Localytics remains focused on serving app developers, brands and publishers. To further protect developers and end-users, Localytics has always released the source code to our SDKs--app developers (and Apple) know exactly what your putting into your apps--and our business model does not rely on advertising, recommendation engines or selling user data to third-parties. Localytics also offers an optional first-party analytics solution as part of our Enterprise service, enabling direct collection of device data.
