{:external: target="_blank" .external} {:shortdesc: .shortdesc} {:codeblock: .codeblock} {:pre: .pre} {:screen: .screen} {:tsSymptoms: .tsSymptoms} {:tsCauses: .tsCauses} {:tsResolve: .tsResolve} {:tip: .tip} {:important: .important} {:note: .note} {:download: .download} {:java: .ph data-hd-programlang='java'} {:ruby: .ph data-hd-programlang='ruby'} {:c#: .ph data-hd-programlang='c#'} {:objectc: .ph data-hd-programlang='Objective C'} {:python: .ph data-hd-programlang='python'} {:javascript: .ph data-hd-programlang='javascript'} {:php: .ph data-hd-programlang='PHP'} {:swift: .ph data-hd-programlang='swift'} {:reactnative: .ph data-hd-programlang='React Native'} {:csharp: .ph data-hd-programlang='csharp'} {:ios: .ph data-hd-programlang='iOS'} {:android: .ph data-hd-programlang='Android'} {:cordova: .ph data-hd-programlang='Cordova'} {:xml: .ph data-hd-programlang='xml'}

{: #push_step_4}

After your applications are developed, you can send basic push notifications.

To send basic push notifications, complete the following steps:

1. In the {{site.data.keyword.mobilepushshort}} service console, click Notifications on the left navigation menu.

2. Click Create, and compose a message.

   • Compose a new notification by providing the following information: Notification text, Notification title (optional), Additional payload (optional).
   • Select the Target audience by one of the following targets:
     • Platforms - Options are: Android, iOS, Web Notifications, Chrome Apps and Extensions, Chrome Browser, Firefox, Safari, and All Devices.
     • Tags - Enter the Tag, topic name or create a tag.
     • Devices/user IDs - Select either Device ID or User ID and enter the device/user ID detail for the selection.

   When you select the All Devices option, all devices that are subscribed to {{site.data.keyword.mobilepushshort}} will receive notifications. {: note}

   • Optionally for rich media notifications use Advanced settings. Select the Priority (valid options are: Default, Max, Min, Low, High) and select the type of notification to be sent (Default or Silent).
   • Quickly review your selection in the Review section.

3. Click Send.

4. Verify that your devices or browser has received the notification.

The following screen capture shows an alert box handling a push notification in the foreground on an Android device.

The following screen capture shows a push notification in the background for Android.

{: #push_step_4_Android}

You can further customize the {{site.data.keyword.mobilepushshort}} settings for sending notifications to Android devices.

The following optional customization options are supported:

• Priority: Specifies the options for assigning delivery priority to messages.
  • A priority high or max result in heads-up notification.
  • A priority low or default will not open network connections on a sleeping device.
  • A priority min is a silent notification.
• Collapse Key: Collapse keys are attached to notifications. If multiple notifications arrive sequentially with the same collapse key when the device is offline, they are collapsed. When a device comes online, it receives notifications from the FCM server, and displays only the latest notification bearing the same collapse key. If the collapse key is not set, both the new and old messages are stored for the future delivery.
• Sound: Indicates a sound clip to be played on the receipt of a notification. Supports default or the name of a sound resource that is bundled in the app.
• Interactive category: Specify the category for interactive notifications. Ensure that this is the same string you have provided to SDK.
• Icon: Specify the name of the icon to display for the notification. Ensure that you have packaged the icon in the res/drawable folder, with the client application.
• Time to live: This value is set in seconds. If this parameter is not specified, the FCM server stores the message for four weeks and will try to deliver the message. The validity expires after four weeks. The possible value range is 0 - 2,419,200 seconds.
• Visibility: You can choose to set the notification visibility option to either public or private.
  • The private option restricts public viewing and you can choose to enable it if your device is secure with a pin or pattern, and the notification setting is set to Hide sensitive notification content. When the visibility is set as private, a redact field must be mentioned. Only the content that is specified in the redact field shows up on a secure locked screen on the device.
  • The public option would render the notifications to be freely read.
• LED Color: You can set the color to when LED ON and LED OFF.
• Delay when idle: You can set this to either of the following values:
  • True - Instructs the FCM server not to deliver the notification if the device is idle.
  • False - Ensures notification delivery even if the device is idle.
• Sync: By setting this option to true, notifications across all your registered devices are in sync. If the user with a username has multiple devices with the same application installed, reading the notification on one device ensures deletion of notifications in the other devices. You need to ensure that you are registered with {{site.data.keyword.mobilepushshort}} service with userId for this option to work.
• Channel ID: Specify the channel to which the notification to be sent.
• Expandable notification: This provides customers an option to expand a notification with more information, while a basic notification would be visible with the notification collapsed. The following options are supported:
  • Big Picture Notifications: You can choose to include a picture when the notification is expanded. Ensure that you provide a Title text and URL for the picture.
  • Big Text Notifications: You can choose to include more text with a title. Ensure that the Big Text message and Title text information are furnished.
  • Inbox Style Notifications: You can send the notification that is styled as an inbox notification. Provide a Title text and furnish the message in Lines.

{: #push_step_4_ios}

You can customize the {{site.data.keyword.mobilepushshort}} settings for sending notifications to iOS devices. The following optional customization options are supported.

• Badge: Indicates the number that is displayed on the application badge. The default value is zero (0), and this would not display a badge.
• Sound: Indicates a sound clip to be played on the receipt of a notification. Supports default or the name of a sound resource that is bundled in the app.
• Additional payload: Specifies the custom payload values for your notifications.

You can also choose to enable interactive notifications and rich media notifications.

{: #push_step_4_monitor}

The {{site.data.keyword.mobilepushshort}} service provides a monitoring utility to help you check the status of messages that are sent. To configure your monitoring utility, go through monitoring section of either onef the following options:

• Enable monitoring for Android applications.
• Enable monitoring for iOS applications.