Allan Day
aday@gnome.org
Alex Puchades
alex94puchades@gmail.com 2015
Daniel Mustieles
daniel.mustieles@gmail.com 2011 - 2015
Nicolás Satragno
nsatragno@gnome.org 2013
Benjamín Valero Espinosa
benjavalero@gmail.com 2011
Jorge González
jorgegonz@svn.gnome.org 2009
Rosa Elena Pérez
rozydicemiau@gmail.com 2014
Oscar Rafael Arachi
arachi910@gmail.com 2014 - 2015
Miguel Ajuech
miguel.ann.28@gmail.com 2014
Adrián Pérez Domínguez
adrian@aztli.org 2015
Celina Osorio Ochoa
chelinoska@gmail.com 2015
Dario Amigon Espinoza
daramigon@gmail.com 2015
Yenisei Ramírez Pérez
yeniseirape@gmail.com 2015
José Roberto Ramíres Mendoza
aczella@gmail.com 2015
Bernardo Sánchez Romero
b.sanchez.rom@gmail.com 2015
Emmanuel Márquez Juárez
resident3333@gmail.com 2015
David Romero Serrano
lemi136@hotmail.com 2015
Omar Garcia Guzman
garciag.omar91@gmail.com 2015
Edilberto Huerta Niño
edilberto.huerta0290@gmail.com 2015

# Notificaciones

Notifications enable you to inform the users about events when they are not using your application. They also provide the ability for users to quickly respond to those events, using notification actions.

# Cuándo usarlas

Use notifications to inform the user about events they will be interested in while they are not using your application. This can include new messages in messaging applications, the completion of long-running tasks, reminders for calendars, and so on.

Notifications shouldn’t be used as a substitute for feedback that is provided by your application windows, which should be able to inform the user about events without the need for notifications.

# Elementos de la notificación

Las notificaciones en GNOME 3 tienen un número estándar de componentes:

Elemento | Descripción
--- | ---
Icono de la aplicación | Indicates which application sent the notification.
Título | El encabezado de la notificación
Cuerpo | Un bloque de texto opcional que da detalles adicionales acerca de la notificación. El cuerpo de la notificación puede incluir múltiples párrafos. Por ejemplo: un fragmento del inicio de un correo electrónico.
Acción predeterminada | Esta es la acción que se lanza cuando la notificación esta activada.
Acciones | Cada notificación puede incluir hasta tres botones.

## Títulos

El título puede proporcionar un resumen corto y conciso de un evento que lance una notificación. El cuerpo de la notificación puede no siempre ser visible, sin embargo es importante asegurar que la notificación se deba entender desde el título por sí solo.

## Acciones predeterminadas

La acción predeterminada siempre debe descartar la notificación y abrir una ventana perteneciente de la aplicación que envió la notificación. Si la notificación se relaciona con una parte específica de la interfaz de usuario de la aplicación, la acción predeterminada debe mostrar la parte de la IU. La acción predeterminada para una notificación acerca de un nuevo correo electrónico debe mostrar la importancia del mensaje del correo electrónico cuando se activa, por ejemplo.

## Acciones de la notificación

You can provide useful functionality by embedding buttons in notifications. This allows users to quickly and easily respond to the notification.

Notification actions should be related to the content of the notification, and should not provide generic actions for your application. This ensures that each notification has a clear focus and purpose.

Only use notification actions when the functionality that they provide is commonly required.

Actions should not replace user interface controls elsewhere - it should be possible to take the same actions from your application’s windows.

It is not necessary to always use notification actions, and many notifications will not require them.

Notification actions should not duplicate the default action. For example, a new email notification does not need to include an Open button, since the default action should already perform this action.

# Guía general

It is important not to needlessly distract users with notifications. This can easily become annoying and frustrating, and will not incline users to like your application. Therefore, always be critical when using notifications, and question whether users really need to be informed about the events you want to communicate.

Applications that deal with lots of events, such as email or social media messages, run a particular risk of distracting users with too many notifications. These applications should place restrictions on how frequently they send notification messages. Instead of showing a notification for each new message, it is a good idea for each notification to provide a summary of new messages.

Notifications in GNOME 3 persist after they have been initially displayed. It is therefore important to remove notification messages that are no longer relevant to the user.

Your application window should provide feedback on all the events that have been communicated by notifications. As a result, when your application window is focused, notification messages should be treated as having been read, and should be removed.

Ensure that your application removes notifications that are no longer valid. For example, a notification for a weather warning that has been revoked should be removed.