A Notification Timeline using React

Subscribe to my newsletter and never miss my upcoming articles


It's been a while I have done much with React. When I was trying it out with simple state management, in-built hooks, basic styling and managing events, I thought, why not to build something useful? That's when the idea of building a simple, light-weight notification-timeline came into my mind.

So what is notification-timeline?

  • As the name indicates, it notifies you sooner a notification arrives.
  • It helps you in reading through your notifications in timed sorted manner. That's where the timeline comes from.
  • You can mark the notifications as read.
  • You can identify what notification was received and when.
  • Few more customization capabilities that we will discuss bit later.

How does it look?

  • The basic look and feel contains a bell icon along with a number of unread notifications for you to look into.


  • You click on the bell icon to open up a pop-over to read the notifications and mark them as read, if required.



In this article, I am going to explain some source code at the high level. Please stick to it. I am sure, you will have some take-away from it.

In case, you want to get to the code or the demo early, here are the details:


You can access the demo from here: https://notify-timeline.netlify.app/

Source Code

All the Source Code are here in the git repo. If you like the work, please show your support with a star for the repo.

Yayyy, it is available as npm

Did you know, this component is also available as a npm? Yeah! you can download and install it using,

npm i react-notification-timeline


yarn add react-notification-timeline

Once installed, it can be imported into your React project as,

import NotifyMe from 'react-notification-timeline';

Use the component as,

  heading='Notification Alerts'

For more details about the properties and customizations, please read it from here.

Please give it a try and let me know how it goes. Almost nothing is bug free! Feel free to be a contributor if you would like to find-try-fix bugs or add features to it. You are most welcome.

Understanding the 'How' part

Thank you for reading through so far! This section of the article is going to explain few important parts of the source code and the basic logic around it. Here is the direct link to the component file.

First is the data

The notification-timeline component expects data in the following format,

       "update":"70 new employees are shifted",
       "update":"Time to take a Break, TADA!!!",

The object must have two properties.

  • timestamp: The timestamp of the time a message was generated. This must be of type long that represent a timestamp value.
  • update: The message to show as notification.

Note: The key names, timestamp and update can be customized as explained in the properties section.

States to manage

The hook useState returns a pair. First is the current state and second is an updater function. We usually take advantage of array destructuring to assign the values. The initial state value can be passed using the argument.

The notification component manages few states using useState,

  • To show the unread message count
     const [showCount, setShowCount] = useState(false);
  • How many unread messages
     const [messageCount, setMessageCount] = useState(0);
  • To show the message panel on click of the bell icon
     const [show, setShow] = useState(false);
  • To set the click target of the message panel
     const [target, setTarget] = useState(null);
  • To maintain a read index. This is to determine, how far the messages were read so that the unread messages can be shown with a different style.
     const [raedIndex, setReadIndex] = useState(0);

Handle the side effects

The hook useEffect is used for handling any sort of side effects like, state value changes, any kind of subscriptions, network requests etc. It takes two arguments, first a function that will be invoked on the run and, an array of the values that will run the hook.

It runs by default after every render completes. However we can make it run whenever a particular value changes by passing it as the second parameter. We can also make it run just once by passing an empty array as the second parameter.

Notification component handles the side effect of the data changes. Whenever a new notification arrives, the data gets muted and we need to handle this side effect.

useEffect(() => {
        if (!sortedByKey) {
            data.sort((a, b) => b[key] - a[key]);

        let readItemLs = reactLocalStorage.getObject(storageKey);
        let readMsgId = Object.keys(readItemLs).length > 0 ? readItemLs['id'] : '';

        let readIndex = (readMsgId === '') ? data.length : 
                               elem => 
                                   elem[key] === readMsgId);

        readIndex === -1 ? readIndex = data.length : readIndex;

        (data.length && readIndex) > 0 ? 
            setShowCount(true) : setShowCount(false);

    }, [data]);

On data change,

  • Check and sort by timestamp, if required.
  • We track the last read message by adding the timestamp of it into the local storage. We check if any last read item id is in the local storage.
  • We set the message count, last read index accordingly.

The render part

Last, the render part. We have a bell icon that shows the unread message count and method to handle the click event.

<div className="notification-container">
    <div className = 
                 showCount ? 
                   'notification notify show-count' : 
                       'notification notify'
            onClick={event => handleClick(event)}>
                    <Bell color={bellColor} size={bellSize} />

Important to note here, we use the data-* attribute to embed custom data. In this case it is the unread message count using the data-count attribute. Read more about HTML data-* attribute from here.

Next, the handleClick() method handles to show the pop-over with the notification messages. To do that, we just need to update couple of states,

// Handle the click on the notification bell
const handleClick = (event) => {

That's all for covering all the important parts here. I have used feather icons for the bell icon and react bootstrap for the message pop-over component.

Concluding with a plan

I would like to enhance the code better as in, I can make it more precise and short. There are lots of scope to improve this component with additional features like,

  • Showing total message count.
  • Mark as unread.
  • Limiting the total number of notifications and flush out.
  • Read/Unread Selected notification messages.
  • Delete all the notification messages.
  • Better persistence hook, other than the browser local storage.
  • Better look-and-feel.

That's all for now. I am happy to share my learning with you and that's motivates me further to learn more.

If it was useful to you, please Like/Share so that, it reaches others as well. To get e-mail notification on my latest posts, please subscribe to my blog by hitting the Subscribe button at the top of the page. You can also follow me on twitter @tapasadhikary.

The cover photo is an improvisation on top of the awesome work by freepik.

Gepenyan's photo

Is there any way to customize the bell icon?

Gepenyan's photo

I mean to replace t with another svg for example. Not only the color etc.

Tapas Adhikary's photo

Gepenyan, At this point no. But, this is a really good enhancement request! Thanks for asking.

I have added a GitHub issue to track this: github.com/atapas/notifyme/issues/5

A bit of background to this:

I am using the Bell icon from feather js.

import { Bell } from 'react-feather';

As part of the enhancement, I will have to keep it open for an icon supplied as an optional prop.

Btw.. feel free to do any changes to the code. I may get to it a bit late. Repo is here,

Victoria Lo's photo

Very cool! Maybe I'll build something using your notification timeline :)