SShortSingh.
Back to feed

Why most apps lose push notification users, and how to keep them

0
·1 views

Most apps lose more than half of their opted-in users within a year, usually because of poor timing, generic messaging, or sending too often. The guidance is to ask for notification permission after a user has a meaningful success, such as a saved result or completed order, and to explain the specific benefit first. Each message should give a concrete reason tied to the reader, with one message per send and no fake urgency. Teams are advised to limit sends per user, respect quiet hours, and pause after ignored messages, while tracking opt-out rates rather than open rates. The article argues that sending fewer, more relevant notifications helps retain users.

Read the full story at DEV Community

This is an AI-generated summary. ShortSingh links to the original source for the complete article.

Discussion (0)

Log in to join the discussion and vote.

Log in

Related stories

0
ProgrammingHacker News ·

Entire Introduces a Git Forge Designed for Agent-Human Collaboration

A new post on the Entire blog introduces a Git forge aimed at supporting collaboration between AI agents and human developers. The announcement was shared on Hacker News, where it gathered 11 points and no comments at the time of capture. The source material provides only the headline, link, and engagement metrics, so details about the product's features, pricing, or availability are not confirmed here. The blog post at entire.com is the primary reference for further information.

0
ProgrammingHacker News ·

Cohere Blog Flags Concerning Behavior in a Popular Open-Weight AI Model

A post on Cohere's blog raises concerns about the behavior of a popular open-weight AI model, according to a Hacker News listing that drew 20 points and 3 comments. The original article text was not available, so the specific nature of the behavior, the model in question, and the evidence cited could not be confirmed. Readers should consult the original Cohere post for details.

0
ProgrammingDEV Community ·

Why One Developer Switched From WebSockets to SSE for Live Dashboards

While building a Node.js dashboard that needed live updates without page refreshes, the author initially assumed WebSockets were the right tool. On closer analysis, the dashboard only required one-way data flow from server to browser, so the bidirectional capability of WebSockets went unused. Server-Sent Events run over standard HTTP, use the browser's native EventSource API, and avoid the manual lifecycle and heartbeat management that WebSockets demand. The article notes SSE integrates easily with existing proxies and load balancers, benefits from HTTP/2 multiplexing, and handles reconnection natively. The author concludes that protocol choice should follow the direction of data flow rather than update frequency alone.

0
ProgrammingDEV Community ·

Network Latency Could Corrupt Robot Training Data, Researchers Argue

A recent paper introduces K-AoI, a metric that measures how closely a digital twin stays synchronized with the physical scene during remote robot operation. It combines data age with spatial alignment rather than relying on delay alone. The authors argue that remote teleoperation sessions produce recorded demonstrations used to train future autonomous robots, so frames with stale views may be unreliable. The piece also notes that trained human annotators must review such footage frame by frame before it becomes usable training data.