Using ContentProvider to develop Android SDKs
At the end of the session an Android Developer should be able to understand when, why and how to use ContentProvider in Android. Finally, the developer should be able to understand how they can use ContentProvider to build an Android SDK for an existing backend.
The session is divided into following parts.
- How ContentProvider works? How is it being used currently in some of the default Android apps?
- When should you choose to use ContentProvider? More importantly, when should you stay away from it?
- How to use ContentProvider using an existing server backend? This part will involve demonstration by writing a basic ContentProvider implementation and a light app communicating with ContentProvider.
- How can you package ContentProvider seperately and provide that to others to build apps on top of it?
A participant should know how to use Cursors in Android. The whole concept of ContentProvider will build on top of that.
I’m currently a Lead Engineer at MobStac and have worked on building the Android SDK for our platform to support Android Apps. The SDK is currently in use in all the apps based on our platform that are currently available on Play Store.