I got tired of Google Messages mixing my OTPs, bank alerts, and promo spam into one cluttered inbox. So I built my own.
Msgs is an open-source Android SMS client I've been developing in Flutter. No AI, no cloud — everything is parsed on-device using pattern matching and regex.
What's wrong with Google Messages?
Google Messages is polished, but its inbox is a mess if you get a lot of transactional SMS. OTPs, bank debits, and promotional spam all land in the same place. You have to hunt for what matters. Their "categories" tab exists but feels like an afterthought — and it doesn't give you any visual context for your transactions.
What Msgs does differently
🔑 OTP copying from notification
When an OTP arrives, Msgs detects the code and the service name instantly. You can copy it directly from the notification — no need to open the app or the message thread.💳 Transactions shown separately
Bank credits and debits are extracted and displayed as visual summary cards — amount, account ending, and type (debit/credit) at a glance. Not buried in a thread with 200 other bank messages.📢 Promotional messages are blocked
Promo SMS never reaches your main inbox. Messages filters them out automatically so your inbox only shows what matters.
No AI involved
Everything is done with on-device pattern matching. Fast, private, and it works offline. Your messages never leave your phone.
Material You design
Messages follows Material 3 with full dynamic color support — it picks up your wallpaper colors and adapts the entire UI. Light and dark mode included.
Tech behind it
Flutter with BLoC state management
Isar Database for fast local indexing and search
Pattern-based classifier — no ML model, no network calls
Clean feature-driven architecture
Current status
The app is still in active development. SMS reading, OTP detection, transaction cards, and chat all work. MMS is coming next.
⭐ If this sounds useful, check out the repo and drop a star:
👉 Github Repo
Top comments (0)