The starting point is a notification from an app that you want to create a rule for. So you wait for a notification, then click on it in the "History" tab, and then you can configure the rest from there. It's slightly non-intuitive, but the reason for that flow is that the app needs the package name of the app, which almost nobody will know.
You should still add an IAP to the Play Store build, and make it "paid" even if it has no different features. There are dozens of us who support OSS apps, dozens!
It does have rules for about 25 common apps already built in. I had considered making a feature to 'share' rules with other users of the app, but that would've required Internet access. And as you can see from the comments on this thread, nobody wants an app like this to send data :(
The app requires a very specific permission for this, which it asks for on first launch. It's not even just a popup on which you can tap "Ok" - Android will take you to a special screen from where you need to manually switch on the notifications access for it to work.
iOS doesn't give developers access to other apps' notifications, AFAIK. I'm not an iOS developer though - maybe someone with more knowledge can chime in.
There's an API for notification mirroring, but only in the EU. As you can guess this is a "deprivileging Apple Watch" thing. So there's no generic "filter notifications" ability, it's ONLY for sending notifications to a connected non-Apple smartwatch.
> Have you thought about adding ML-based classification for notifications that are harder to catch with patterns?
Honestly that's a little out my league. The idea did occur to me, but I'm discouraged by the amount of compute required for most ML.
> Also curious about battery impact — how often does it process the notification stream?
The OS sends any new notification to the app (it is a push based approach) automatically. On my own phone, this app currently shows at the bottom of the list in battery usage (<1%).
I would greatly appreciate it, if this was open source :)
Especially since this will be able to read 2FA codes sent by SMS.
(I get that SMS 2FA codes are not perfectly safe to begin with, I personally don't love them either, but they are still used on a bunch of services)
I'm going to join the list of voices requesting open source here. If you're not planning to charge money for this, there are several benefits starting with increased trust.
Mobile apps are a cesspool of user-hostile behavior, and I have a strong preference for not giving closed source apps access to sensitive data.
Putting on my CISO hat, if they release the source, someone else could then create an app, but this time maliciously with said exfiltration of information, and publish it on play with paid ad time.
[0] https://developer.android.com/develop/ui/views/notifications...
reply