Notifications are an integral part of any product. It helps to improve user engagement and makes sure they get useful information at every step of interaction with the product. We built Engagespot to help developers from spending months to build a notification stack for their product.
When we talk about notifications, it's not just about Push. A notification is any piece of information for the user. And it should be delivered through multiple channels like email, push, realtime message inside the app, sms etc, depending on the urgency and nature of the information.
A good product notification stack should have the following components -
- Multiple notification delivery channels such as InApp, Web Push, Mobile Push, Email, SMS etc.
- Notification Preference Manager for Users
- Notification Categories
- Grouped Notifications etc.
Building a basic notification system for your product with a single channel such as email might seem easier in the begining. But once you want to add more features and give preference controls to your users on different channels and categories, most of your development effort will be spent on notifications. We believe that a developer should never try to re-invent the wheel. Write code only for what is not there, else simply plug it in! Your time is precious. Spend it on building your core features.
Why building a Product Notification System is complex?
Like I said, it's very easy if you just need to notify your users via email. Simply integrate an email API, or an SMTP provider. Done!
Now as your product scales and add more features, you will have several type of notifications. For example in a social network, you might want to send "Someone commented on your photo", "Someone liked your photo", security notifications, friend request notifications, New message notifications etc. Some of these notifications have an urgent nature, and some of them are just informational. So you must decide which channel is best based on the urgency of notification.
Also, your users might have different preference on receiving notifications. Some of them want a particular type of notifications to be delivered only via email. Some of them donot want to receive any notifications at all. So you must build a fine grained notification preference module for users.
Do you think you should be spending most of your development effort in building a notification system like this? But ofcourse you cannot ignore having all these features because it's must for improving your product's user experience. For example look at products like Facebook and Slack and how smart they are in delivering notifications via different channels.
This is where a solution like Engagespot can help. Instead of spending months of time building, improving and maintaining a notification engine, you can simply plug in a full-fledged product notification system in minutes, without compromising on any functionalities.
Simply, you should never attempt to build a notification system from scratch. And that's why we've developed Engagespot. We focus on improving all the aspects of a highly scalable notification system while you focus on building your product.