I understand that people can rip it apart and do whatever with it so my main concern is about "official" android releases.
Can someone from Google comment if the support for all built in content providers is a requirement for being able to run Android Market or is this part not regulated? I'm asking because when I'm developing an app that will be published on the Android Market, do I have to design for all cases where a particular built-in content provider (or part of it) is not supported? Tauno On Wed, Oct 21, 2009 at 4:03 PM, Mark Murphy <mmur...@commonsware.com> wrote: > > tauntz wrote: >> In 1.5 and 1.6 the following code snippet works: >> --- >> import android.provider.Contacts; >> import android.provider.Contacts.People; >> >> ContentValues values = new ContentValues(); >> values.put(Contacts.ExtensionsColumns.NAME, "name"); >> values.put(Contacts.ExtensionsColumns.VALUE, "value"); >> Uri personUri = ContentUris.withAppendedId(People.CONTENT_URI, 1); >> Uri personExtensionUri = Uri.withAppendedPath(personUri, >> People.Extensions.CONTENT_DIRECTORY); >> getContentResolver().insert(personExtensionUri, values); >> --- >> >> Can we rely on the fact that the same URIs will be handled by the >> built-in content providers also in future versions/devices or is there >> a possibility that some of them do not support it by throwing a >> UnsupportedOperationException ( Unknown uri: ... )? The documentation >> for content providers says that: "Android ships with a number of >> content providers for common data types (audio, video, images, >> personal contact information, and so on). You can see some of them >> listed in the android.provider package." Does that mean that >> everything that is under android.provider.* has to be supported by all >> future Android versions/devices? > > "Has to" is a strong expression. > > Remember that Android is open source, and therefore device manufacturers > can do what they want. Those having the Android Market on-device are > held to a higher compatibility standard, but there may be holes in the > testing process. > > Many devices will support the standard content providers with the > standard URLs and projections. I'll even go out on a limb and say that > most devices will do that. I'll be fairly surprised if all devices do > that, though. > > -- > Mark Murphy (a Commons Guy) > http://commonsware.com | http://twitter.com/commonsguy > > _The Busy Coder's Guide to *Advanced* Android Development_ > Version 1.1 Available! > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~----------~----~----~----~------~----~------~--~---
