"You Were Attacked" Push Notifications and Async Retention

The Game That Doesn't Wait for You (By Design)

Persistent servers mean rivals upgrade, sprint, and disrupt while you sleep. That's the fantasy — a live market, not a paused single-player save.

The cost: you can lose ground without knowing. Push notifications exist to close that loop without turning the game into a second job.

This post explains what we notify, what we don't, and why that maps to healthy async retention — for founders playing on iPhone and founders building products.

---

Notify on Consequence, Not on Noise

Good async notifications answer: "Should I open the app now?"

Event	Why push
Disrupt attack received	PvP consequence — defense and revenge timing matter
Investment window opened	Time-limited fundraising decision
Activity ready to collect	Completes timed activity pool loop
Upgrade / research finished	Macro progress unblock

We avoid:

• Hourly "come back" guilt pings
• Every rival action (forty founders × dozens of events = spam)
• Generic re-engagement with no in-world reason

---

Disrupt: "You Were Attacked"

The headline players remember. Someone on your server triggered Disrupt — you took a hit to customers or momentum (not treasury theft — see redistribution rules).

Push creates emotional stakes similar to real competitive markets: a rival moved while you were in a meeting.

Good response path inside the app:

1. Read the public attack log (fair play cooldowns)
2. Check Security department
3. Plan counter-sprint or scout with spy kit

Notification is the hook; strategy is the session.

---

Investment: Term Sheet on Your Board

When MRR crosses a gate, an investment offer may open — angel through exit. Windows expire.

Push mirrors real inbox pressure: decisions have deadlines. Founders who ignore term sheets in life lose deals; founders who ignore windows in-game lose timing advantage on the leaderboard.

Pair notifications with understanding equity dilution before tap-accepting.

---

Activities and Upgrades: Positive Return Triggers

Timed activities and long upgrades are scheduled rewards. A collect notification feels like completion, not interruption — especially when sessions are 10–30 minutes evening windows.

This is product-led retention: the app tells you when your prior decision matured.

---

Permission and Trust

Push only works if users opt in. We treat notification permission like analytics consent — separate concerns:

• Push = gameplay events you asked to hear about
• Analytics = optional product improvement data

If you decline push, the persistent world still runs — you just sync on your schedule. Fair for busy adults.

---

Retention Metrics We Care About

Metric	Healthy signal
Return within 24h of disrupt push	Engagement with PvP loop
Investment push → decision < window	Players read term sheets
Activity collect push → same session	Short loop completion
Uninstall after notification spike	Bad — means spam or betrayal of trust

Design goal: fewer, meaningful pings beat daily arbitrary streak guilt (monetization without ads sets the same trust bar).

---

Founder Lesson for Your Own App

Building Unicorn Rivals taught us:

1. Tie notifications to user-initiated timers (activities, upgrades)
2. Tie notifications to other players' actions that affect you (disrupt)
3. Tie notifications to expiring high-stakes choices (investment)
4. Never notify for vanity (rank changed by one point)

If you're designing async multiplayer or SaaS with long-running jobs, the same rules apply.

---

Feel Async Pressure in a Safe Sandbox

Reading about notification strategy is easier than calibrating it live with angry players.

Unicorn Rivals ships the full async stack — persistent rivals, push on consequence, fair Disrupt limits. Join the waitlist.

---

Questions? hello@unicornrivals.com · Follow the build on X