Getting it on F-droid is on the to-do list once I’m confident I don’t need to make any backwards incompatible changes going forward!

This is why getting more people to test is good! On both my phone and my wife’s nothing is cutoff so I haven’t run into these UI issues before.

The g for grams being all over the place is actually a bit intentional. For the nutrients it’s a label that can’t be changed which is why it’s right aligned and grey. Serving amount is just a string so it could be anything. Serving quantity the g is actually a button to convert to different units which is why it looks different.

I understand that the overall UX is probably the weakest part of the app. I’m more of a backend engineer that dabbles in frontend haha

Due to how both Open Food Facts and USDA store data metric is actually the default!

I actually shout out Waistline in the first paragraph of the README haha

On a technical level, the major differences between the two are Waistline uses Cordova and a key value DB while I use Tauri+Angular and SQLite.

On a non-technical level, I think Waistline’s UX is a bit rough around the edges. For example, when adding something to a meal Waistline will add only 1 serving and then I have to go back in and edit that. Manatee Fitness will immediately bring you to the quantity form after selecting the food to make it more seamless.

I absolutely love Waistline and appreciate the project! I just wanted to take my own crack at it with a modern framework and see if I could improve my personal pain points.

The food database is initially loaded with info from the USDA! That covers generic stuff like eggs or milk. Anything new is either added manually or sourced from the Open Food Facts database which is already crowdsourced.

I’m prioritizing Google Play but after that’s settled I’m open to f-droid as well. Most of the people I know that’ll benefit from this app the most wouldn’t know how to even install f-droid.