102 lines
4.5 KiB
Plaintext
102 lines
4.5 KiB
Plaintext
|
page.title=Notifying the User
|
||
|
|
@jd:body
|
||
|
|
|
||
|
|
<div id="qv-wrapper">
|
||
|
|
<div id="qv">
|
||
|
|
<h2>Topics</h2>
|
||
|
|
<ol>
|
||
|
|
<li><a href="toasts.html">Creating Toast Notifications</a></li>
|
||
|
|
<li><a href="notifications.html">Creating Status Bar Notifications</a></li>
|
||
|
|
<li><a href="{@docRoot}guide/topics/ui/dialogs.html">Creating Dialogs</a></li>
|
||
|
|
</ol>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
|
||
|
|
<p>Several types of situations may arise that require you to notify the user
|
||
|
|
about an event that occurs in your application. Some events require the user to respond
|
||
|
|
and others do not. For example:</p>
|
||
|
|
<ul>
|
||
|
|
<li>When an event such as saving a file is complete, a small message
|
||
|
|
should appear to confirm that the save was successful.</li>
|
||
|
|
<li>If the application is running in the background and needs the user's attention,
|
||
|
|
the application should create a notification that allows the user to respond at
|
||
|
|
his or her convenience.</li>
|
||
|
|
<li>If the application is
|
||
|
|
performing work that the user must wait for (such as loading a file),
|
||
|
|
the application should show a hovering progress wheel or bar.</li>
|
||
|
|
</ul>
|
||
|
|
|
||
|
|
<p>Each of these notification tasks can be achieved using a different technique:</p>
|
||
|
|
<ul>
|
||
|
|
<li>A <a href="#Toast">Toast Notification</a>, for brief messages that come
|
||
|
|
from the background.</li>
|
||
|
|
<li>A <a href="#StatusBar">Status Bar Notification</a>, for persistent reminders
|
||
|
|
that come from the background and request the user's response.</li>
|
||
|
|
<li>A <a href="#Dialog">Dialog Notification</a>, for Activity-related notifications.</li>
|
||
|
|
</ul>
|
||
|
|
|
||
|
|
<p>This document summarizes each of these techniques for notifying the user and includes
|
||
|
|
links to full documentation.</p>
|
||
|
|
|
||
|
|
|
||
|
|
<h2 id="Toast">Toast Notification</h2>
|
||
|
|
|
||
|
|
<img src="{@docRoot}images/toast.png" alt="" style="float:right" />
|
||
|
|
|
||
|
|
<p>A toast notification is a message that pops up on the surface of the window.
|
||
|
|
It only fills the amount of space required for the message and the user's current
|
||
|
|
activity remains visible and interactive. The notification automatically fades in and
|
||
|
|
out, and does not accept interaction events. Because a toast can be created from a background
|
||
|
|
{@link android.app.Service}, it appears even if the application isn't visible.</p>
|
||
|
|
|
||
|
|
<p>A toast is best for short text messages, such as "File saved,"
|
||
|
|
when you're fairly certain the user is paying attention
|
||
|
|
to the screen. A toast can not accept user interaction events; if you'd like
|
||
|
|
the user to respond and take action, consider using a
|
||
|
|
<a href="#StatusBar">Status Bar Notification</a> instead.</p>
|
||
|
|
|
||
|
|
<p>For more information, refer to <a href="toasts.html">Creating Toast Notifications</a>.</p>
|
||
|
|
|
||
|
|
|
||
|
|
<h2 id="StatusBar">Status Bar Notification</h2>
|
||
|
|
|
||
|
|
<img src="{@docRoot}images/notifications_window.png" alt="" style="float:right; clear:right;" />
|
||
|
|
|
||
|
|
<p>A status bar notification adds an icon to the system's status bar
|
||
|
|
(with an optional ticker-text message) and an expanded message in the "Notifications" window.
|
||
|
|
When the user selects the expanded message, Android fires an
|
||
|
|
{@link android.content.Intent} that is defined by the notification (usually to launch an
|
||
|
|
{@link android.app.Activity}).
|
||
|
|
You can also configure the notification to alert the user with a sound, a vibration, and flashing
|
||
|
|
lights on the device.</p>
|
||
|
|
|
||
|
|
<p>This kind of notification is ideal when your application is working in
|
||
|
|
a background {@link android.app.Service} and needs to
|
||
|
|
notify the user about an event. If you need to alert the user about an event that occurs
|
||
|
|
while your Activity is still in focus, consider using a
|
||
|
|
<a href="#Dialog">Dialog Notification</a> instead.</p>
|
||
|
|
|
||
|
|
<p>For more information, refer to
|
||
|
|
<a href="notifications.html">Creating Status Bar Notifications</a>.</p>
|
||
|
|
|
||
|
|
|
||
|
|
<h2 id="Dialog">Dialog Notification</h2>
|
||
|
|
|
||
|
|
<img src="{@docRoot}images/dialog_progress_spinning.png" alt="" style="float:right" />
|
||
|
|
|
||
|
|
<p>A dialog is usually a small window that appears in front of the current Activity.
|
||
|
|
The underlying Activity loses focus and the dialog accepts all user interaction.
|
||
|
|
Dialogs are normally used
|
||
|
|
for notifications and short activities that directly relate to the application in progress.</p>
|
||
|
|
|
||
|
|
<p>You should use a dialog when you need to show a progress bar or a short
|
||
|
|
message that requires confirmation from the user (such as an alert with "OK" and "Cancel" buttons).
|
||
|
|
You can use also use dialogs as integral components
|
||
|
|
in your application's UI and for other purposes besides notifications.
|
||
|
|
For a complete discussion on all the available types of dialogs,
|
||
|
|
including its uses for notifications, refer to
|
||
|
|
<a href="{@docRoot}guide/topics/ui/dialogs.html">Creating Dialogs</a>.</p>
|
||
|
|
|
||
|
|
|
||
|
|
|