About NotiWeave

A phone gets hundreds of notifications a day from a dozen apps, and Android treats every one of them as disposable: swipe it away and it is gone, and the built-in history keeps a day at most. Meanwhile the one setting most people actually want — a sound that tells you who it is before you look — exists in a handful of messaging apps and nowhere else.

NotiWeave started as a fix for both. It reads notifications only from the apps you enable, keeps them as a thread per sender so a conversation reads as a conversation, and lets any sender, app or rule have its own tone or looping ringtone. Everything else it does — the Notifications panel, blocking, App Lock, backup, themes — grew out of using it every day.

NotiWeave is designed and built by Rizwan Ahmad, an independent Android developer, and published on Google Play under Vianex. There is no data business behind it: nothing the app captures is sold, shared or analysed by anyone, and there is no NotiWeave server for it to be sent to. The blog and the support inbox are run by the same developer.

• Your notifications are yours. They are kept in private storage on your phone that no other app can open. No account, no NotiWeave server, and no syncing you did not ask for — the only copy that ever leaves is a backup you set up yourself.
• You choose what is read. Apps opt in one at a time. Banking and finance apps, and Android’s own system apps, are never listed, and their notifications are dropped the moment they arrive.
• Say what it can’t do. It can only save what arrives after it is set up, it cannot reach back in time, and it is Android-only. The guides on the blog say so too.
• Nothing hidden in the fine print. The privacy policy says in plain words what uses the internet, and why.

NotiWeave is a React Native app with a native Android notification listener. Capture, threading, sound rules and the call ringtone run in native code on the device; the JavaScript side is the interface. Everything is stored in a private database in the app’s own storage, which Android walls off from every other app. The one permission it needs is Notification Access — Android’s single mechanism for reading another app’s notifications — and the explainer on the blog describes exactly what that grants and what it doesn’t.

Questions, bug reports, feature ideas or press: notiweave@gmail.com. The support page covers set-up and the common fixes, and the social links in the footer go to the same place.