Confirming is asking the user to verify that they truly want to proceed with an action they just invoked. In some cases, the confirmation is presented along with a warning or critical information related to the action that they need to consider.
+
Acknowledging is displaying text to let the user know that the action they just invoked has been completed. This removes uncertainty about implicit operations that the system is taking. In some cases, the acknowledgment is presented along with an option to undo the action.
@@ -22,14 +22,14 @@ page.tags=dialog,toast,notification
Confirming
-
-
+
+
Example: Google Play Books
In this example, the user has requested to delete a book from their Google Play library. An alert appears to confirm this action because it's important to understand that the book will no longer be available from any device.
When crafting a confirmation dialog, make the title meaningful by echoing the requested action.
-
+
Example: Android Beam
Confirmations don't necessarily have to be presented in an alert with two buttons. After initiating Android Beam, the user is prompted to touch the content to be shared (in this example, it's a photo). If they decide not to proceed, they simply move their phone away.
@@ -37,15 +37,15 @@ page.tags=dialog,toast,notification
Acknowledging
-
-
+
+
Example: Abandoned Gmail draft saved
In this example, if the user navigates back or up from the Gmail compose screen, something possibly unexpected happens: the current draft is automatically saved. An acknowledgment in the form of a toast makes that apparent. It fades after a few seconds.
Undo isn't appropriate here because saving was initiated by the app, not the user. And it's quick and easy to resume composing the message by navigating to the list of drafts.
-
+
Example: Gmail conversation deleted
After the user deletes a conversation from the list in Gmail, an acknowledgment appears with an undo option. The acknowledgment remains until the user takes an unrelated action, such as scrolling the list.
@@ -53,14 +53,14 @@ page.tags=dialog,toast,notification
No Confirmation or Acknowledgment
-
-
+
+
Example: +1'ing
Confirmation is unnecessary. If the user +1'd by accident, it's not a big deal. They can just touch the button again to undo the action.
Acknowledgment is unnecessary. The user will see the +1 button bounce and turn red. That's a very clear signal.
-
+
Example: Removing an app from the Home Screen
Confirmation is unnecessary. This is a deliberate action: the user must drag and drop an item onto a relatively large and isolated target. Therefore, accidents are highly unlikely. But if the user regrets the decision, it only takes a few seconds to bring it back again.
diff --git a/docs/html/design/patterns/fullscreen.jd b/docs/html/design/patterns/fullscreen.jd
index 624d44c..1c95f21 100644
--- a/docs/html/design/patterns/fullscreen.jd
+++ b/docs/html/design/patterns/fullscreen.jd
@@ -19,13 +19,13 @@ page.tags=full screen,immersive,leanback
back into view.
-
-
+
+
Lean Back
Touch the screen anywhere to bring back system bars.
-
+
Immersive
Swipe from the any edge of the screen with a hidden bar to bring back system bars.
![]({@docRoot}design/media/fullscreen_immersive_swipe_bottom.png)
@@ -69,8 +69,8 @@ page.tags=full screen,immersive,leanback
interrupted by accidental touches and swipes.
-
-
+
+
diff --git a/docs/html/design/patterns/gestures.jd b/docs/html/design/patterns/gestures.jd
index ada0735..b471ee3 100644
--- a/docs/html/design/patterns/gestures.jd
+++ b/docs/html/design/patterns/gestures.jd
@@ -15,9 +15,9 @@ following table shows the core gesture set that is supported in Android.
-
+
-
+
Touch
Triggers the default functionality for a given item.
@@ -28,7 +28,7 @@ following table shows the core gesture set that is supported in Android.
-
+
Long press
Enters data selection mode. Allows you to select one or more items in a view and act upon
@@ -40,7 +40,7 @@ following table shows the core gesture set that is supported in Android.
-
+
Swipe or drag
Scrolls overflowing content, or navigates between views in the same hierarchy. Swipes are
@@ -57,9 +57,9 @@ following table shows the core gesture set that is supported in Android.
-
+
-
+
Long press drag
Rearranges data within a view, or moves data into a container (e.g. folders on Home Screen).
@@ -70,7 +70,7 @@ following table shows the core gesture set that is supported in Android.
-
+
Double touch
Scales up a standard amount around the target with each repeated gesture until reaching
@@ -84,7 +84,7 @@ following table shows the core gesture set that is supported in Android.
-
+
Double touch drag
Scales content by pushing away or pulling closer, centered around gesture.
@@ -106,9 +106,9 @@ following table shows the core gesture set that is supported in Android.
-
+
-
+
Pinch open
Zooms into content.
@@ -119,7 +119,7 @@ following table shows the core gesture set that is supported in Android.
-
+
Pinch close
Zooms out of content.
diff --git a/docs/html/design/patterns/help.jd b/docs/html/design/patterns/help.jd
index 97949e2..6ef155a 100644
--- a/docs/html/design/patterns/help.jd
+++ b/docs/html/design/patterns/help.jd
@@ -21,8 +21,8 @@ page.tags=settings,preferences
To teach high value functionality that's only available through a gesture.
For example, we use help content to teach users how to place apps on their Home screen. This functionality is:
-
-
+
+
However, not all high value gesture-only functionality needs a tutorial. For example, don't teach users how to scroll content. They already know how because it's a fundamental, system-wide interaction.
-