There is standard use of SmsMessage to send messages. http://developer.android.com/reference/android/telephony/SmsManager.html
However, I think the Content Provider solution is more stable than the Concrete Class, because the Content Provider is an abstract layer for accessing data in the case of multiple applications. In the long run, everything can be changed. For this, it will be beneficial for developers to use a design template, a wrapper class to manage the content provider (Facade), or use a data access template, etc.
In the Android configuration file, we can limit the sdk level to prevent something lost:
<uses-sdk android:minSdkVersion="5" android:maxSdkVersion="8" android:targetSdkVersion="7" />
I am new to Android development, even if I read a lot of documents or books, I know that there is black magic in the source code. Changing the record too quickly to write the complete document (its relevance is not possible), so do not worry about changing AUTHORITY or Class.
my 2 cents
source share