Many of my friends use calorie trackers like Lose it! or MyFitnessPal. And I've heard many complaints about them locking basic functionality behind a subscription. The straw that broke the camel's back was not allowing barcode scanning without a sub. I've been looking for a meaty, pun intended, side project to pick up and decided to try to do some good while saving some people money!
-
Built using Tauri in order to use Angular for the GUI and get mobile platform support.
-
Data is stored on-device using SQLite.
-
Initially I'm only targeting Android, I'd love to target iOS too but I don't own any Apple devices to dev+test on.
-
I'd say it's a "late alpha" as of right now. It has most but not all functionality, but has only been tested by me so there are likely small bugs that need to be found.
-
My wife really likes manatees, hence the name.
-
I've commissioned an artist for a logo so that should be coming by February.
Would love to hear people's thoughts! Currently you'd have to build the app yourself, though I do have an item on my to-do list to generate signed APKs via a github action. Mostly I'm just looking to start spreading the word now and hopefully get some good feature requests or bug reports. If you've read this far, thanks for your time!
Edit: I figured out how to generate signed APKs via GitHub so I have a v0.2.0 Pre-Release up. It's already led me to finding out there are some bugs on Samsung phones that don't happen on my Pixel so please submit any issues you encounter! Thank you!
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.
I feel like, even on the Github page (targeted at technically-minded folks), you should still lead with the non-technical differences instead of the technical ones. In other words, change that first paragraph in the README to include the info from your third paragraph here.
Neat! I look forward to giving it a crack.