Android equivalent of top level menu

Desktop apps have top level menus (File, Edit, Search, ..., Help).

Web apps have very similar thing, menu tabs (Logo, Questions, Tags, Users, Badges, ...).

However I cannot find equivalent of top level menu in Android framework. Assume that my app has 5 main activities. According to menu design guidelines options menu should contain actions related to current activity. So how an app should allow users to easily switch to one of five main activities.

It seems that different apps solve the problem in different ways. Some have a tab list at the top of the screen, some at the bottom. Even Google applications aren't consisted in that field. Google Listen has an options menu item called 'Listen Home', however Listen main activity has no that options menu item. Others have two icons in app luncher which start two different activities from one app.

I realize that due to small phone screens Android apps have to be designed in a slightly different way than web or desktop apps. But I have a feeling that the app top level menu topic was omitted in Android framework. And developers are on their own here. Or am I missing something?

Update: this is Google blueprint for a great app

Update2: this an example app of these patterns

Update3: GreenDroid library helps a lot implementing these patters in your apps. It seems that开发者_如何学C dashboard and action bar patterns are becoming quite popular.

You should take a look at this Google I/O session: http://www.google.com/events/io/2010/sessions/android-ui-design-patterns.html

They talk about the design patterns they used for the Twitter application and basically the type of concept you are asking about. Basically, your activity should have a top bar that gives the user specific tasks to do in the view or allows them to switch into another activity.

Google has not implemented anything like this into the actual SDK yet so you're sort of on your own in terms of implementing it but the main concept is given in the presentation. This is the direction that Google would like to see Android shift into though.

Hopefully this helps you out somewhat.

The file/edit menus of desktop apps have a very different purpose than the questions/tags etc. tabs at the top of this webpage.

The contents of the file/edit menu should be implemented as in the options menu that appears when you press the menu button. This is, as you noted, to save space on the smaller screens.

App navigation like the questions/tags etc could be implemented using a Tab Layout. You are right that apps vary in whether or not the tabs are on the top or bottom, but I don't think thats a huge deal. In my unscientific look through apps on my phone, the bottom seems to be more common. However, I think it might depend on your specific implementation which you decide.

A lot of apps don't require any sort of navigation like that, and can get away with just having a path forward or back via the back button. I think this is preferable for a lot of applications, but won't work in all cases.

I'm not sure what more you would want built into the framework.. It seems like you can accomplish any kind of navigation desired with the above options.

You can look at the source of the Google IO app

ioshed