Thank you for your answers so far, but I still think you're getting me
wrong.
I'm not planing to use private APIs - at least not as long as they
remain private. I'm trying to create high quality software and I know
that hacking won't get me there.
But it would be nice if Google (or the Open
Hi,
MosthiddenAPIs are used by the framework itself and not by
applications. Some applications do usehiddenAPIs but we definitely
want to fix them to compile with the SDK.
Does this mean those APIs, e.g. reading contacts, will be made a
public part of the SDK?
But I'm afraid there may be
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
On Android, All apps are created equal but some are equal than
others... You can replicate most of the functionality of the built in
apps by using internal classes, that do not ship as part of the SDK.
The only exception I've found is that some classes require you to have
the same process id
Don't use private APIs. Seriously. Your app will break at some point when
your users get a new version of the OS.
In the vast majority of the cases where the built-in apps are using a
private API, there is in fact a public API they can use to do the same
thing. In the few cases where there
5 matches
Mail list logo