This is an automated archive made by the Lemmit Bot.
The original was posted on /r/selfhosted by /u/drivingLights on 2025-01-15 20:26:06+00:00.
TLDR
Developing a open source self-hostable period tracker with e2e encrypted device syncing and cycle sharing. Any suggestions or input will be huge help!
Why?
Currently most period trackers out there are entirely proprietary. While many make promises that they encrypt your data or wont share it with law enforcement we all know that those promises are often empty. I wont get political but we can agree that privacy especially biological privacy is sacred.
My solution, both server and client, will be open source, transparent and verifiablely end-to-end encrypted. There are already pen source trackers out there (such as Drip) but these also have their own issues.
-
Many are not very feature rich, not as easy to use or unattractive.
-
None that I have seen support device syncing or cycle sharing with friends and partners.
1.0 features
Features that I want stable and ready for the 1.0 release:
-
Basic tracking with both pre-baked symptom logging as well as custom symptoms and notes
-
Cycle predictions
-
Cycle sharing – Allow friends, family or partners to be able to view each-others cycles (similar to Stardust)
-
End-to-end encrypted. The entire app and server are being built from the ground up with encryption and secure sharing in mind.
-
The client will be local first, with connecting to a server simply providing additional features.
Development
The server is being coded in Java and postgresSQL database. The client is being developed in Dart and Flutter with SQLite being used for local data. I’m not very experienced with UI or app development so I am learning Dart/Flutter as I go but intend for everything to be polished and best practice.
This is in very early development aiming for a beta client and server to be out by the end of the year.
Disclosure
Yes I’m a cis man. Most of my inspiration so far has come from my female peers. I know statistically this community is majority male as well but any input on often missing features or something you would like to see in the final product please let me know. Any notes or comments can help, especially where I could potentially have blind spots.