If the app required payment by giving your name, address, credit card, and more to "Jimmy" (some person you don't know and don't trust) who will be contacting you to collect, and somebody said "I don't know Jimmy and I don't really trust this. I'd prefer to use a trusted method of payment" would you reply, "You just don't want people to make a living!" I would really hope not.
It could be an in-app purchase for themes or something like that. It can be a “thanks for supporting the app” cosmetic badge, completely optional, just there to buy a coffee for the author. But you’re dealbreaking it before you even see it?
In-app purchase != data collection
Also, regarding FOSS alternatives, you should know that FOSS does not mean “free from payment.” It technically doesn’t even mean “free from data collection.” It just means that the source code is available under a free and open source license. FOSS isn’t necessarily “free as in beer” and the FSF explicitly defines it that way. It’s more important that you’re offered the freedoms of the open source license and ability to get the source code. Whether or not you pay is a separate issue entirely.
but yeah, you already have:
- system apps for play service which run all the time and can access all apps' storage.
- all apps can ask the OS for a list of other installed/recently open apps. whats app request that list every minute.
- etc. not going to list all the crap you can use to target individuals on apple and android. there's plenty.
my point is, in the end. apps with purchase option are the least worse from the official stores. chill.
If your issue with this app being posted to HN is the mere existence of the app on the Play Store (including all of the store and the OS’ existing flaws), I don’t see how that’s supposed to be a constructive or useful discussion relevant to this app.
> An in-app purchase is an automatic dealbreaker? Doesn’t that depend on what it actually is?
Hardly unrelated
REALLY? That was blocked on iOS like a decade ago.
More importantly, if privacy centric apps raise the barrier for entry to include licensing fees, then most people are going to choose the "free" alternatives that get paid for by selling their metadata. If you actually care about protecting users' privacy, you should avoid gatekeeping the technology behind a paywall.
There are plenty of Free (as in beer + as in freedom) period trackers out there that I would be happy to donate time and money to help develop. The closed-source for-profit version that demands that I disclose my identity to Google before I get started is dead-in-the water, having failed to be suitable for any purpose than making the developer a bit of cash while pretending to care about women's privacy in a world that wants to imprison them for a miscarriage.
If the goal was to be privacy-centric, it already fails at that for this alone.
And if the goal was to profit off of women's need for privacy-centric period tracking, then there is absolutely no reason not to find a proper FOSS alternative that cares about its users more than making passive income for the developer.