141–150 of 231 posts
Earlier quoted context omitted.
What's the point in "privacy friendly" if you're backing up to google?
"privacy friendly" does not mean not relying on any service at all. Its about understanding when and where your privacy is respected. If the user is already using a Google Account for the app (you need a google account to officially download apps from the Play store), they are okay with minimal use of the Google account. Google might be evil in its ways but the google app data is far different than sharing your perso…
I'm using an unofficial Google Play client, Aurora Store, which can use anonymous accounts instead of your own account.
Anyway, giving the user an option to backup data in Google is better than no option at all, although I'd also add a simple export to file, too.
Earlier quoted context omitted.
Thanks! The backup feature is already on my roadmap to offer it as an optional feature - but since you can manually import and export your data, it's not a high priority yet. F-Droid may be an option - but for now the project is not open source. so I think that's not possible
I'd argue that it's a falsehood to call a closed source application privacy friendly.
Great idea, especially since many popular cycle tracking apps have a bad rep of sharing data eagerly with Facebook and other entities. One thing though: I know it's popular in these apps to show the cycle as a "clock face", but if you think about it, this is a weird representation, because of the variations in cycle lengths (of natural cycles not changed by contraceptive hormones). So, if one cycle is 26 days long an…
> many popular cycle tracking apps have a bad rep of sharing data eagerly with Facebook and other entities Many no longer have a choice as to whether to turn their data over to law enforcement who may use it to deny lifesaving medical care. (Florida briefly tried to make reporting periods mandatory for student athletes, too, but that fortunately failed)
Earlier quoted context omitted.
What's the point in "privacy friendly" if you're backing up to google?
"privacy friendly" does not mean not relying on any service at all. Its about understanding when and where your privacy is respected. If the user is already using a Google Account for the app (you need a google account to officially download apps from the Play store), they are okay with minimal use of the Google account. Google might be evil in its ways but the google app data is far different than sharing your perso…
Then you certainly shouldn't be using Google (or any third party service that isn't encrypting customer data in an end-to-end way) for this, as Google is subject to law enforcement requests and right wing states have already tried to use this to access healthcare data. The whole point of this app seems to be to prevent that.
Earlier quoted context omitted.
I'd argue that it's a falsehood to call a closed source application privacy friendly.
You would? How?
Earlier quoted context omitted.
In-app purchases: You can buy another theme if you want. There is no need to do that - the whole functionality is available anyway. I thought it would be nice to at least have the opportunity to make some money from it... I haven't thought about open-sourcing it... Maybe I'll think about it...
Making additional themes be in-app purchases seems like a reasonable way of funding the project. You might want to specifically say in the app description in the store what the in-app purchases are. I was kind of suspicious until I saw this explanation. "Free on F-Droid, $3 on the Play Store" is another approach I've seen (e.g., Conversations and DAV5x).
Earlier quoted context omitted.
> you'd get a lot of mileage out of open sourcing it I’m not sure. Maintaining an open source project requires even more time than a closed source project. You can have a community-oriented closed source project, too. > and doubling down on the privacy / local storage angle Yeah!
There's a difference between open sourcing and "maintaining an open source project". Realistically most open source android apps do not receive many, if any, contributions from outsiders. Being open source does however signal the app isn't likely to become a paid shitfest.