Skip to main content
Dev & Tech
kinetic

Releasing. Passed. Everyone knows.

Manual release Pings keep the team current without another status thread.

4 Quick Pingsa grouptap to send
The scene
01

The release owner starts the rollout and taps Releasing. Everyone in the room gets the same concise update.

Releasing
tapped
02

Passed announces the good path. Failed or Rolling back makes the change of plan clear without a paragraph in chat.

Passed
tapped
Failed
tapped
Rolling back
tapped
03

These buttons work manually out of the box. A CI/CD webhook can be connected later if the team wants automated updates.

The vocabulary

4 buttons. A whole language.

Each Ping has its own label, sound, and haptic. This is the four-button setup the template creates. Delivery follows each member’s device, connectivity, and notification settings.

Releasing
zapmedium
Passed
tingsuccess
Failed
punch harderror
Rolling back
zapwarning
Why it lands
  • 01

    Four clear manual states for the release owner.

  • 02

    Each update shows who sent it and when.

  • 03

    Optional CI/CD webhook setup is separate.

  • 04

    A compact status signal for the people following the release.

Keep release status one tap away.

Your version starts the moment you make the room. 30 seconds, free, no card.

Download for iOSDownload for Android