Should I use Settings.System when writing our Android SDK for developers?
We are not develping applications. Instead we provide a SDK for
developers. One Service is used to do our job for all apps intergrated our
SDK, thus we have to save some "global settings". I found
android.provider.Settings.System is widely used in our project, which
means we use Settings.System.putString() to save and
Settings.System.getSring() to read. However, there are too few developers
using this. I am wondering if we shouldn't use this class, will Android
forbidden us to use Settings.System in the next version? If is safe?
No comments:
Post a Comment