A retail mini-program we work with used to send a blast every Tuesday. Open rate sat at 3% and falling. Then they switched to subscription messages: after a customer placed an order, they asked one question — "want a reminder when it ships?" — and only those who said yes got the nudge. Open rate on those hit 61%. Same audience, opposite result, because the permission flipped from "we decided" to "you decided."

That's the whole difference between push and subscription messages in a mini-program.

How the model actually works

On a phone, a push notification is something an app sends you. In a mini-program, the host mediates. The user grants a one-off or template-scoped permission tied to a real action they just took — an order, a booking, a service request. The host then delivers the message inside its own messaging surface, not as a system notification competing with everything else.

The permission is the product. Because the user opted into this specific message about this specific thing, they actually read it. The blast is gone. The triggered, relevant note is what survives.

What earns the tap

Message typeGets openedGets muted
"Your order shipped"Almost alwaysNever, it's expected
"Table ready in 10 min"Almost alwaysNever, it's timely
"Sale this weekend!"RarelyFast, it's a blast
"We miss you 💔"RarelyFast, it's generic

The pattern is boring and true: messages tied to a thing the user is waiting for win; messages tied to a thing you want them to do lose. The teams that treat subscription messages as a logistics channel — not a marketing channel — build trust that compounds.

Why the host-owned runtime helps

Because the runtime is shared and the messaging surface is the host's, the message renders consistently and the user knows where it came from. There's no sketchy third-party SDK pretending to be a system alert. That native trust is why open rates stay high. A standalone app's push, by contrast, fights notification fatigue that users have already trained themselves to ignore.

The tradeoff and the trap

You don't own the channel. The host sets the rules: how many messages, how often, what templates are allowed. Push past that and you get throttled or muted at the platform level, not just by the user. So the constraint is real, and it's a good one — it forces relevance.

The trap is treating it like email. Teams port their newsletter cadence and wonder why the host flags them. Subscription messages are sparse by design. Send the three a user is waiting for, not the thirty you wish they'd read.

Sources