Push Notifications That Earn Their Place

Krishna — Mon, 26 Oct 2026 15:57:04 +0000

Most apps lose over half their opted-in users within a year. The cause is usually the app itself: wrong timing, generic copy, too many sends.

Before any push, ask one question:

Why would this person be glad their phone buzzed right now?

If the answer is "so our numbers go up", don't send it.

Ask for permission after a win, not at launch Wait for the first real win: a saved result, a completed order. Show your own screen first. Trigger the system prompt only after they tap yes. Name the reason: "Get a message when your order ships", not "Enable notifications". On iOS, use provisional authorization for informational pushes.

Asking at launch gets about 40% opt-in on iOS. Asking after a win gets 70%+.

Give every push a reason that belongs to the reader Noise Their reason We miss you! Come back and explore. Your draft from Tuesday is still here. New features just dropped. The export you asked about is live. 50% off, today only! The jacket you saved dropped to $48. Lead with the specific; only the first few words show on a locked phone. One push, one thing. No exclamation marks or emoji in the title. Never fake urgency or activity.
Reach drifting users at their own hour

Two small jobs replace the campaign blast:

Nightly score: how likely each user is to return on their own (days away, first-week sessions, core action done, past taps).
Hourly send: users below the line, inside their usual open hours, not reached this week. Send the one message that fits. No match, no send.

Bonus: home Wi-Fi in the evening means the user has sat down. Infer it from connection type, open hour and a hashed IP. You don't need the SSID or location permission.

Give every user a budget Rule Value Nudges per user 1 a week, max 2 Gap after any push 24 hours Quiet hours (local) 22:00 to 08:00 After 1 ignored push Wait 2 weeks After 2 ignored in a row Stop nudging Transactional (order shipped, reply received) Unlimited
Get the platform basics right Android: one channel per kind of push ("Order updates", "Reminders"), named for users. Tokens: delete on FCM UNREGISTERED or APNs Unregistered. Re-register on every launch. Deep links: test them from a cold start. Rich media: only when the image is the content. Keep it under 100 KB.
Measure opt-outs, not opens

Open rate flatters you. Track these instead:

Opt-out rate within 7 days of a push: under 0.5%
Opens that lead to the core action: above 30%
Opt-in rate on your own pre-prompt: above 60%
Dead-token rate per send: under 2%

Send fewer pushes and you'll keep more users.

Harnessing the Power of JavaScript's Map Function for Enhanced Development Introduction

Krishna — Tue, 12 Sep 2023 06:55:16 +0000

Introduction

As developers, we often find ourselves working with arrays in JavaScript, manipulating data, and transforming it in various ways to meet the requirements of our applications. The map function in JavaScript is a powerful tool that can simplify and streamline this process. In this blog post, we'll explore the map function and demonstrate how it can be used to enhance your development workflow.

Understanding the map Function
The map function is a built-in method that JavaScript provides for arrays. It allows you to apply a specified function to each element of an array and create a new array with the results. Here's the basic syntax:

const newArray = array.map(callback(element, index, array));

array: The original array you want to iterate through.
callback: A function that is called for each element in the array.
element: The current element being processed.
index (optional): The index of the current element being processed.
array (optional): The array that map was called upon.
Mapping to a New Array
One of the most common use cases for the map function is to create a new array by applying a transformation to each element of the original array. Let's look at a simple example:

const numbers = [1, 2, 3, 4, 5];
const doubledNumbers = numbers.map((number) => number * 2);

console.log(doubledNumbers); // [2, 4, 6, 8, 10]

In this example, we use the map function to double each number in the numbers array, resulting in a new array called doubledNumbers.

Mapping Objects
The map function is not limited to working with simple values like numbers or strings; it can also be used to transform objects. Consider the following example:

const users = [
  { id: 1, name: 'Alice' },
  { id: 2, name: 'Bob' },
  { id: 3, name: 'Charlie' },
];

const userNames = users.map((user) => user.name);

console.log(userNames); // ["Alice", "Bob", "Charlie"]

In this case, we are mapping an array of user objects to an array of their names.

Filtering with map
The map function can also be used to filter an array while mapping it. By returning undefined for elements you want to exclude, you effectively filter out those elements from the resulting array. Here's an example:

const numbers = [1, 2, 3, 4, 5];
const evenNumbers = numbers.map((number) => {
  if (number % 2 === 0) {
    return number;
  }
});

console.log(evenNumbers); // [undefined, 2, undefined, 4, undefined]

In this example, we use the map function to filter out odd numbers while mapping the array. You can then use methods like filter or reduce to further process the filtered array if needed.

Conclusion
The map function is a versatile tool that every JavaScript developer should have in their toolkit. It simplifies the process of transforming and manipulating arrays, making your code more concise and readable.

DEV Community: Krishna

Push Notifications That Earn Their Place

Harnessing the Power of JavaScript's Map Function for Enhanced Development Introduction