Android Design 1:back keys and up keys in app navigation

One, the concept

1, back key always exists in Android system

1-1 return under Any page

1-2 Floating Window

1-3 contexual Action Bar/highlight Select

1-4 Keyboard

2, the UP key comes with Android design.

2-1 android Design defined by the parent container

The main interface of the 2-2 app does not exist with the UP key

Second, situational analysis

1, inside the app

1-1 Step Deep Path

Back: According to the order of activity in the stack

Up: According to the order of activity in the stack.

1-2 did not follow a step-by-step path, such as jumping from book to movie

Back: According to the location of the activity in the stack

Up: Return to parent container (back to Movie home page)

2, two app jumps (jump from Play Store to Gmail share)

Back: According to the order of activity in the stack

Stack status : No new stacks will be created and will be added to the store's stack separately from the Gmail share page that jumps to. If Gmail had already had a stack, it wouldn't be affected.

Up: Returns the currently applied parent container

Stack status : A new stack will be created to return to the parent container Activity, if the original Gmail already has a stack, the original stack will be destroyed. Because the system wants to update to the latest state. The store stack will also remain in the background and can be recents screen.

Three, Reference

Http://developer.android.com/design/patterns/navigation.html#between-apps

This article is from the "Little New column" blog, please be sure to keep this source http://mikewang.blog.51cto.com/3826268/1416250