2
1 Comment

My marketing said 76 banks. The code had 130. I never checked.

I build Masareef, a private expense tracker for Android that reads the payment notification your bank posts on the phone and writes the transaction itself, with the app closed.

The whole pitch rests on one number: how many banks it recognises. Every store listing, every directory submission and every draft press email said 76. I wrote that number once, months ago, and copied it forward without ever looking again.

Last week I generated the list from the source instead of from memory. The registry holds 130 named institutions: 62 Egyptian, 8 Saudi, 6 Emirati, 54 global. I had been underselling the one thing that makes the app worth installing by 54 banks, in two languages, across a Play listing and four directory entries.

The fix was to stop writing the number by hand. A script reads the registry and regenerates the supported-banks page and every paste-ready store description, so the count can only be wrong now if the code is wrong.

Two other things that cost more than they should have.

Android 15 redacts the content of banking notifications. That broke the direct approach, and working around it without falling back to SMS access was the hardest part of the project. Taking the SMS permission would have been easy, and it also means read access to every message on the phone, which is exactly why a lot of people will not install an automatic tracker.

An app update unbinds the notification listener. Android drops the binding on replace and says nothing, so every user who updates silently stops capturing anything. Nothing reports itself. You find out from a support message, or you never find out.

Still early. Free with a Pro tier, Arabic and English, Android only.

If your bank is not on the list, tell me and I will add it. That is genuinely how the list got to 130.

posted toAvatar for product Masareef
Masareef
  1. 1

    The 130-bank correction is a useful lesson in how easily the marketing surface can drift from the actual product.

    Curious whether the bigger concern now is communicating the broader coverage, or making sure users never silently lose the automation after an update.