Retention bottleneck in mesh messaging

Mesh messaging apps usually fail less because the radio link stops working, and more because people stop finding them useful every day. FireChat proved that millions will try offline chat in a crisis or at an event, but it shut down in 2018. Serval Mesh’s core code and app repos show their last meaningful activity around 2017. Briar is still maintained, but its Android only footprint and power tradeoffs show how hard it is to turn a clever networking layer into a habit forming consumer product.

• Retention is the real bottleneck. A mesh app only gets more useful when enough nearby people keep it installed, open, and permissioned for Bluetooth or Wi Fi. Once usage falls, the network gets worse for everyone, which makes churn compound fast.
  1 sacra 2 github 3 github
• Maintenance burden is unusually high. These apps sit close to the operating system, radios, battery management, and background process limits, so every Android and iOS update can break discovery, syncing, or reliability. Briar’s manual and issue tracker show how much configuration around Tor, battery, and connectivity has to be managed even in an actively maintained app.
  4 briarproject 6 briarproject 7 briarproject
• The products that persist tend to narrow the use case. Briar stays focused on activists and crisis communications on Android. Bridgefy has shifted toward a developer SDK with Signal based encryption. That is a sign the durable opportunity is often infrastructure or a specific niche, not a broad standalone messenger.
  4 briarproject 8 bridgefy 9 bridgefy

The next winners in mesh messaging are likely to look less like mass market chat apps and more like tightly scoped tools, or embedded connectivity layers inside other products. For Bitchat, the path forward is to turn technical reliability into repeated everyday use, because survival in this category depends on habit density more than novelty.