> Does this mean those APIs, e.g. reading contacts, will be made a > "public" part of the SDK?
Reading contacts is already part of the public APIs. > * No, there is no such list. No, there is no such list and we won't offer one. > Please understand my point of view: I understand that there is a > reason to have private APIs. I just don't understand why this should > be kept secret. They're not private: you can grab the source code and find them in there. But developers are already wrongly using those APIs and producing such a list would only encourage the use of private APIs. It will only cause problems and there is absolutely no good reason to do so. You have a list of public APIs, if something you want to do is not possible with these APIs, then you cannot do it. You are welcome to submit patches (source.android.com) or file feature requests (b.android.com) though. -- Romain Guy Android framework engineer romain...@android.com Note: please don't send private questions to me, as I don't have time to provide private support. All such questions should be posted on public forums, where I and others can see and answer them --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
