Appreciate the transparency about the AI-assisted development. Your concerns about code quality are valid, but you're overthinking it. We've all shipped worse code that we wrote ourselves.The real win here is that you listened to feedback and made it verifiable. That's what the privacy-conscious Android community needed. The fact that it already works well in production is a bonus.

Good for you.

FWIW, I suspect there isn't a single programmer you admire that hasn't looked back on moments in their career and cringed at some of their own code.

In some ways, I think it is the hurdle that Linus overcame as an undergraduate that I admire the most. Just putting it out there. This is code. Look at it. It might not amount to anything, but who dares wins.

Very proud of you for doing this! I think attitudes around vibe-coded software have been changing a lot over those past two months. Not just on a single axis of "accepted" vs. "rejected" but evolving along many axes. Thank you for helping Android users customize their digital environment.

I would gladly pay a dollar in the official store to get this app, even knowing it can be downloaded for free from GitHub

Hi

I’m not an Android user, but props to you for taking the feedback onboard and doing this, Anuj. Lot of respect for you. In an era of eroded privacy, intrusive notifications, and enshittification you’ve done a genuinely positive and helpful thing to allow ordinary users to fight back.

And, yes, some people will criticise code quality but (a) if those people aren’t actively contributing to the product then you should ignore them, and (b) I suspect the complainers will largely be drowned out by the many who will support your decision.

You certainly aren’t the only highly experienced engineer vibe-coding their way through a problem - I’m leaning very heavily on Claude, and somewhat on ChatGPT, at the startup I’m working on at the moment.

Thank you, Anuj!

I started doing all my projects as open source from the beginning The problem isn’t “well then they won’t pay” there tons of coders and open source users who would gladly save time and energy with paid hosted version this is what I offer potential customers that’s not even the hard part the hard part is and always will be marketing and sales and distribution

Shame is a good instinct here.

Android does, at the level of "Allow notifications from app X" and "Block notifications from app X".

DoNotNotify gives granularity and rules (which a specific app may have chosen not to implement).

For example:

    "Allow <budget airline app X> to display notifications of gate changes"
    "Block <budget airline app X> from displaying advertising notifications"

I assume this allows more granularity. Many apps avoid you blocking their marketing by not using the notification categories system. It's all or nothing. This app would presumably allow me to differentiate between the two if it can't be done with notification categories.

It does, but this appears to have a lot more granularity. You don't always want to block an entire app, sometimes you just want to block some of the notifications from a specific app.

undefined

This is what drove me to uninstall Facebook, twitter, etc. I use their websites if I occasionally want to visit. I don't want notifications hooking me into my phone.

You're right - the app sandbox model in iOS prevents inter-app communication of notifications, and there is no iOS equivalent to the Android ListenerNotificationService API.

It should be able to, unless they are using Live Update [0] notifications.

[0] https://developer.android.com/develop/ui/views/notifications...

The NotificationListenerService.

It has genuine use-cases such as this DoNotNotify app, but could easily be misused - e.g. malware intercepting a wallet OTP notification and forwarding it to the attacker.

Access to the API is controlled by a specific permission which users have to explicitly enable in "Special app access".

https://developer.android.com/reference/android/service/noti...

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.

...

Is this for real, like do you really not see the difference? Not tryingto be snarky or sth, just struggle to comprehend this.

You compare apples to oranges here. From a short look at the provided link, i guess it doesn'tcompare at all because it's something completely different?

Link you provided seems to be Samsung or OneUI only, integrated with Good Lock. This seems to collect and present notifications together with the ability to search. Does not seem to be open source.

DoNotNotify allows you to restrict apps to only sending you certain kinds of notifications.

They could supplement each other but you can't compare them as far as i'm concerned.