Changes

<td width="20%">[[An Android SQLite Database Tutorial|Previous]]<td align="center">[[Kindle Fire Andrid 4 App Development Essentials|Table of Contents]]<td width="20%" align="right">[[Implementing an Android Content Provider|Next]]</td>

<google>BUY_KINDLE_FIREBUY_ANDROID</google>

The previous chapter worked through the creation of an example application designed to store data using a SQLite database. When implemented in this way, the data is private to the application and, as such, inaccessible to other applications running on the same device. Whilst this may be the desired behavior for many types of application, situations will inevitably arise whereby the data stored on behalf of an application could be of benefit to other applications. A prime example of this is the data stored by the built-in Contacts application on the Kindle Fire an Android device. Whilst the Contacts application is primarily responsible for the management of the user’s address book details, this data is also made accessible to any other applications that might need access to this data. This sharing of data between Android applications is achieved through the implementation of content providers.

<google>BUY_KINDLE_FIREBUY_ANDROID</google>

<td width="20%">[[An Android SQLite Database Tutorial|Previous]]<td align="center">[[Kindle Fire Android 4 App Development Essentials|Table of Contents]]<td width="20%" align="right">[[Implementing an Android Content Provider|Next]]</td>