A lot of applications will have the user to choose photos. It would be good to have a Google standard View for selecting images stored on the phone. And that all developers storing images must use a standard way that ensures that the standard image picker view always can be used for accessing all photos in the Android phone regardless of what third- party photo or image applications are used.

Google says: "Since Android is an open cell phone platform, anyone will be able to build their own devices that run the core Android OS. There is no requirement that any given phone include any Google software, or even be associated with Google at all."

From: http://code.google.com/android/toolbox/google-apis.html

That's like Sun Microsystems saying: "You are free to not use the standard Java String class. You can write your own string class and use that instead, and you don't even have to subclass the standard string class, you can write a totally separate and incompatible class." In the case of Android Views and Services we are of course talking about a higher level of abstraction, but the principle is the same: standards are needed for integration to work in practice.

In the 20th century even integration of computer networks was problematic before TCP/IP became a de facto standard. In C++ everyone was writing their own string class. And so on. In the 21th century, the Android platform use many standards, but there is also a need for bringing in standards on a higher level, such as for managing images, if you get the picture.

Likely people at Google are already working a lot on these kinds of problems, but I want to stress the importance of having many of these