Viper Messenger

Posts · August 5, 2026

Two Weeks, Four Releases: How Viper Got Fast, Then Got Unbreakable

TL;DR

The last two weeks were the fastest stretch of shipping in Viper's history. Four App Store releases, a full transport migration, and the groundwork for the biggest privacy features we've ever built — landed back to back.

This is what shipped, and why.

1.5.12

Speed. Everywhere.

The performance release. We went after every delay a user can feel.

Viper now launches instantly. Chats and contacts render the moment the app opens — no loading screen, no spinner, no placeholder. The first frame is the real list.

Under that, we replaced the storage layer with a new SQLite engine. Long conversations open instantly now, tab switching is smooth, and memory use is down across the board. Scrolling a thread with thousands of messages no longer asks the disk for permission.

We also rebuilt the weak-network paths for account creation and switching. On a flaky connection, creating a second account or moving between accounts no longer stalls halfway — it completes, or it fails fast and tells you why.

The composer is new: a proper multiline input with refined send, voice, and video buttons. Profile data — username, account address, recovery phrase — loads instantly instead of trickling in. And dozens of stability fixes you'll never see, because the crashes that caused them are gone.

1.5.13

The one-bar war

We tested Viper on terrible networks on purpose. One bar of signal. High latency. Packet loss. The kind of conditions where most apps just spin.

This release made user search and relay message delivery reliable there. Search no longer times out when the radio is gasping. Relay messages arrive instead of silently dropping. If you've ever watched a messenger "sending…" for a minute on a train platform, that's the failure mode we closed.

1.5.14

P2P goes QUIC

Major transport upgrade. Viper's direct device-to-device layer moved to QUIC.

Text, voice messages, video messages, and files now transfer directly between devices over QUIC whenever a direct connection exists. Lower latency, better behavior under packet loss, faster handshakes than the old transport.

RLDP stays supported for backward compatibility. If P2P can't be established — NAT, no relay candidate, asymmetric routing — Viper falls back to relay automatically. And when both peers are online, the relay forwards messages in real time without storing them. Direct when possible, relayed when needed, never parked on a server.

1.5.15

The relay goes QUIC too

The same transport upgrade, applied to relay traffic. Faster message delivery. Faster user search. Much better reliability on slow, high-latency, unstable mobile networks.

With both hops on QUIC — direct P2P and relay — the whole path is modern. There's no legacy leg left in the route a Viper message takes.

First published August 5, 2026 on the old Viper Foundation blog; moved here November 19, 2026. All posts