Jonathan Lloyd

Pusher’s **Beams SDKs and API** make it easy to send push notifications to all of your iOS and Android users with one request.

The service manages manages your app credentials and the lifecycle of device tokens which are required for every request to Google’s Firebase Cloud Messaging (FCM) service and APNs for your iOS devices. 

You can subscribe your app user’s registered device to [Interests](https://pusher.com/docs/beams/concepts/device-interests), which act like persistent Pub/Sub topics, so that you can update many devices with the same request. Create as many interests as you need, and send unlimited push notifications. 

**Today we will walk you through the steps to start sending push notifications to your Android app users with Pusher’s Beams SDKs and API.**

## Step 1 - Sign up for a Pusher account

Before we can start building you will have to sign up for a Pusher [account](https://dash.pusher.com/authenticate/register?ref=pn-tutorial-android) (or log in with your existing Pusher credentials).

## Step 2 - Set up your free Beams instance

Head on over to the [dashboard](https://dash.pusher.com/?createInstance=push-notifications&name=Push%20Notifications) and create your first Beams instance. With a free plan, you can send unlimited push notifications to up to 2000 devices during a billing month.

This will take you to our Quickstart wizard:

![push-notifications-android-choose-platform](//images.ctfassets.net/1es3ne0caaid/3ObqgfqqHHSEUt5EjAhM9V/bcdddad0ff84f0be490d85a728b31356/Screenshot_2020-03-06_at_16.18.13.png)

The Quickstart will guide you through the following steps:

### Configuring FCM

The first step of the Quickstart involves configuring your credentials with FCM. 

All push notifications requests for Android devices go through Firebase Cloud Messaging (FCM), Google’s service which delivers them to the device. 

Pusher’s SDKs and API are abstracted above FCM as well as Apple’s APNs service so that you can deliver push notifications to both platforms with one request. Pusher manages the Server Key and Device Token for each request.

[This page](https://pusher.com/docs/beams/getting-started/android/configure-fcm) guides you through the process of getting an FCM Server Key.

### Uploading your FCM Server Key
After you have configured FCM the next step is to upload your FCM Server Key through the Quickstart wizard:

![push-notifications-android-fcm-key](//images.ctfassets.net/1es3ne0caaid/584Fkmw8iJWuHTlIeT15yY/fe2616af05a6fed0f93fb7c965df1381/Screenshot_2020-03-06_at_16.20.16.png)

## Step 3 - Integrating the Beams SDK into your Android project

Now you will integrate the Beams SDK into your Android project. This will send the Device Token to Pusher’s Beams service, which manages its lifecycle if it changes or if the user uninstalls the app. 

You will start by adding the necessary dependencies to your project build.gradle:

``` kotlin
    buildscript {
        ...
        
        dependencies {
           classpath 'com.google.gms:google-services:4.0.1'
        }
    }
```

And your app build.gradle:

``` kotlin
    dependencies {
        ...
    
        implementation 'com.google.firebase:firebase-core:16.0.1'
        implementation 'com.google.firebase:firebase-messaging:17.1.0'
        implementation 'com.pusher:push-notifications-android:1.4.0'
    }
    
    // Add this line to the end of the file
    apply plugin: 'com.google.gms.google-services'
```

You can now register the Device Token with the Beams service. All you have to do is import the SDK:

```
    import com.pusher.pushnotifications.PushNotifications;
```

Then register the Device Token at the appropriate point in your application lifecycle and subscribe your device to an interest `hello`:

``` kotlin
    @Override
    protected void onCreate(Bundle savedInstanceState) {
        super.onCreate(savedInstanceState);
        setContentView(R.layout.activity_main);
        PushNotifications.start(getApplicationContext(), "YOUR_INSTANCE_ID");
        PushNotifications.addDeviceInterest("hello");
    }
```

When your server publishes a push notification to the interest *hello*, it will get passed to your app.

You can find more information on this step [here](https://docs.pusher.com/push-notifications/android/sdk-integration).

## Step 4 - Start sending notifications

Push notifications are triggered by your servers to your Beams service. After a device using your Android application subscribes to an interest on our service, your server can then send a push notification to that device by publishing to that interest.

In this example we’ll use Node.js. Firstly, let’s install the dependency:

``` javascript
    $ npm install pusher-push-notifications-node --save
```

In our JavaScript file, all we need to do is create a Beams instance with our app credentials shown on [our dashboard](https://dash.pusher.com). Then we simply call `publish` with an array of interests and a payload. Every device subscribed to the interests specified in the array will receive a push notification.

To send via FCM, the payload key will be `fcm`:

``` javascript
    const PushNotifications = require('pusher-push-notifications-node');
    
    let pushNotifications = new PushNotifications({
      instanceId: 'YOUR_INSTANCE_ID_HERE',
      secretKey: 'YOUR_SECRET_KEY_HERE'
    });
    
    pushNotifications.publish(
      ['hello'],
      {
        fcm: {
          notification: {
            title: 'Hello World',
            body: 'Hello!'
          }
        }
      }
    }).then((publishResponse) => {
      console.log('Just published:', publishResponse.publishId]);
    }).catch((error) => {
      console.log('Error:', error);
    });
```

If you run your mobile app and put it into background mode, then run this script – you should see your notification. Neat, huh?

**Didn’t see the push notification?** We recommend that you minimise your app by pressing the home button so that you see the push notification when it arrives.

You can send push notifications from your server by using one of our server SDKs. We currently support [many languages](https://pusher.com/docs/beams/reference/all-libraries) including PHP, Python, Node.js and Java.

We will walk you through the steps to send push notifications to your Android app users with Pusher’s Beams API.


Discover how to send push notifications for your Android device using FCM and our Push Notifications API to send both iOS and Android users with one request.

Send Push Notifications to your Android app

Beams

Lanre Adelowo

Webhooks make it extremely easy to send push notifications to all of your iOS and Android users with a single request. In this tutorial, learn about webhooks and how you can take advantage of them to send a notification to Slack every time a user reads or opens the sent notification. 

Notify Slack users of push notification status with webhooks

Wern Ancheta

In this tutorial, create a web app for monitoring the status of your servers in realtime using Laravel.  The app will offer realtime monitoring of disk, CPU and memory. You can also add custom notifications and have the server send you a text message when the CPU usage goes above a set threshold.

Creating a server health monitoring app with Laravel

Channels

Christopher Batin

## Introduction

Pusher Beams allows you to customize push notifications you send to your devices via a server. However it can be expensive to run a server 24 hours a day 7 days a week and we may only need to send notifications every so often. This is where [Microsoft Azure Functions](https://azure.microsoft.com/en-gb/services/functions/) can help. Azure Functions are serverless and work on a pay as you go model (with a generous free tier). This means that you only pay for when you use the function. We’re going to explore how we can setup Pusher Beams on an Android client using an Azure Function running Java to trigger the notifications.


## Prerequisites


- A free Microsoft Azure account. You can create one [here](https://azure.microsoft.com/en-gb/free/).
- A free Pusher account. You can create one [here](https://dash.pusher.com/authenticate).
- Maven installed on your machine. Instructions [here](https://maven.apache.org/install.html).
- A free Google Firebase account. You can create one [here](https://firebase.google.com).
- Postman or another HTTP client installed on your machine. You can download Postman from [here](https://www.getpostman.com).
- Android Studio 3.3.2+
- An understanding of Android development and Android Studio environment.


## Create your Android application

We will need to have a user that has registered for notifications and signed up for an interest we will call “hello”, so we can test out our implementation. We’re going to create a very basic Android app that doesn’t actually show anything to the user except for the notification on the lock screen.

Create a new **Empty Activity** project using Android Studio and name it something like AzurePusher. Provide a **Package name** and remember this as you will need it for completing the Firebase set up. We will be using **Kotlin** as the language choice for this tutorial and supporting Android 16+ (Jelly Bean). 

### Firebase set up

Log in to your Firebase account [here](https://firebase.google.com) and go to your console. If you do not already have a project created you will need to create one and name it anything you like, if you have a project select it. Within the **Project Overview** page select **Add App** and follow the instruction for creating a new Android application. 

Once you have completed the setup for your Android app you will be returned to the dashboard. You will need to go to the project settings (found within the “settings cog” in the top left). Once in the project settings select the **Cloud Messaging** tab. Copy the **Server Key** you will need it for setting up your Pusher Beams instance.

![azure-java-android-notifications-img1](//images.ctfassets.net/1es3ne0caaid/4M0VL46QppgHg8oYf7Cwuw/f661c1fd4768eab49983131482daac06/azure-java-android-notifications-img1.png)

### Creating a Pusher Beams instance
Login or create an account to access your dashboard [here](https://dash.pusher.com). Create a new beams instance using the dashboard.

![zure-java-android-notifications-img2](//images.ctfassets.net/1es3ne0caaid/1BmsX4wk9Z37hMEEyris3O/029e824e0ada5ae5e95bafc8c048ec69/zure-java-android-notifications-img2.png)

Complete step one of the Android setup guide, by providing your FCM server key you copied earlier and **Continue**. We will pick up the remainder later on in this tutorial. Press the **X** to exit the setup guide and you will be returned to your dashboard for that instance. Scroll to the bottom of the page and you will find your Pusher Beams instance ID and secret key, make note of these you will need them later.

### Adding the SDKs
Open your app level `build.gradle` file and add the following into your dependencies:

```
    // app/build.gradle
    ...
    dependencies {
     ...
     implementation 'com.google.firebase:firebase-messaging:17.1.0'
     implementation 'com.pusher:push-notifications-android:1.4.0'
     ...
    }
    ...
```

Here we are adding the Firebase messaging SDK and the Pusher Beams SDK. You should already have the Google Service SDK and `google-services.json` added to your project when setting up the Firebase app.

Synchronize Gradle by pressing the **Sync Now** button.

### Initialize Beams

Open your main activity and add the following import:

```kotlin
    // App/java/{your.package.name}/Main.activity
    import com.pusher.pushnotifications.PushNotifications
```

Add the following to your `onCreate` function:

```kotlin
    // App/java/{your.package.name}/Main.activity
    PushNotifications.start(applicationContext, "YOUR_INSTANCE_ID")
    PushNotifications.addDeviceInterest("hello")
```

Remember to replace `YOUR_INSTANCE_ID` with the instance id from your Pusher Beams console and run your application.

## Create your Azure function

### Creating a Pusher Beams instance
Log in or create an account to access your dashboard [here](https://dash.pusher.com). Create a new Pusher Beams instance using the dashboard.

![zure-java-android-notifications-img3](//images.ctfassets.net/1es3ne0caaid/4v90uIaC4j1eluWEWlPHf2/9392c9a352aed318a003caedef49ba41/zure-java-android-notifications-img3.png)

Complete step one of the Android setup guide, by providing your FCM server key you copied earlier and **Continue**. We will pick up the remainder later on in this tutorial. Press the **X** to exit the setup guide and you will be returned to your dashboard for that instance. Scroll to the bottom of the page and you will find your Beams instance ID and secret key, make note of these you will need them later.

### Creating our function
Log in to your Microsoft Azure portal [here](http://portal.azure.com). Using the search facility (found at the top of the page) search for “Function App”. 


> **Note:** When searching make sure to sure for “Function App” and not “Function Apps”

Once you are on the function app page click **Add** to begin the process of adding a new Azure Function. You will need to give your app a name, this must be unique and you cannot use full stops. Try reverse domain naming like this: `com-example-appname`. I have used `PusherBeams-Java-``Android`. As long as the radio buttons are set to **Create new**, entering a name should also auto complete the resource group and storage. If it hasn’t you should complete these fields as well. 

Select your **Subscription** and **Hosting Plan.** If you’re unsure what these should be leave them as the default values. 
We will also be using **Windows OS** for this tutorial and our location will be set to **Central US**. However feel free to alter the location if the **Java** run time is available there as well. Make sure your **Runtime Stack** is set to **Java** and click **Create**.

![zure-java-android-notifications-img4](//images.ctfassets.net/1es3ne0caaid/78NNiMqRzxJk3P9w9uwacR/4580551e2428aaa4a4f4b5f7194ce55b/zure-java-android-notifications-img4.png)

Once your resource has been created you should receive a notification on the navigation bar. If you don’t see this, wait a couple of minutes and refresh the page. Your resource should appear in a list of Function Apps. Select your resource. 

Now you have created a Function App you need to create a Function. On the overview page select the button **New Function**  or from the side bar click on the **+** the is next to the **Functions** drop down. You will be given a selection of ways to build your function, select the **Visual Code** option and click **Continue**. On the next page select the **Direct Publish** option and click **Continue**. Follow the instructions on the next page for installing and setting up for Visual Code, the Azure command line tools and the Azure Functions extension for Visual Studio Code. Make sure you have signed in to your Azure account in Visual Studio Code before continuing.

![zure-java-android-notifications-img5](//images.ctfassets.net/1es3ne0caaid/pnMQSysIdYIFJnzqaKG3P/b8536579deba23810505de3b02452fa5/zure-java-android-notifications-img5.png)

With Visual Code Studio open open the command palette (**View → Command Palette**). Select **Create New Project**. When prompted provide an empty directory for your project and select the language to be **Java**. Provide a group ID using a reverse domain name naming method. Complete the remaining steps as appropriate (you can just accept the default values).

Azure functions make it easy to invoke your code by hitting an HTTP endpoint. This is great for push notifications, as you can hit this endpoint using our HTTP rest client and passing in our message. You will see more of this later when you test your integration. For now all you need to know is that the default implementation will set this up for you.


> **Note:** There are lots of other templates available for invoking your function and you may wish to explore these as well. You can always invoke your function from the portal if you wish to.

 
Once your project is setup you can deploy it straight from Visual Code, right click on the newly created **src** folder and select **Deploy to Function App**. Select the function app you created earlier for example Pusher-Beams-Java-Android. This will complete the deployment process for you, you can confirm the success by checking the terminal output in Visual Code Studio and by refreshing your Azure Portal. 

![zure-java-android-notifications-img6](//images.ctfassets.net/1es3ne0caaid/6bEGGPpvVja9YVahAenTZS/51b3b6d5c45b9166d3f1ebe0dc448c08/zure-java-android-notifications-img6.png)

### Writing our function

The first thing we need to do in our function is install our dependencies. Open your `pom.xml` file and add the following to your dependencies (make sure it’s `<dependencies>`  and not `<dependencyManagement>`):

```xml
    // pom.xml
    <dependencies>
      // ....
      <dependency>
        <groupId>com.pusher</groupId>
        <artifactId>push-notifications-server-java</artifactId>
        <version>1.1.0</version>
      </dependency>
      // ...
    </dependencies>
```

If prompted you should synchronize your project. Now open your `Function.java` and replace the contents of the file with the following:

```java
    // src/main/java/{your/reverse/domain}/Function.java
    package YOUR_PACKAGE_NAME;
    
    import java.io.IOException;
    import java.net.URISyntaxException;
    import java.util.*;
    import com.microsoft.azure.functions.annotation.*;
    import com.pusher.pushnotifications.PushNotifications;
    import com.microsoft.azure.functions.*;
    public class Function {
        @FunctionName("HttpTrigger-Java")
        public HttpResponseMessage run(@HttpTrigger(name = "req", methods = { HttpMethod.GET,
                HttpMethod.POST }, authLevel = AuthorizationLevel.FUNCTION) HttpRequestMessage<Optional<Notification>> request,
                final ExecutionContext context) {
            String instanceId = "YOUR_INSTANCE_ID";
            String secretKey = "YOUR_SECRET_KEY";
            final Notification body = request.getBody().get();
            if (body == null) {
                return request.createResponseBuilder(HttpStatus.BAD_REQUEST)
                .body("Please pass a string or in the request body").build();
            }
            PushNotifications beamsClient = new PushNotifications(instanceId, secretKey);
            List<String> interests = Arrays.asList("hello");
            Map<String, Map> publishRequest = new HashMap();
            Map<String, String> alertMessage = new HashMap();
            alertMessage.put("title", body.getTitle());
            alertMessage.put("body", body.getMessage());
            Map<String, Map> alert = new HashMap();
            alert.put("alert", alertMessage);
            Map<String, Map> aps = new HashMap();
            aps.put("aps", alert);
            publishRequest.put("apns", aps);
            try {
                beamsClient.publishToInterests(interests, publishRequest);
                return request.createResponseBuilder(HttpStatus.OK).body("Push Sent").build();
            } catch (IOException e) {
                e.printStackTrace();
                return request.createResponseBuilder(HttpStatus.INTERNAL_SERVER_ERROR).body("Push Failed").build();
            } catch (InterruptedException e) {
                e.printStackTrace();
                return request.createResponseBuilder(HttpStatus.INTERNAL_SERVER_ERROR).body("Push Failed").build();
            } catch (URISyntaxException e) {
                e.printStackTrace();
                return request.createResponseBuilder(HttpStatus.INTERNAL_SERVER_ERROR).body("Push Failed").build();
            }
        }
    }
```

This code will be used by our Azure function later on to publish notifications to devices that our registered for the `hello` interest. We retrieve the title and message from the request body before creating an object that the Pusher Beams library can use to publish our push notification. Remember to replace `YOUR_INSTANCE_ID` and `YOUR_SECRET_KEY` with the credentials from your Pusher Beams console. The above code has used an object `Notification`, this object is used to decode the request body. 

Create a new file called `Notification.java` and add the following to fix the compiler warnings:

```java
    // src/main/java/{your/reverse/domain}/Notification.java
    package YOUR_PACKAGE_NAME;
    public class Notification {
        private String title;
        private String message;  
      
        public Notification(String title, String message) {
          this.title = title;
          this.message = message;
        }
      
        public String getTitle() {
          return title;
        }
      
        public String getMessage() {
          return message;
        }
        
        @Override
        public String toString() {
          return "Notification={title=" + title + ",message=" + message + "}";
        }
    }
```

Next we need to comment out the auto-generated test case that Visual Studio Code has made for us. Go to `FunctionTest.java` and comment out the file. Alternatively you could get the test to pass if you wish.

Now we can deploy the correct code to, make sure you have saved all your files and deploy your code as you did before. Alternatively you can use the command palette and the **Deploy to Function App** command.

Return to your Azure Portal and your function app, select the **HttpTrigger-Java** (it may be named differently for you if you used a custom setup earlier in this tutorial) within the **Functions** dropdown. Click the **Get function URL** button and copy the URL for the **default (Function key)** and keep it somewhere safe. You will need it for testing your integration later on.

![zure-java-android-notifications-img7](//images.ctfassets.net/1es3ne0caaid/5bDvZhKO09JqSRMAklC7zz/239fe398dc5a0147b62659fdddced83f/zure-java-android-notifications-img7.png)

## Testing our implementation

Open your Postman HTTP rest client and create a new POST request. Add the function URL, that you got from your Azure function earlier, to the URL field. This URL contains a secret key for invoking your function, anybody with this key could potentially invoke your function so you should not share it within the public domain. Within the body of the post request add the following:

```
    {
        "title": "hello",
        "message": "Just a friendly hello"
    }
```

![azure-java-android-notifications-img9](//images.ctfassets.net/1es3ne0caaid/5wFDJgoDuqWXD9zPhDfpfV/75daa86f2b739fa6fd3bad06fffdb0f4/azure-java-android-notifications-img9.png)

Once you are done press the **Send** button at the bottom. If everything has worked as expected you should receive a push to your device.

![zure-java-android-notifications-img8](//images.ctfassets.net/1es3ne0caaid/47Szm2bm6TpJg5UEzmxrVd/070584beb4818b18d6ad3c0ff0ffb365/zure-java-android-notifications-img8.jpeg)

## Conclusion

We’ve learned how to create an Azure function using Java that can publish a push notification using Pusher Beams to an Android device. The source code for this tutorial can be found [here](https://github.com/cjbatin/Azure-function-Java-and-Pusher-Beams-for-Android-Notifications).

Azure Functions are serverless and work on a pay as you go model, which is useful if you only need to send push notifications every so often. In this tutorial, explore how to setup Pusher Beams on an Android client using an Azure Function running Java to trigger the notifications.

Azure function running Java for Android notifications

In this tutorial, we are going to look into building a todo iOS app with React Native. The most interesting part of this tutorial is the fact that we will be implementing push notifications via [Pusher Beams.](https://pusher.com/beams) Every time an updated version of the app is released to the App Store, all devices that have the app installed will get a notification informing them of the available upgrade.

## Prerequisites

To follow along in this tutorial you need the following things:

- Xcode installed on your machine. Download [here](https://developer.apple.com/xcode).
- Know your way around the Xcode IDE.
- React Native. Find out how to install it [here](https://facebook.github.io/react-native/docs/getting-started.html). You will need to follow the section **Building Projects with Native Code.**
- Carthage installed on your machine. Install it with `brew install carthage`.
- A Pusher Beams account. Create one [here](http://https:://dash.pusher.com).


> If you happen not to have `brew` installed, you can do so by running `/usr/bin/ruby -e "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/master/install)"`.


## Creating the iOS project

We will be naming our project `todoApp`. To do that we will be needing to make use of the `react-native` CLI tool to create a new iOS project. Open a terminal and run the following command:

```
    $ react-native init todoApp
```

Depending on your internet connection, the above command should take some time. Once it is done, we are ready to add functionality to our iOS app.

The first thing we need to do is to actually build a useful app - the to-do app. Open up the project in your favorite editor, then create a file called `Todo.js`. It will serve as the model for our project. In `Todo.js`, you will have to paste the following code:

``` javascript
    // todoApp/Todo.js
    
    import { AsyncStorage } from 'react-native';
    
    export default class Todos {
      constructor() {
        this.tasks = {
          items: [],
        };
    
        this.all(() => {});
      }
    
      // register a callback event passing the items found in the store
      // as it's arguments
      all = callback => {
        AsyncStorage.getItem('pushertutorial', (err, allTasks) => {
          if (err !== null) {
            return;
          }
    
          if (allTasks === null) {
            return;
          }
    
          this.tasks = JSON.parse(allTasks);
          callback(this.tasks.items);
        });
      };
    
      // saves a new item to the store
      save = item => {
        this.tasks.items.push(item);
        return AsyncStorage.setItem('pushertutorial', JSON.stringify(this.tasks));
      };
      
      // deletes an item based off an index from the store.
      delete = index => {
        this.all(items => {
          const tasks = {
            items: items.filter((task, idx) => {
              return idx !== index;
            }),
          };
          AsyncStorage.setItem('pushertutorial', JSON.stringify(tasks));
        });
      };
    }
```    

The above code uses the default key-value pair storage system bundled with React Native called AsyncStorage to retrieve and save our to-do items. You can read more about AsyncStorage [here](https://facebook.github.io/react-native/docs/asyncstorage).

Moving on, we will have to actually make use of the Todo model we created earlier. To do this, you will need to edit the `App.js` file already created by React Native during the installation earlier. You should edit `App.js` and paste in the following:

``` javascript
    // todoApp/App.js
    
    import React, { Component } from 'react';
    import {
      AppRegistry,
      StyleSheet,
      Text,
      View,
      FlatList,
      AsyncStorage,
      Button,
      TextInput,
      Keyboard,
      Platform,
    } from 'react-native';
    import Todos from './Todo';
    
    export default class TodoList extends Component {
      constructor(props) {
        super(props);
    
        this.state = {
          tasks: [],
          text: '',
        };
    
        this.todos = new Todos();
        this.syncTodos();
      }
    
      syncTodos = () => {
        this.todos.all(items => {
          this.setState({
            tasks: items,
            text: '',
          });
        });
      };
    
      updateTaskText = text => {
        this.setState({ text: text });
      };
    
      addTask = () => {
        let notEmpty = this.state.text.trim().length > 0;
    
        if (notEmpty) {
          let { tasks, text } = this.state;
    
          this.todos.save({ text });
          this.syncTodos();
        }
      };
    
      deleteTask = i => {
        this.todos.delete(i);
        this.setState({
          tasks: this.state.tasks.filter((task, index) => {
            return index !== i;
          }),
        });
      };
    
      render() {
        return (
          <View style={[styles.container, { paddingBottom: 10 }]}>
            <FlatList
              style={{ width: '100%' }}
              data={this.state.tasks}
              keyExtractor={(item, index) => item.text}
              renderItem={({ item, index }) => (
                <View key={index}>
                  <View
                    style={{
                      flexDirection: 'row',
                      alignItems: 'center',
                      justifyContent: 'space-between',
                    }}
                  >
                    <Text
                      style={{
                        paddingTop: 2,
                        paddingBottom: 2,
                        fontSize: 18,
                      }}
                    >
                      {item.text}
                    </Text>
                    <Button title="X" onPress={() => this.deleteTask(index)} />
                  </View>
                </View>
              )}
            />
            <TextInput
              style={styles.input}
              onChangeText={this.updateTaskText}
              onSubmitEditing={this.addTask}
              value={this.state.text}
              placeholder="Add a new Task"
              returnKeyType="done"
              returnKeyLabel="done"
            />
          </View>
        );
      }
    }
    
    const styles = StyleSheet.create({
      container: {
        flex: 1,
        justifyContent: 'center',
        alignItems: 'center',
        backgroundColor: '#F5FCFF',
        padding: 10,
        paddingTop: 20,
      },
      input: {
        height: 40,
        paddingRight: 10,
        paddingLeft: 10,
        borderColor: 'gray',
        borderWidth: 1,
        width: '100%',
      },
    });
```    

While the above code is simple and straightforward, I would like to explain `deleteTask`. After deleting an item from the database, we remove the app from the local state too. This is to allow a UI update.

You can now run this app by either:

- `react-native run-ios`
- Clicking the play button in Xcode. ( highly recommended ).

At this stage, you should have the following:

![ios-beams-updates-demo-1](//images.ctfassets.net/1es3ne0caaid/ujmW55mAPm8g62mcgcqcq/b60a90aaa20e6635ff057ad7560e3938/ios-beams-updates-demo-1.gif)

## Push notifications

You have worked hard into this new release of your app, it wouldn’t make any sense to have just 2% of your existing users making use of the newer release - including critical bug fixes and some UI improvements probably. Sending push notifications to users can be a good way to keep your users informed. 

In this section, we will configure and add [Pusher Beams](https://pusher.com/beams) to our application to help us deliver push notifications about updates to users who have the app installed.

We will be making use of two packages to achieve this. 

- The official iOS SDK. [GitHub Repo](https://github.com/pusher/push-notifications-swift).
- The React Native bridge for the official iOS SDK. [GitHub Repo](https://github.com/b8ne/react-native-pusher-push-notifications).

> Using the React Native bridge requires the installation of the official SDK.

We will start by installing the official iOS SDK. We will make use of Carthage for this. Carthage makes use of a `Cartfile` to track dependencies to install, so we will need to create that file.

```
    $ # Assuming you are at the root directory which is todoApp
    $ cd ios
    $ touch Cartfile
``` 

The next thing to do is to specify the exact dependencies you want installed. This is as easy as pasting the following content in the `Cartfile`:

```
    // todoApp/ios/Cartfile
    github "pusher/push-notifications-swift"
```

Once the dependencies have been specified, the next point of action is to actually install them. To do that, you will need to run the below command in a terminal:

```  
    # This assumes you are in the todoApp/ios directory
    $ carthage update
```    

Once `carthage` is done installing, you will need to:

1. In Xcode, visit the **General** settings tab of the application’s target, in the “Linked Frameworks and Libraries” section, drag and drop the `PushNotifications.framework` from the [Carthage/Build](https://github.com/Carthage/Carthage/blob/master/Documentation/Artifacts.md#carthagebuild) folder on disk. 

> A directory called Carthage will be created next to the `**Cartfile**`. You will need to locate `**PushNotifications.framework**` in the iOS folder too.

2. On your application targets’ **Build Phases** settings tab, click the *+* icon and choose **New Run Script Phase**. Create a run script in which you specify your shell (ex: `/bin/sh`), add the following contents to the script area below the shell:
    
    /usr/local/bin/carthage copy-frameworks


3. Add the path below to `PushNotifications.framework` under “Input Files". 
    
    $(SRCROOT)/Carthage/Build/iOS/PushNotifications.framework    


4. Add the path below to `PushNotifications.framework` under the “Output Files”. 
    
    $(BUILT_PRODUCTS_DIR)/$(FRAMEWORKS_FOLDER_PATH)/PushNotifications.framework    

The next step is to now install the React Native bridge which will allow us access native code (the official iOS SDK in this case ) from JavaScript. To do that, you need to run the following command

```  
    $ npm install react-native-pusher-push-notifications
``` 

1. In Xcode, in the project navigator, right click **Libraries** ➜ **Add Files to todoApp**.
2. Go to **node_modules** ➜ **react-native-pusher-push-notifications** and add **RNPusherPushNotifications.xcodeproj**
3. In Xcode, in the project navigator, select your project. Add **libRNPusherPushNotifications.a** to your project's **Build Phases** ➜ **Link Binary With Libraries**

Open the `AppDelegate.m` to register the device for push notifications. Append the following contents to the file:

```
    // todoApp/ios/AppDelegate.m
    
    // Add this to the top of the file where other imports are placed.
    #import "RNPusherPushNotifications.h" 
    
    - (void)application:(UIApplication *)application didRegisterForRemoteNotificationsWithDeviceToken:(NSData *)deviceToken {
      NSLog(@"Registered for remote with token: %@", deviceToken);
      [[RNPusherPushNotifications alloc] setDeviceToken:deviceToken];
    }
    
    - (void)application:(UIApplication *)application didReceiveRemoteNotification:(NSDictionary *)userInfo fetchCompletionHandler:(void (^)(UIBackgroundFetchResult))completionHandler {
      [[RNPusherPushNotifications alloc] handleNotification:userInfo];
    }
    
    -(void)application:(UIApplication *)application didFailToRegisterForRemoteNotificationsWithError:(NSError *)error {
      NSLog(@"Remote notification support is unavailable due to error: %@", error.localizedDescription);
    }
```    

As a final step, you will need to add the following to your Header search path **under **Build Settings**, `$(SRCROOT)/../node_modules/react-native-pusher-push-notifications/ios`.


> If you receive an error such as “dyld: Library not loaded:”, you should go to **Build Settings** and set **Always Embed Swift Standard Libraries** to yes.

Login or create an account to access your Pusher Beams dashboard [here](https://dash.pusher.com/). Create a new Pusher Beams instance using the dashboard.

Complete only step one of the iOS setup guide and follow the onscreen instructions to upload (and how to find) your APN key and Team ID. Then press the **X** to exit the setup guide and you will be returned to your dashboard for that instance. Scroll to the bottom of this page and you will find your Pusher Beams instance ID and secret key, make note of these you will need them later.

As a final step, you will need to enable push notifications capabilities for the project. You will also need to set the correct team and bundle ID as without those, push notifications capabilities cannot be enabled.

![ios-beams-updates-push-notifications-on](//images.ctfassets.net/1es3ne0caaid/4MP2SyBVwkuee0eeIOmECI/1f63fb349409a873f1fb2461004dd4fd/ios-beams-updates-push-notifications-on.png)

You will need to edit the `index.js` file to ask the user for permissions to send notifications and also subscribe to the updates topic.

``` javascript
    // todoApp/index.js
    
    import { Alert, Linking, AppRegistry, Platform } from 'react-native';
    import App from './App';
    import { name as appName } from './app.json';
    import RNPusherPushNotifications from 'react-native-pusher-push-notifications';
    
    const appUpdateInterest = 'debug-updates';
    
    // Initialize notifications
    export const init = () => {
      // Set your app key and register for push
      RNPusherPushNotifications.setInstanceId(
        'YOUR_PUSHER_INSTANCE_KEY'
      );
    
      // Init interests after registration
      RNPusherPushNotifications.on('registered', () => {
        subscribe(appUpdateInterest);
      });
    
      // Setup notification listeners
      RNPusherPushNotifications.on('notification', handleNotification);
    };
    
    // Handle notifications received
    const handleNotification = notification => {
      if (Platform.OS === 'ios') {
        Alert.alert('App update', notification.userInfo.aps.alert.body, [
          { text: 'Cancel', onPress: () => {} },
          {
            text: 'Update now',
            onPress: () =>
              // Just open up Apple's Testlight in the app store.
              // Ideally we will replace this if the app has been previously released to 
              // the app store
              Linking.openURL(
                'itms-apps://itunes.apple.com/ng/app/testflight/id899247664?mt=8'
              ),
          },
        ]);
      }
    };
    
    // Subscribe to an interest
    const subscribe = interest => {
      console.log(interest);
      RNPusherPushNotifications.subscribe(
        interest,
        (statusCode, response) => {
          console.error(statusCode, response);
        },
        () => {
          console.log('Success');
        }
      );
    };
    
    init();
    
    AppRegistry.registerComponent(appName, () => App);
```    

The above piece of code is really easy to understand as it all does is configure the PushNotifications library to make use of the key we got from the dashboard earlier. When the device has been registered with Pusher Beams, we subscribe the user to the `debug-updates` topic as all notifications for updating the app will be published to that topic.

In `handleNotification` , we show an alert dialog that provides the user with two options. One is to cancel, the other is to actually update. Clicking on the option to update the app will take the user to the Apple app store.

> Since this is an hypothetical app, we will forward the user to Apple’s Testflight app. You can replace the link to that of a real app if the app already exists on the app store.


## Sending push notifications to the device

The bulk of the entire work has been done. All is that is left now is to actually test that push notifications are delivered to the user. To do this, you will need to visit your instance page on the [dashboard](https://dash.pusher.com). You will want to navigate to the **Debug** console.

> You will need to run the app on a real device as push notifications do not work on a simulator.

![ios-beams-updates-events-log](//images.ctfassets.net/1es3ne0caaid/6uZXS1ZJdYSCyICsmc8G2/2a933f60b500cfde9bf36b018b5ab0ec/ios-beams-updates-events-log.png)

Once you have filled the above form, click on the **Publish Notifications** button. You will get an alert on your device in less than a second. 

Here is an example of how the app works. You should be able to replicate this behavior on your device.

![ios-beams-updates-demo-2](//images.ctfassets.net/1es3ne0caaid/2JmbH8rsGsWwm8GQ0CUqoQ/72927ad023e21970f8063ab6f63a23bd/ios-beams-updates-demo-2.gif)


## Conclusion

In this tutorial, we have built a mechanism for informing users of updates to our app with the help of Pusher Beams. 

The source code can be found on [GitHub](https://github.com/adelowo/pusher-app-updates-push-notifications).

In this tutorial, you will build a simple to-do app for iOS using React Native. You will integrate push notifications, so that every time an updated version of the app is deployed to the App Store, users will receive a notification.

Use Pusher Beams to notify users of updates to your iOS app

Using Pusher Beams to notify users of a new release of your iOS app

Neo Ighodaro

## Introduction

In [the previous part](https://pusher.com/tutorials/spotify-currently-playing-ios-part-1), we started by creating the API that will power the client applications. In this part, we will be adding realtime functionality to a prebuilt iOS client application. This will be a simple music player that will play songs and broadcast the current song, device, and the track position.


![spotify-currently-playing-player-img1](//images.ctfassets.net/1es3ne0caaid/7AZ9cDaNjCnzQ2UPGUdfrH/ce5d00054d5848bbce82021b1bc2cf8b/spotify-currently-playing-player-img1.gif)

This will make it easy to switch listening between clients just like Spotify does with its music clients. Let’s get started.


## Prerequisites

To follow along in this part, you must have the following requirements:

- Completed the [first part](https://pusher.com/tutorials/spotify-currently-playing-ios-part-1) of the series
- Have Xcode 10.x installed on your machine
- Have CocoaPods installed on your machine
- Knowledge of the Xcode IDE 

If you have the requirements then let’s get started.


## Setting up your project

Clone the project from [GitHub](https://github.com/neoighodaro/spotify-like-currently-playing-realtime). The iOS application is in the `iOS-*` directory in the repository. One is the completed project and the other is the music player without realtime features (`iOS_Base`). You can use the one without realtime to follow along and the other for reference.

Now that you have the project, open the `.xcworkspace` file in Xcode. Here’s a quick explanation of the project.

There is a `Podfile` in the root of the project. This file is used to define the dependencies of the application. To update or install the dependencies, close Xcode and run the following commands:

```
    $ pod install
```

Note that sometimes you may need to clear your cache to get the latest version of your dependencies. If this happens, just run the following commands below:

```
    $ pod cache clean --all
    $ pod repo update
    $ pod install
```

When your installation is complete, reopen the project using the `Spot.xcworkspace` file in the root of your project.

In the project, there is a `Main.storyboard` file that defines the scenes of the application, here is what it looks like:

![spotify-currently-playing-player-img2](//images.ctfassets.net/1es3ne0caaid/6C09CIHHOQ0xNB6cpMTvpH/f194b2f5a7fd8b1c3f8c2b13023a40eb/spotify-currently-playing-player-img2.png)

The first is the home screen with a button to enter the application. The second scene is a navigation controller that has the third scene defined as the root controller. The root controller in the third scene just displays the tracks available. The final scene displays the currently playing track.

In the project, we have a `Song` struct which is just a struct that we will use to store the song details when we fetch them from the API we built in the first part of the article. The struct looks like this:

```javascript
    import Foundation
    
    struct Song: Codable {
        let id: Int
        let title: String
        let cover: String
        let duration: Int
        let artist: String
        var isPlaying: Bool? = false
    }
```

Next, we have the `PlaylistTableViewController`. This class is responsible for fetching the tracks list, playing the selected track, keeping a song seconds elapsed timer. In the same file, we also defined a small `Duration` class that we will use for the elapsed timer.

The `TrackViewController` is responsible for the view displaying the currently playing track. It displays the time elapsed and also has a few controls but only the **Play/Pause** button works to keep the tutorial focused.

In the assets, we have the stock mp3 file, which we got from [bensounds.com](https://www.bensound.com/). We also have a placeholder cover image. If you build and run the application in a simulator, you should have the music player but without any realtime features and it also plays the mp3 file.


![spotify-currently-playing-player-img3](//images.ctfassets.net/1es3ne0caaid/5xbHO3fCwfTo6hHBcAaHFh/b49a9624dc672e6a5f548ab92ce612da/spotify-currently-playing-player-img3.gif)



## Adding some extra features to the application

Now that we have the application running, let’s connect it to our backend API and add some extra features to the application. 

To get started, make sure your Node.js application is still running in the background. To start the Node.js server, `cd` to the root of the Node.js application and run the following command:

```
    $ node index.js
```

When the server is running, we can begin.

The first thing we want to do is load the tracks list from the server. We will just use this so we can have multiple listed on the main page instead of the one. Note though that the sound we will play will always be the same.

Before we do anything, open your project’s `info.plist` and make sure the setting to **Allow Arbitrary Loads** is set to **YES.**


![spotify-currently-playing-player-img4](//images.ctfassets.net/1es3ne0caaid/1gPWOIxdNUhgRNzQOk2h2w/6b22bab83db83ab09f1d345fed325a8d/spotify-currently-playing-player-img4.png)


Next, open the `PlaylistTableViewController` class and at the top, import the `Alamofire` library:

```swift
    // File: PlaylistTableViewController.swift
    // [...]
    
    import Alamofire
```

Then, replace the contents of the `populateTracks` method with the following code:

```swift
    // File: PlaylistTableViewController.swift
    // [...]
    
    fileprivate func populateTracks() {
        Alamofire.request("http://localhost:3000/tracks").validate().responseData { res in
            guard res.result.isSuccess, let responseData = res.data else { 
              return print("Failed to fetch data from the server") 
            }
    
            let decoder = JSONDecoder()
            self.tracks = try! decoder.decode([Song].self, from: responseData)
            self.tableView.reloadData()
        }
    }
```

Also, go to the `tickTimer` method and replace the contents with the following code:

```swift
    // File: PlaylistTableViewController.swift
    // [...]
    
    @objc fileprivate func tickTimer() {
        if Duration.instance.freeze {
            return
        }
    
        Duration.instance.count += 1
        
        if Duration.instance.count > 1000 {
            killTimer()
        }
        
        else if (playingDevice == deviceName) {
            let params: Parameters = [
                "device": deviceName,
                "id": currentlyPlaying?.id ?? 0,
                "position": Duration.instance.count,
            ]
    
            Alamofire.request("http://localhost:3000/tick", method: .post, parameters: params)
                .validate()
                .responseData { _ in }
        }
    }
```

The code above makes sure that the tracks are loaded from the Node.js server instead of the hardcoded implementation we had previously.

Next, let’s add a simple indication to each track name to know which is currently playing from the list view. In the same `PlaylistTableViewController` class, find and replace the following code as seen below:

```swift
    // Replace:
    cell.textLabel?.text = "🎶 \(track.title) - \(track.artist)"
    
    // With:
    let isPlaying = track.isPlaying ?? false
    cell.textLabel?.text = "\(isPlaying ? "🎶" : "") \(track.title) - \(track.artist)"
```

Then in the `tableView(``*_*` `tableView:, didSelectRowAt indexPath:)` method, find and replace the method with the following:

```swift
    // File: PlaylistTableViewController.swift
    // [...]
    
    override func tableView(_ tableView: UITableView, didSelectRowAt indexPath: IndexPath) {
        startTimer()
        
        if lastPlayed == nil {
            lastPlayed = tracks[indexPath.row]
        }
        
        if sound.playing == false || currentlyPlaying == nil || currentlyPlaying?.id != lastPlayed?.id {
            if let index = tracks.firstIndex(where: { $0.id == currentlyPlaying?.id }) {
                tracks[index].isPlaying = false
            }
    
            tracks[indexPath.row].isPlaying = true
            self.tableView.reloadData()
            
            lastPlayed = currentlyPlaying
            currentlyPlaying = tracks[indexPath.row]
            
            if playingDevice == nil || playingDevice == deviceName {
                playingDevice = deviceName
                playSound()
                resetTimer()
            }
            
            if timerStarted == false {
                timer?.fire()
                timerStarted = true
            }
        }
    }
```

That should do the trick. Now let’s start adding realtime features.


## Adding realtime features to the application

The first thing we want to do is connect the application to Pusher Channels. To do this, open the `PlaylistTableViewController` file and in the `viewDidLoad` method, add the following code:

```swift
    // File: PlaylistTableViewController.swift
    // [...]
    
    func viewDidLoad() {
      // [...]
      
      pusherConnect()
    }
```

Then add the following property and methods to the class as shown below:

```swift
    // File: PlaylistTableViewController.swift
    // [...]
    
    var pusher: Pusher!
    
    fileprivate func pusherConnect() {
        pusher = Pusher(key: "PUSHER_KEY", options: PusherClientOptions(
            host: .cluster("PUSHER_CLUSTER")
        ))
        pusher.connect()
        
        let channel = pusher.subscribe("spotmusic")
        
        let _ = channel.bind(eventName: "tick") { [unowned self] data in
            if let data = data as? [String: Any] {
                self.handleTickEvent(data: data)
            }
        }
    }
    
    fileprivate func handleTickEvent(data: [String: Any]) {
        guard let device = data["device"] as? String, device != deviceName else {
            playingDevice = deviceName
            return
        }
        
        guard let position = data["position"] as? Int else { return }
        
        if playingDevice == deviceName {
            killTimer()
        }
        
        playingDevice = device
        
        setTimer(count: position)
        startTimer()
        pauseSound()
    }
```

> Replace the `PUSHER_*` placeholders with the values in your Pusher dashboard.

We are using a device name so we can know where the event is fired from. We don’t want an event fired from the same device to be handled by the same device.

At the top of the class, import the `PusherSwift` library:

```swift
    // File: PlaylistTableViewController.swift
    // [...]
    
    import PusherSwift
```

One last thing we need to make sure we do is ping the main server to update the `tick` event. We will use this to broadcast the position of the currently playing track at all times the track is playing.

**Track Controller**
There is another controller called the `TrackViewController`, which displays the song details when a song is tapped. We do not need to make any changes to this file but it could come in handy if you need to make some improvements to the application.

Great. Now let’s test our application.


## Testing your application

Make sure the Node server is running in the background. You can run the server by running the command below in the root of the API project:

```
    $ node index.js
```

Now, build your music application and run it . You should notice no major difference from how it was but if you log into your Pusher dashboard and look at the **Debug Console** for your application, you will notice there will be an event fired for every second the song plays.


![spotify-currently-playing-player-img5](//images.ctfassets.net/1es3ne0caaid/2G2hrPiZKwvt9HcfJuJaeo/df3770238bfb0bfb59d684f3f7eab48c/spotify-currently-playing-player-img5.gif)


Now that we have the ticker, let’s build another application that listens for these changes and displays it in realtime. 

## Conclusion

In this part of the tutorial, we have learned how we can use realtime features to enhance our music player. In the next part, we will consume this information from another player.

The source code is available on [GitHub](https://github.com/neoighodaro/spotify-like-currently-playing-realtime).

When using music streaming services like Spotify, you can see realtime technology in action when you are using multiple devices. On the other devices, you can see how much playtime has elapsed. This three-part tutorial series looks at how to integrate this feature into your application. In the second part, add realtime functionality to a prebuilt iOS client application.

When using music streaming services like Spotify, you can see realtime technology in action when you are using multiple devices. In the second part of this tutorial series on how to integrate this feature into your application, add realtime functionality to a prebuilt iOS client application.

Build a Spotify-like currently playing feature - Part 2

Building a Spotify-like currently playing feature: Part 2 - Building the iOS player

## Introduction

When using music streaming services like Spotify, you can see realtime technology in action when you are using multiple devices. On the other devices, you can see how much playtime has elapsed.

In this series, we will take a look at how you can integrate this feature into your application with minimal fuss. We will be building a web API, a web app, and an iOS application. Both apps will consume the API we built.


![spotify-currently-playing-API-img1](//images.ctfassets.net/1es3ne0caaid/5c40g0HYWdT9vg9kcInhf2/467a5c2254947a427a86b52d214eddfe/spotify-currently-playing-API-img1.gif)


## Prerequisites 

To follow along in this part of the series, you must have the following requirements:

- Node.js (any LTS version) and NPM installed locally on your machine. Install [here](https://nodejs.org/en/download/).
- Basic knowledge of JavaScript.
- Basic knowledge of the command-line interface.


## Setting up

The first thing you need to do is [create a Pusher account](https://pusher.com). Next, create a Pusher Channels application using the dashboard.

Next, create a root directory for your Web API project. We will call it `spot`. When this is done, launch your terminal application and `cd` to the directory you just created. In this directory, run the following command:

```
    $ npm init -y
```

![spotify-currently-playing-API-img2](//images.ctfassets.net/1es3ne0caaid/72uTIgkgk6Qf8VuoktelDK/7d0c75cc5e43fe3617966644a208a7e0/spotify-currently-playing-API-img2.png)

At the end, you should have a `package.json` file in the root of your application.

Let’s install some dependencies we will need for our API. In the terminal, run the following command:

```
    $ npm install --save express body-parser pusher cors
```

![spotify-currently-playing-API-img3](//images.ctfassets.net/1es3ne0caaid/6irkA5SbfuJU3Yh9cr9cIU/235f7a61f347e91a5bee6c7e74cf37c7/spotify-currently-playing-API-img3.png)

This will install all the dependencies we need to build the API. When the installation is complete, we can move on to building the application.


## Building the web API

Now that we have everything installed, let’s create the web API. Open the project in an IDE of your choice. Create a new `index.js` file. This will be where we will have all our logic. Let’s start building our API.

Let’s start by importing and using all the dependencies that we installed using npm. In the file, paste the following code:

```javascript
    // File: index.js
    const express = require('express');
    const bodyParser = require('body-parser');
    const Pusher = require('pusher');
    const fs = require('fs');
    const cors = require('cors');
    const path = require('path');
    const app = express();
```

Above, we imported and created instances of the dependencies we installed using npm. Next, let’s create our API endpoints.

We will be creating three endpoints:


1. `tracks` - this endpoint will return all the available tracks for the music player. Since we are not building a full-fledged application, we will be mocking the data from a flat JSON file. We will create this file later on.
2. `current` - this endpoint will return the currently playing song. This will make it easy for other clients to know which song is currently playing when they are loaded.
3. `tick` - this endpoint will trigger a Pusher event. As the song plays, we will intermittently send the current position of the song playing using this endpoint. This is so that other web clients can know where the track is currently.

Let’s start implementing these endpoints.

In the `index.js` file, paste the following code:

```javascript
    // File: index.js
    // [...]
    
    app.use(bodyParser.json());
    app.use(bodyParser.urlencoded({ extended: true }));
    
    let tracks = JSON.parse(fs.readFileSync(path.resolve(__dirname, 'data.json')));
    
    app.get('/tracks', (req, res) => {
      res.json(tracks);
    });
```

As seen above, we are returning the contents of a nonexistent JSON file. This file is supposed to contain the data for our tracks. Let’s create this file.

Create a file named `data.json` and paste the following JSON string into the file:

```json
    // File: data.json
    [
      {
        "id": 1,
        "duration": 195,
        "artist": "JugHead",
        "title": "Polly",
        "cover": "https://via.placeholder.com/500x500"
      }
    ]
```

Now that we have the data file, we can continue building the API. In the `index.js` file, paste the following code to create the second endpoint:

```javascript
    // File: index.js
    // [...]
    
    let current = {};
    
    app.get('/current', (req, res) => {
      res.json(current);
    });
```

Above, the endpoint simply returns the currently playing track if there is any or an empty JSON object if nothing is playing. 

Let us add the last endpoint. In the `index.js` file, add the following code:

```javascript
    // File: index.js
    // [...]
    
    app.options('/tick', cors());
    
    app.post('/tick', cors(), (req, res) => {
      const { id, position, device } = req.body;
    
      for (let index = 0; index < tracks.length; index++) {
        if (tracks\[index\]['id'] === parseInt(id)) {
          current = tracks[index];
          pusher.trigger('spotmusic', 'tick', { id, position, device });
          return res.json({ status: true });
        }
      }
    
      res.json({ status: false });
    });
```

In the endpoint above, we will receive the ID of the track currently being played, the position of the track and then we will receive the device that is sending the request. When we find a matching existing track, we will trigger the event to Pusher and save the currently playing track on the server.

Finally, let’s make sure the Node.js server is listening on port 3000 when we start the server. In the `index.js` file, add the following code:

```javascript
    // File: index.js
    // [...]
    
    app.listen(3000, () => console.log('Listening on port 3000!'));
```

Now that we have the endpoints set up, let’s add realtime triggers to Pusher. Before the `app` variable, add the following code:

```javascript
    // File: index.js
    // [...]
    
    let pusher = new Pusher({
      appId: 'PUSHER_APP_ID',
      key: 'PUSHER_APP_KEY',
      secret: 'PUSHER_APP_SECRET',
      cluster: 'PUSHER_APP_CLUSTER',
      useTLS: true
    });
```

> Replace the `PUSHER_APP_*` placeholders with the credentials from your Pusher dashboard.


## Running the application server

Now that we have built the application, we need to run the application in a server. In your terminal, run the following command to start the Node server:

```
    $ node index.js
```

![spotify-currently-playing-API-img4](//images.ctfassets.net/1es3ne0caaid/R7Lg5VnlvvSRGGsoDOQDN/946a64a11c580664fd7cb2c113d6474b/spotify-currently-playing-API-img4.png)

Now your server is running, in the next parts, we will move on to creating the clients that will consume the API that the Node.js app provides.

## Conclusion

In this part, we created a web API for our music application. This API will be responsible for returning the tracklist and also updating the now playing track. It will also be responsible for triggering events to Pusher. 

In the next part, we will start building an iOS app that will consume the API we built in this part. The source code is available on [GitHub](https://github.com/neoighodaro/spotify-like-currently-playing-realtime).

When using music streaming services like Spotify, you can see realtime technology in action when you are using multiple devices. On the other devices, you can see how much playtime has elapsed. This three-part tutorial series looks at how to integrate this feature into your application. In the first part, build the web API.

When using music streaming services like Spotify, realtime technology allows you to see on other devices how much playtime has elapsed. This three-part tutorial series looks at how to integrate this feature into your application. In the first part, build the web API.

Build a Spotify-like currently playing feature - Part 1

Building a Spotify-like currently playing feature: Part 1 - Building the web API

## Introduction

Pusher Beams allows you to customize push notifications you send to your devices via a server. However it can be expensive to run a server 24 hours a day 7 days a week and we may only need to send notifications every so often.

This is where [Microsoft Azure Functions](https://azure.microsoft.com/en-gb/services/functions/) can help. Azure Functions are serverless and work on a pay as you go model (with a generous free tier). This means that you only pay for when you use the function. We’re going to explore how we can setup Pusher Beams on an iOS client using an Azure Function running Java to trigger the notifications.


## Prerequisites


- A free Microsoft Azure account. You can create one [here](https://azure.microsoft.com/en-gb/free/).
- A free Pusher account. You can create one [here](https://dash.pusher.com/authenticate).
- Homebrew installed on your machine. Instructions [here](https://brew.sh).
- Postman or another HTTP client installed on your machine. You can download Postman from [here](https://www.getpostman.com).
- Xcode 10+
- MacOS
- An iOS device for testing notifications.
- An understanding of iOS development and Xcode environment.
- Cocoapods - Install instructions [here](https://guides.cocoapods.org/using/getting-started.html).

## Create your Azure function

### Creating a Pusher Beams instance
Log in or create an account to access your dashboard [here](https://dash.pusher.com). Create a new Pusher Beams instance using the dashboard.

![azure-java-notifications-ios-img1](//images.ctfassets.net/1es3ne0caaid/6VeFGvrfeQyRunvLYsoNUN/541c20a2530920155542cefcc6a000d2/azure-java-notifications-ios-img1.png)

Complete step one of the iOS setup guide, by providing your APNS key and team ID and clicking **Continue**. We will pick up the remainder later on in this tutorial. Press the **X** to exit the setup guide and you will be returned to your dashboard for that instance. Scroll to the bottom of the page and you will find your Pusher Beams instance ID and secret key, make note of these you will need them later.

### Creating our function
Log in to your Microsoft Azure portal [here](http://portal.azure.com). Using the search facility (found at the top of the page) search for “Function App”. 


> **Note:** When searching make sure to sure for “Function App” and not “Function Apps”

Once you are on the function app page click **Add** to begin the process of adding a new Azure Function. You will need to give your app a name, this must be unique and you cannot use full stops. Try reverse domain naming like this: `com-example-appname`. I have used `PusherBeams-Java-iOS`. As long as the radio buttons are set to **Create new**, entering a name should also auto complete the resource group and storage. If it hasn’t you should complete these fields as well. 

Select your **Subscription** and **Hosting Plan.** If you’re unsure what these should be leave them as the default values. 

We will also be using **Windows OS** for this tutorial and our location will be set to **Central US**. However feel free to alter the location if the **Java** run time is available there as well. Make sure your **Runtime Stack** is set to **Java** and click **Create**.

![azure-java-notifications-ios-img2](//images.ctfassets.net/1es3ne0caaid/WwwGIXP19gHbtI1qLQlEE/b23f737544d7ff4e43542e865b4a33d6/azure-java-notifications-ios-img2.png)

Once your resource has been created you should receive a notification on the navigation bar. If you don’t see this, wait a couple of minutes and refresh the page. Your resource should appear in a list of Function Apps. Select your resource. 

Now you have created a Function App you need to create a Function. On the overview page select the button **New Function** or from the side bar click on the **+** the is next to the **Functions (Read Only)** drop down. 

![azure-java-notifications-ios-img3](//images.ctfassets.net/1es3ne0caaid/3Ff8RS3kVNrbdGD6OMvyrz/7c0697a1d0e5e9d81d435d98b3ace955/azure-java-notifications-ios-img3.png)

You will be given a selection of ways to build your function, select the **Visual Code** option and click **Continue**. On the next page select the **Direct Publish** option and click **Continue.** Follow the instructions on the next page for installing and setting up for Visual Code, the Azure command line tools and the Azure Functions extension for Visual Studio Code. Make sure you have signed in to your Azure account in Visual Studio Code before continuing.

![azure-java-notifications-ios-img4](//images.ctfassets.net/1es3ne0caaid/2tApHmDSzXbVgLLWDlCunh/7f3a61470c96ea15ffb3633fb953503f/azure-java-notifications-ios-img4.png)

Before you continue you will need to install maven by running the following in terminal:

```
    $ brew install maven
```

With Visual Code Studio open open the command palette (**View → Command Palette**), select **Create New Project**. When prompted provide an empty directory for your project and select the language to be **Java**. Provide a group ID using a reverse domain name naming method. Complete the remaining steps as appropriate (you can just accept the default values).

Azure functions make it easy to invoke your code by hitting an HTTP endpoint. This is great for push notifications, as you can hit this endpoint using our HTTP rest client and passing in our message. You will see more of this later when you test your integration. For now all you need to know is that the default implementation will set this up for you.


> **Note:** There are lots of other templates available for invoking your function and you may wish to explore these as well. You can always invoke your function from the portal if you wish to.

 
Once your project is setup you can deploy it straight from Visual Code, right click on the newly created `src` folder and select **Deploy to Function App**. Select the function app you created earlier for example Pusher-Beams-Java-iOS. This will complete the deployment process for you, you can confirm the success by checking the terminal output in Visual Code Studio and by refreshing your Azure Portal. 

![azure-java-notifications-ios-img5](//images.ctfassets.net/1es3ne0caaid/4XwNT60QBbQHATOLzNaU6b/4eec8f1a724388bedb708f9ed22a7c24/azure-java-notifications-ios-img5.png)

### Writing our function

The first thing we need to do in our function is install our dependencies. Open your `pom.xml` file and add the following to your dependencies:

```xml
    // pom.xml
    <dependencies>
      // ....
      <dependency>
        <groupId>com.pusher</groupId>
        <artifactId>push-notifications-server-java</artifactId>
        <version>1.1.0</version>
      </dependency>
      // ...
    </dependencies>
```

> **Note:** If prompted you should synchronize your project. If you are not prompted you may need to install the maven extension for Visual Studio Code such that you can synchronise.

Now open your `Function.java` and replace the contents of the file with the following:

```java
    // src/main/java/uk/co/cjapps/Function.java
    package YOUR_PACKAGE_NAME;
    
    import java.io.IOException;
    import java.net.URISyntaxException;
    import java.util.*;
    import com.microsoft.azure.functions.annotation.*;
    import com.pusher.pushnotifications.PushNotifications;
    import com.microsoft.azure.functions.*;
    public class Function {
        @FunctionName("HttpTrigger-Java")
        public HttpResponseMessage run(@HttpTrigger(name = "req", methods = { HttpMethod.GET,
                HttpMethod.POST }, authLevel = AuthorizationLevel.FUNCTION) HttpRequestMessage<Optional<Notification>> request,
                final ExecutionContext context) {
            String instanceId = "YOUR_INSTANCE_ID";
            String secretKey = "YOUR_SECRET_KEY";
            final Notification body = request.getBody().get();
            if (body == null) {
                return request.createResponseBuilder(HttpStatus.BAD_REQUEST)
                .body("Please pass a string or in the request body").build();
            }
            PushNotifications beamsClient = new PushNotifications(instanceId, secretKey);
            List<String> interests = Arrays.asList("hello");
            Map<String, Map> publishRequest = new HashMap();
            Map<String, String> alertMessage = new HashMap();
            alertMessage.put("title", body.getTitle());
            alertMessage.put("body", body.getMessage());
            Map<String, Map> alert = new HashMap();
            alert.put("alert", alertMessage);
            Map<String, Map> aps = new HashMap();
            aps.put("aps", alert);
            publishRequest.put("apns", aps);
            try {
                beamsClient.publishToInterests(interests, publishRequest);
                return request.createResponseBuilder(HttpStatus.OK).body("Push Sent").build();
            } catch (IOException e) {
                e.printStackTrace();
                return request.createResponseBuilder(HttpStatus.INTERNAL_SERVER_ERROR).body("Push Failed").build();
            } catch (InterruptedException e) {
                e.printStackTrace();
                return request.createResponseBuilder(HttpStatus.INTERNAL_SERVER_ERROR).body("Push Failed").build();
            } catch (URISyntaxException e) {
                e.printStackTrace();
                return request.createResponseBuilder(HttpStatus.INTERNAL_SERVER_ERROR).body("Push Failed").build();
            }
        }
    }
```

This code will be used by our Azure function later on to publish notifications to devices that our registered for the `hello` interest. We retrieve the title and message from the request body before creating an object that the Pusher Beams library can use to publish our push notification. Remember to replace `YOUR_INSTANCE_ID` and `YOUR_SECRET_KEY` with the credentials from your Pusher Beams console. The above code has used an object `Notification`, this object is used to decode the request body. 

Create a new file called `Notification.java` and add the following to fix the compiler warnings:

```java
    // src/main/java/uk/co/cjapps/Notification.java
    package YOUR_PACKAGE_NAME;
    public class Notification {
        private String title;
        private String message;  
      
        public Notification(String title, String message) {
          this.title = title;
          this.message = message;
        }
      
        public String getTitle() {
          return title;
        }
      
        public String getMessage() {
          return message;
        }
        
        @Override
        public String toString() {
          return "Notification={title=" + title + ",message=" + message + "}";
        }
    }
```

Next we need to comment out the auto-generated test case that Visual Studio Code has made for us. Go to `FunctionTest.java` and comment out the file. Alternatively you could get the test to pass if you wish.

Now we can deploy the correct code to, make sure you have saved all your files and deploy your code as you did before. Alternatively you can use the command palette and the **Deploy to Function App** command.

Return to your Azure Portal and your function app, select the **HttpTrigger-Java** (it may be named differently for you if you used a custom setup earlier in this tutorial) within the **Functions** dropdown. At the top of your text editor you should see a **Get function URL** button, click this and copy the URL for the **default (Function key)** and keep it somewhere safe. You will need it for testing your integration later on.

![azure-java-notifications-ios-img6](//images.ctfassets.net/1es3ne0caaid/10i8W3cMazDeKg5oTeYMRH/0fc625c944c2b280989be40c345ab26e/azure-java-notifications-ios-img6.png)

## Create your iOS application

Now that we have created our Azure function, we need to have a user that has actually registered for notifications and signed up for the hello interest so we can test out our implementation. We’re going to create a very basic app that doesn’t actually show anything to the user except for the notification on the lock screen.

### Project setup

Create a new **Single View App** using Xcode and name it something like AzurePush. Once the project is created we need to install the Beams SDK. Open the terminal and go to the working directory of the newly created project and run the following command.

```
    $ pod init
```

Open the newly created `Podfile` and add the following pod:

```
    pod 'PushNotifications', '2.0.0'
```

In the terminal run:

```
    $ pod install
```

Make sure you close your Xcode project and reopen the newly created Xcode Workspace before continuing. Within your project capabilities make sure you have switched on the **Push Notifications** capability. Also turn on the **Background Modes** capability and tick the box for **Remote Notifications**.

Open your `AppDelegate.swift` file and replace its contents with the following. Remembering to replace the instance ID with your own.

```swift
    // AppDelegate.swift
    import UIKit
    import PushNotifications
    
    @UIApplicationMain
    class AppDelegate: UIResponder, UIApplicationDelegate {
        var window: UIWindow?
        let pushNotifications = PushNotifications.shared
    
        func application(_ application: UIApplication, didFinishLaunchingWithOptions launchOptions: [UIApplication.LaunchOptionsKey: Any]?) -> Bool {
            self.pushNotifications.start(instanceId: "YOUR_INSTANCE_ID")
            self.pushNotifications.registerForRemoteNotifications()
            try? self.pushNotifications.addDeviceInterest(interest: "hello")
    
            return true
        }
    
        func application(_ application: UIApplication, didRegisterForRemoteNotificationsWithDeviceToken deviceToken: Data) {
            self.pushNotifications.registerDeviceToken(deviceToken)
        }
    
        func application(_ application: UIApplication, didReceiveRemoteNotification userInfo: [AnyHashable: Any], fetchCompletionHandler completionHandler: @escaping (UIBackgroundFetchResult) -> Void) {
            self.pushNotifications.handleNotification(userInfo: userInfo)
        }
    }
```

You can now run the application on your iOS device and accept to receive notifications. The SDK will then manage registering our interest in hello. Remember to replace `YOUR_INSTANCE_ID` with your instance ID credential from your Pusher Beams console.


## Testing our implementation

Open your Postman HTTP rest client and create a new POST request. Add the function URL, that you got from your Azure function earlier, to the URL field. This URL contains a secret key for invoking your function, anybody with this key could potentially invoke your function so you should not share it within the public domain. Within the body of the post request add the following:

```
    {
        "title": "hello",
        "message": "Just a friendly hello"
    }
```

![azure-java-notifications-ios-img7](//images.ctfassets.net/1es3ne0caaid/2V1BpM6U4O13L5JieweQEA/332b3479e64f6871050a13e2573e0c12/azure-java-notifications-ios-img7.png)

Once you are done press the **Send** button at the bottom. If everything has worked as expected you should receive a push to your device.

![azure-java-notifications-ios-img8](//images.ctfassets.net/1es3ne0caaid/1uB5kAmXFc8iFarjsQOa9b/d36b8861720619acb7b66dbe92bc1fac/azure-java-notifications-ios-img8.jpeg)

## Conclusion

We’ve learnt how to create an Azure function using Java that can publish a push notification using Pusher Beams to an iOS device. The source code for this tutorial can be found [here](https://github.com/cjbatin/Azure-function-Java-and-Pusher-Beams-for-iOS-Notifications).

Azure Functions are serverless and work on a pay as you go model, which is useful if you only need to send push notifications every so often. In this tutorial, explore how to setup Pusher Beams on an iOS client using an Azure Function running Java to trigger the notifications.

Azure function running Java for iOS notifications

Suragch

This tutorial introduces common authentication and security problems, and walks through two authentication methods using Dart. Use the Aqueduct server framework to simplify development, and Postman to quickly test your authentication setup.

Learn & Discover Pusher

Send Push Notifications to your Android app

Notify Slack users of push notification status with webhooks

Creating a server health monitoring app with Laravel

Azure function running Java for Android notifications

Using Pusher Beams to notify users of a new release of your iOS app

Building a Spotify-like currently playing feature: Part 2 - Building the iOS player

Building a Spotify-like currently playing feature: Part 1 - Building the web API

Azure function running Java for iOS notifications

Authentication with server side Dart

Products

Developers

Company

Connect