What are the principles for creating Android URIs?

Is there any documentation on how to use URIs on the Android platform? For example, I have an application that allows a user to read certain forums. It has several actions - one for viewing the list of forums, one for viewing the list of topics, one for viewing the list of posts, etc.

I would like to use a hierarchical URI in my actions to indicate what should be displayed in the action. Is that a good idea? If so, what is the best way to formulate these URIs?

For example, should I use my own schema like myforums: or content: :?

+4
source share
1 answer

Use standard http URIs to view public web content and configure your host / path based intent filter. Some illustrations of this include the Android Market, which will open links to applications on http://market.android.com , while the site itself opens in any browser. The YouTube app will also open direct links to the video.

Using the http URI means that general links to this content can be opened from any browser on any platform if your application is missing, but the application can take over when it is there to provide a richer or more optimized experience.

+3
source

All Articles