This article originally appeared on Hackernoon.

I’ve been working at Carnival.io a while now, and I’ve worked with many fortune 500 companies and startups to help them get set up with push notifications, and advising on their strategies for content. I’ve seen some great strategies, and I’ve seen some less great strategies.

So in this post, I want to discuss what those great strategies, these best practices, are, and how you, a developer or marketer, can use them in your app.

Push is important. Push is probably as important or even more important than the rest of your app’s UX. Why?

(Source unknown. I asked. Take with a grain of salt.)

The good thing about notifications is they remind your users that your app is installed. A bad thing about notifications is they remind your users that your app is installed.

Get that touchpoint wrong, and you’ve lost that user, perhaps for life. Usage, feedback and revenue are all gone. Bad push practices can really harm your bottom line.Secondly, it’s important to remember this simple truth:

Push Notifications go to people, not devices.


So here they are, my best practices for push notifications. These can be thought of as four pillars*:

  • When: Make them timely
  • Who: Make them relevant
  • What: Make them precise
  • Tech: Implement them correctly

READ ON TO THE FULL HACKERNOON ARTICLE TO GET THE BEST PRACTICES! 

Leave a Reply

Your email address will not be published. Required fields are marked *