My app needs a minimum sdk 19. So at least that would fit. But to be honest: I don't think I'll add those features in the near future.
The mood tracking is already on the feature list. But the one with the tags.... I write it down to evaluate it. Also you can export the data - but that will result in a json file - not a csv
Yeah - you are right. But I like it that I can see how many days are left - even if it's not 100% correct and I get stuck at "5 minutes before 12" because then I see that it can appear every time.
Maybe I'll add an option for another representation... something like the commit graph in github (don't know the name...) That would be nice too.
To compare the cycle length there is an extra statistic section. I want to add a graph there to make the fluctuations more clear.
Do you mean the contributions-in-the-last-year block at the bottom of your user profile? I can see that being a good alternative to the monthly clockface, because it's broken out by weeks and not months. Color intensity might be useful when you get around to tracking things like mood.
I was honestly terrified to post it. I didn’t want to cause you any problems (e.g. if the replies turned into a dumpster fire) or any weirdness (it’s really hard to strike a balance between saying everything you want to, and not being overbearing about it). It’s a relief that the message made it to you and brightened up your day a bit more.
All the best to your family as well — we hope to have two one day too.
I debated saying something like this too because I've had it backfire, but in a way I didn't expect.
My daughter was excited to go to a coding camp with me, until several people (not all at the same time) each stopped to praise her for being a girl, and me for bringing my daughter. Everyone truly had the best of intentions, but the unfortunate impact was it gave her a bunch of attention that she didn't want, and only served to raise her awareness of how few girls there were. It made her feel more like a misfit and an alien. Afer she realized that it wasn't "normal for a girl to do coding," she didn't want to go anymore. That was a hard and heartbreaking lesson for me. I don't know if it's even applicable outside of my circle, but figured I'd mention it in case it's helpful to others who are trying to create a warm/welcome/inclusive environment. Since then I basically just try to "act normal." It's a hard problem.
That! This! Thank you for talking about it and putting it into words. Not only is it applicable, I’ve had so many discussions about it with my wife. Her central theme is "treat us normally; stop making it a big deal" but with the added context of "it sucks that there aren’t many examples of that." So it’s a balance between the two. I told my wife your story and she said yup, that checks out. I wanted to touch on this but couldn’t figure out how to fit it in.
She points out that the thing not to do is to be like "wow, you’re a girl!" and instead showcase examples of women coding. It’s the showcasing part that helps them feel like they belong. She notes that it would be cool if people would just say "this is Ada Lovelace, she was the first programmer" instead of doing the usual thing of saying "the first programmer was a woman". They might seem equivalent to us, but it feels way different to experience, and it’s something that I couldn’t appreciate until a few instances of me feeling out of place as a man. And then I realized that’s how women feel in tech.
That’s also why OP’s example meant so much to me. It was completely casual, which is the only way my daughter might feel like she belongs too.
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
Indeed, I think it used to be doable because I installed an app without source available from F-Droid a few years ago, but I don't believe it is anymore. Would be super cool if you did though! My wife is still using pen and paper to track because of privacy concerns, but my daughter finds this abhorrent and wants to use an app :-D
I agree that it isn’t as easily verifiable that it is privacy-respecting without the source code but that’s a couple steps from saying that it is “a falsehood” to say it is.
What made me wonder about it is that this is very specific wording that indicates that they proactively know the author is lying, when it would be very easy to instead say something along the lines of what you said, that it is too hard to verify without access to the source code.
I agree that the language used wasn’t perfect, but… If a claim is not verifiable, it can only be taken on faith. Same as all the existing apps in the category that this one aims to replace. Is there a better word we can use to describe this sort of situation?
I can’t think of one specific word to swap out for “falsehood,” it would be better to just replace the whole phrase. Various things have been bounced around here in the discussion. I’d go with something like “without the source code, unfortunately that can’t be verified.” This is a better phrase all around. It describes the actual problem. And it isn’t unnecessarily accusatory.
I think that isn’t it, because it would be easy to say something like “we can’t verify the claim that it is privacy respecting so we should assume otherwise.” Which is a totally reasonable position to take.
I think it is important to be specific, clear, and to have evidence if one wants to call somebody a liar, though.
Or maybe it is something else, it could be interesting if they have some other definition of “privacy respecting” that precludes closed source apps, for example. That is, to “respect privacy” could be understood to actually be to provide users with verifiable evidence that their private info isn’t compromised. I think this isn’t the conventional definition definition of privacy respecting but I’m definitely ready to be pulled on-side if anybody starts pushing it.
Not really, not anymore. Many apps are now using certificate pinning to make it impossible for the user to to modify the trust store. This means that unless it is open source, it is very difficult for people to verify, even when they know very well what they are doing.
Yes you could, although the bar is still a lot higher than if it's open source. You will have to fully re-test all possible paths in the app every time a new release is made if it's closed source. If it's open, you just need to look at the git log.
Plus if there is one legitimate network call, then this strategy is out since you can't know what that request contains. OP using in-app purchases, so I'm willing to be there's at least one network call in there.
If there is no network access permission at all, then I think we agree, that's a reasonable guarantee.
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).
You can always pop it on GitHub with no license. You retain copyright, nobody can do anything with it. Would enable users to report bugs there in the Issues area, or you could make a basic GitHub Pages site, or there's a wiki or discussion forum.
If you did add a license, users could submit PRs of bug fixes or new features. If you don't have a lot of users it probably would get very little traffic and so not become burdensome. (And you can always ignore it... Not ideal, but life comes first)
If you care about privacy and want to have some fun with the license idea, you can add an Ethical Source license, so anyone who uses your code has to comply with a code of ethics. (https://ethicalsource.dev/licenses/) Maybe a license that says you cannot use this if you actively work against women's reproductive health/freedoms?
