Push notifications allow apps to send information directly to a user’s device without the user having to open the app. Push notifications come in two main categories – push only and fetch. Understanding the difference between push only and fetch notifications can help you optimize your app’s notification strategy.
What are push only notifications?
Push only notifications are sent directly from an app’s server to the user’s device. When the app server has new information to send, it triggers a push notification without waiting for a request from the device. This allows information to be delivered immediately, without any delay.
Some key characteristics of push only notifications:
- Sent directly from app server to device
- No request from device required to trigger
- Delivered instantly when new information is available
- Does not require app to be open
- Works even when device is asleep
Push only notifications are great for time-sensitive alerts that need to be sent right away, like a messaging app sending a new message or a news app sending breaking news. The user gets the information without any delay.
When are push only notifications used?
Here are some examples of when push only notifications may be preferable over fetch notifications:
- Instant messaging apps – New incoming messages need to be delivered immediately. Push only notifications allow this without any delay.
- Ride sharing apps – Alerting a driver that a new ride request is available requires real-time delivery. Push only is optimal.
- News and weather apps – Breaking news and severe weather alerts should be sent to users right away. Push only notifications enable this.
- Calendar apps – Appointment reminders need to pop up at the exact scheduled time. Push only notifications can handle this time precision.
- Social media apps – When another user interacts with your profile or content, push only notifications let you know instantly.
In summary, any application where time-sensitive information needs to be delivered immediately can benefit greatly from push only notifications.
What are the advantages of push only?
Some of the main advantages of using push only notifications include:
- Real-time delivery – Information is sent instantly to devices when available.
- Works with app closed – Notifications can still be delivered even if the app is not currently open.
- Greater urgency – The instant delivery highlights the urgency of the information for users.
- Better user experience – Timely notifications keep users updated and engaged with relevant information.
- Higher open rates – Push only notifications often see higher open rates than fetch notifications.
- More control – App developers can send notifications precisely when needed.
What are the disadvantages of push only?
There are also some potential downsides to keep in mind with push only notifications:
- Overwhelming users – Too many notifications could frustrate users and lead them to disable notifications.
- Draining device battery – Frequent notifications may drain battery life faster than periodic fetch notifications.
- Data usage – Push notifications use data, which could limit usefulness for users with capped or limited data plans.
- Disruptive – Ill-timed notifications could disrupt users at inconvenient moments.
- App development – Push notifications require more upfront development work compared to fetch notifications.
App developers need to carefully evaluate the user experience to maximize the value of push notifications and avoid potential downsides.
What are fetch notifications?
Fetch notifications take a different approach than push only. With fetch notifications, the device periodically queries the app server looking for new information. If there is new data available, the app server will return it to the device to trigger a notification.
Some key characteristics of fetch notifications:
- Device queries app server on a set interval
- New information returned when available
- Notifications delivered in batches on fetch interval
- Requires app to be open and active to work
Fetch notifications are better suited for non-urgent information that doesn’t need instant delivery. The interval can range from every few minutes to a few times per day depending on use case.
When are fetch notifications used?
Here are some examples of when fetch notifications may work better than push only:
- Productivity apps – Periodic notifications giving task reminders or status updates.
- Smart home apps – Updates like cleaning complete or package delivered don’t need instant push delivery.
- Retail/eCommerce apps – New sales or deals can be batched and sent every few hours.
- Games – Daily rewards or unlock notifications often work fine on a fetch interval.
- Social media – Likes and comments on posts can be fetched every so often rather than instantly pushed.
In general, any non-urgent notifications that provide value to users but don’t require millisecond delivery speeds are good candidates for fetch notifications.
What are the advantages of fetch?
Some of the advantages that make fetch notifications a good choice in many situations include:
- Less disruptive – Batches less frequent notifications rather than constant interruptions.
- Improved efficiency – Allows one request to retrieve multiple notifications at once.
- Works with poor connectivity – Will deliver notifications when connection available.
- Lower data usage – Fetching notifications in batches uses less data.
- Conserves battery life – Not constantly waking device for push notifications.
For non-urgent content, fetch notifications provide a lighter, more efficient way to keep users informed.
What are the disadvantages of fetch?
There are also tradeoffs to consider when using fetch instead of push only notifications:
- Delays delivery – Users won’t get notifications immediately since delivery happens in batches.
- Requires app to be open – Fetch only works when app is active, not in background.
- More complex – Fetch requires device and server to sync up on intervals.
- Higher dropout – If users don’t open app frequently, they may miss notifications.
- Lower urgency – Batching notifications reduces the feeling of importance.
The delayed delivery and dependence on the app being active makes fetch better suited for secondary content instead of critical alerts.
Conclusion
To summarize the key differences:
- Push only notifications are sent immediately when triggered by the app server.
- Fetch notifications are requested by the device and delivered in batches on intervals.
- Push only is optimal for time-sensitive, urgent content.
- Fetch works better for non-urgent updates that don’t require instant delivery.
The right notification strategy depends on the specifics of the app and use case. Both push only and fetch notifications can play an important role in keeping users engaged. Understanding the strengths and limitations of each approach allows developers to select the best option for their needs.