In this page we'll dive deeper into several aspects of our Android library that can be customized to match your needs.

Setting keys in code

Instead of relying on the applicationKey and applicationSecret in, it is possible to set these in code.


These methods should be called before calling Notificare.shared().launch() to make sure the correct keys are used. If you set keys programmatically and have a google-services.json (mandatory) you can safely delete the

Notification LED Settings

You can send along the preferred color and blinking time of the notification light (only works on selected device models) per notification form the Notificare REST API or the Dashboard. However, you can also set a default color for your app. If neither are set, it defaults to white colored blinking for 500 ms on and 1500 ms off.


Allow JavaScript in HTML and Web Page notifications

By default the Notificare SDK does not allow JavaScript in WebViews (HTML or URL type) as a basic security measure. If you are sure you can trust the source of the URLs you push to users, you might want to enable.


Notifications UI

Changing user interface in the Android is intrinsically decided by your app's styles. Basically Notificare will just use the styles you provide in your app, for the several elements used throughout our UI. We recommend these changes are done in your /res/values folders like shown below:

android styles

Action Labels

Labels used for Action Buttons in both the Notification Manager as well as Notification Dialogs can be localized by adding them as strings resources, where the name is equal to the label. To protect collision of resource names, they can be prefixed with a string. The prefix must then be set by calling Notificare.shared().setLocalizedActionLabelPrefix().

Settings Activity

To be able to add tags to the Settings activity you can start by creating a new folder called xml (if you don't have one) under the folder res. Then add a xml file (eg.: preferences.xml) under xml with the following content:

<?xml version="1.0" encoding="utf-8"?>
<PreferenceScreen xmlns:android="">
      android:defaultValue="false" />
      android:defaultValue="true" />

To keep resources organized, all the strings for the setting should reside under res/values/strings_preferences.xml. Inside that strings file add the keys used in the Settings view:

    <string name="pref_tags_title">Notifications</string>
    <string name="pref_summary_tag_news">Receive the latest news</string>
    <string name="pref_title_tag_news">News</string>
    <string name="pref_summary_tag_updates">Receive information on updates</string>
    <string name="pref_title_tag_updates">Updates</string>

By default, the activity contains a setting for location updates. The header, summary and title can be changed and localized too by adding the following strings to your resource file

<string name="pref_location_services_title">Location Services</string>
<string name="pref_summary_location_updates">Keep track of your location to receive only relevant information</string>
<string name="pref_title_location_updates">Location updates</string>

Customizing the IntentReceiver

If you've followed our recommendations, you've implemented your own Intent Receiver. This will offer you the possibility to customize how you handle notifications.

Handling the Extra property

There are use cases where you'll want to add extra sets of data to your notification. This is allowed via the dashboard and API and in order to handle that data you'll need to override the onNotificationReceived method:

public class MyIntentReceiver extends DefaultIntentReceiver {

//more code ...

public void onNotificationReceived(String alert, String notificationId, String inboxItemId, Bundle extras) {
  //Log.d(TAG, " received with extra Notification" + extras.getString("mykey"));
  super.onNotificationReceived(alert, notificationId, inboxItemId, extras);

This will give you the opportunity to intercept the incoming notification and retrieve the data you've included in your notification. Please note the you should call the super.onNotificationReceived method, that will make sure that Notificare library will still handle the notification for you.

If you do not call super.onNotificationReceived, which we do not recommend, then there are a few things you might want to take in consideration.

Events Logging

In order for all metrics to be collected correctly, please make sure you add the following:

public void onNotificationOpened(String alert, String notificationId, Bundle extras) {

//more code ...
    if (inboxItemId != null) {
  //more code ...

Handling Actions

Actions from the notification drawer come in as an intent extra. You can have them handled by the Notificare library in the background.

NotificareAction action = extras.getParcelable(Notificare.INTENT_EXTRA_ACTION);
NotificareNotification notification = extras.getParcelable(Notificare.INTENT_EXTRA_NOTIFICATION);
if (action != null && notification != null) {
  try {
    Class<?> actionClass = Class.forName(action.getType());
    Constructor<?> ctor = actionClass.getConstructor(Activity.class, NotificareNotification.class, NotificareAction.class);
    NotificationAction actionHandler = (NotificationAction) ctor.newInstance(null, notification, action);
    actionHandler.handleAction(new NotificareCallback<NotificarePendingResult>() {
      public void onSuccess(NotificarePendingResult result) {
        Log.d(TAG, "action handle successfully");

      public void onError(NotificareError error) {
        Log.e(TAG, "error handling action", error);
  } catch (Exception e) {
    Log.e(TAG, "error instantiating Action Handler", e);
} else {

  // Display UI

Launching an Activity

Most likely if you are going to handle the notification yourself, you will want to launch an activity in your app. As an example, this is what the DefaultIntentReceiver does:

if (action != null && notification != null) {
// Handle actions
} else {
    // Close the notification drawer
    Notificare.shared().getApplicationContext().sendBroadcast(new Intent(Intent.ACTION_CLOSE_SYSTEM_DIALOGS));
    Intent notificationIntent = new Intent()
    .putExtra(Notificare.INTENT_EXTRA_DISPLAY_MESSAGE, Notificare.shared().getDisplayMessage())

    if (notificationIntent.resolveActivity(Notificare.shared().getApplicationContext().getPackageManager()) != null) {
      // Notification handled by custom activity in package
    } else {
      // Start a task stack with NotificationActivity on top
      notificationIntent.setClass(Notificare.shared().getApplicationContext(), Notificare.shared().getNotificationActivity());
      TaskStackBuilder stackBuilder = TaskStackBuilder.create(Notificare.shared().getApplicationContext());
      buildTaskStack(stackBuilder, notificationIntent, notification);

Cancel Notifications

One other thing you have to take in account when handling the notifications yourself is to make sure you clear notifications from the notification drawer whenever you read them. In your custom IntentReceiver, after presenting the notification, you can add the following:

public void onNotificationOpened(String alert, String notificationId, String inboxItemId, Bundle extras) {

//more code ...
    if (Notificare.shared().getAutoCancel()) {
  //more code ...

## Application Lifecycle

By default we will register both Open and Close events if your application's activities extend **ActionBarBaseActivity**. But in case this is not possible, you will have to handle it manually. This can be done using the following code:

public class YourActivity {

    //more code...
    protected void onResume() {

    protected void onPause() {

    //more code...


If you use ProGuard, rules for classes to keep are included with the AAR, so there is no need to manually add any rules for Notificare.

65k method limit exceeded

Notificare Android library is tested to work with MultiDex, both natively (Android 5 and above) as well as with the MultiDex support library.

Add the following to your app's build.gradle

defaultConfig {
    multiDexEnabled true

dependencies {
    compile ''

Then, override the attachBaseContext method in the Application class for your app.

protected void attachBaseContext(Context base) {

For more information on MultiDex and possible issues and workarounds, see Android Developer Documentation