# Try a Ping Before You Build a Room

> A new first-use demo lets a roomless user experience the real Ping banner, sound, and haptic before configuring a room, inviting anyone, or granting push permission.

- Published: 2026-08-22
- Author: PingRoom
- Category: Product
- Topics: PingRoom onboarding, sample Ping, push notification demo, first-run experience
- Canonical: https://pingroom.io/blog/try-a-ping-before-you-build-a-room
- Cover image: https://pingroom.io/blog/try-a-ping-before-you-build-a-room.webp
- Cover description: A fingertip sends one Signal Red pulse into a phone while unbuilt room pieces wait behind it.

PingRoom opens with a promise: one tap, everyone knows.

Until now, a new user had to create a room, choose its setup, invite someone, and send the first real Ping before they could feel that promise. Configuration and an invitation came before the moment that explained why either mattered.

The August 20–22 mobile source changes put the Ping first. A roomless user can now tap **Try a Ping** on the first screen and experience an arrival before building anything.

This is a development update about mobile source work. It is not a claim that a new public app version shipped on August 22.

## Let The Ping Arrive First

A walkthrough can describe a Ping. It cannot reproduce the physical certainty of receiving one.

The new first-use card sends a local sample through the same in-app banner used by a real arrival. The device plays the normal room sound and matching haptic. A short delay makes the banner feel like an arrival rather than pressed-state feedback.

The sample is a Ping from **Mom** in **Home** saying **Dinner's ready**. It is one event, not a feature tour or staged dashboard.

The user experiences the [One Tap, Everyone Knows](/blog/one-tap-everyone-knows) promise before interpreting a room, template, member role, or delivery setting.

## A Real Arrival, Kept Local

The demo uses the real banner, sound mapping, and haptic behavior, but it does not pretend to be a delivered push.

The sample delivery is generated on the device. It makes no room, notification, or push API request. No room is created, no history row appears, no second person is invented, and no push permission is required before it can play. Normal product analytics may still record that the sample was played.

The demo shows what a Ping feels like without quietly creating product state.

![A sample Ping moves from a tap through a deliberate gap to a notification tile, tactile rings, and a later permission doorway.](/blog/try-a-ping-before-you-build-a-room-1.webp)

## Permission After Meaning

Asking for notification permission on launch forces someone to decide before seeing what the permission enables.

The sample changes the sequence:

1. The user asks to try a Ping.
2. The banner, sound, and haptic arrive.
3. The banner leaves.
4. Only then may PingRoom present its existing notification primer.

The shared primer still owns the permission checks. It skips the primer when notification permission is already granted and prevents multiple primer presentations in one session.

## Preferences Still Count

The sample follows the device's Ping settings. If sounds are off, it stays quiet. If vibration is off, it does not add a haptic.

The first-use Moonflower illustration animates once and restarts when the sample is replayed. With reduced motion enabled, it holds on a stable authored frame.

## Replay Without Pileup

After the first arrival, the card changes from **Try a Ping** to **That was a Ping** and remains available for replay.

Rapid taps do not stack banners, sounds, or haptics. While one sample is on its way or visible, later taps are ignored. Once the banner is dismissed, the next deliberate tap can play it again.

## Then Build The Room

After the sample, the rest of the first screen has context. A template is no longer an abstract set of four buttons. Creating a room prepares the next arrival. Inviting someone chooses who should receive it.

[Starting as a guest](/blog/start-as-a-guest) already removed the account wall from the first session. **Try a Ping** lets someone experience the product before setting it up.

The first Ping should arrive before the first setup lecture.