Creating a Retrospective Board with deepstream.io

With more and more teams working remotely, tools have sprung up everywhere, shifting online processes. The fun part behind retrospective planning poker and other methods was always the interactivity, seeing cards move around and identifying barely readable scribbles.

As such, let’s take a look at how we can use data-sync to create a real-time retrospective board that supports both desktops and mobile phones. It will look something like this:

In the spirit of agile approaches, let’s start by breaking down our requirements. Our retrospective board needs to allow us to:

• Add, edit and move cards
• Allow everyone with access to the board to see live updates
• Have a mobile friendly interface

And to add a little bit of privacy in case you decide to make the application public, let’s throw in a few security requirements:

• Only let people access the board with a username and password
• Only let cards be edited by their creator.

To achieve this, we’ll be using good old jQuery on the frontend and deepstream.io as our backend.

Setting up a server

Installing deepstream is as simple as downloading the latest version from the site or installing it on Linux via apt or yum.

Configuring credentials

Once we’ve got the server, we want to make sure that only users with a valid password can log in. Deepstream supports a number of different authentication strategies, but we’d like to keep things simple. For this tutorial, we’ll simply provide a file with usernames and hashed passwords. To use this, we need to switch to file authentication.

This is done in deepstream’s config.yml file, which can be found either in conf/config.yml or in /etc/deepstream/conf/ on Linux. Here, change auth type:none to the following:

You’ll find a default users.yml file in the same folder where you can add your users, and any user-specific metadata. We’ll use it to define the users’ roles:

To generate password hashes, just use deepstream’s command line interface via the executable:

And finally, start the server via:

Creating the board

Connecting to deepstream

Great! Now that we have a server running, let’s look at setting up the board.

The first thing we’ll need to do is let our users log in. To do this we’ll need to get the deepstream client. You have a few different flavours of installation, either using npm, bower, or having it come as part of your react or polymer plugins. For this example we’re going to go with the simplest approach of just fetching it directly from a CDN:

Now that we have the deepstream library included, we’ll need to get it to connect to the server.

Since we want to limit users who can use the board, we are going to have to get the username and password from a minimalistic login form:

Which on submit triggers a login to the board:

And that’s part two. You now have your users connected and logged into deepstream!

The juicy parts

Now comes the fun part—getting all the cards to remain in sync across all browsers/phones. Let’s take a step back and first look at data-sync and how it is used. We’ll be using records and lists to keep state. A record is just a convenient way of storing and manipulating JSON with data-sync built in.

Core concepts:

• A record has a unique identifier. You can create your own or use getUid() to generate one for you:

• You can set its data:

• To get data:

• To subscribe to changes:
  
  record.subscribe( 'position', ( newPosition ) = { console.log( 'Card moved!' ) } )

  1 2 3

  record.subscribe( 'position', ( newPosition ) = {   console.log( 'Card moved!' ) } )

Deepstream also has a concept of a “list”, which is a useful way to maintain a set of records that have things in common. You can addEntry( removeName ), removeEntry( recordName ) and listen to entry-added and entry-removed events.

Let’s take a look at how we can put these things together to make a board. We’ll need a list to contain the set of all the records on the board. Whenever a card is created, the list will notify us and we can add it into the DOM. Since the list is the entry point to all our records, we need to use a non-random name.

That covers most of the creating of the board. The demo code on GitHub fills in all the parts I’ve not covered here, such as removing cards, and different ways you can add cards depending on your input devices.

The final requirement is dragging a card around and seeing it update on all other browsers. You can see this being done here:

Note how we prevent jQuery from updating the DOM directly. This is because we are using the record as our single source of truth. By doing so, our code will process things the same way, regardless of whether the action happened remotely or locally. This is a great way to consume changes—otherwise, your code will become cluttered with unwanted conditions.

Perfect, now our board starts to look presentable! Let’s look at adding a tiny bit of permissions now that we are familiar with the card’s JSON structure.

Permissions

Deepstream comes with a powerful permissioning language called Valve, which can be used to create rules to allow/deny all possible client actions. Going back to our last requirement, we want to only allow the creator to update his/her own cards. Since we’ve made the username part of the recordname, this is rather straightforward. Let’s take a look at how we can implement that in our pemission.yml config file.

And that’s it. The users who can edit cards have to be the same as the cards’ creators.

Let’s introduce a tiny bit of scope creep, and allow the scrum-master to edit any card and be the only one who can delete cards. Luckily, we added this earlier on in the user config, so we have access to user roles.

And done! We now have all the bits and bobs of a real-time, authenticated and permissioned retrospective board!

Do you think you can beat this Sweet post?

If so, you may have what it takes to become a Sweetcode contributor... Learn More.