Complexity will set in as you allow users to import, export, and sync data. But based on the great start you have here, I bet you can pull it off.
Data syncing is definitely the next step, will try to keep it simple.
As a fellow web slinger, I recently went down the road of trying to build a simple veggie tracker as a PWA.
I realized pretty quickly that the PWA world still feels like a hacky mess, with weird CSS rules to make it feel more, but never fully, native.
Most of the issues from way back in the pre-App-Store days remain.
For example, double tapping on the screen triggers a zoom, and there's no way to disable it.
After a full week trying to make my PWA not feel clunky, I resorted to making my first native iOS app with the help of chatty G.
It was surprisingly easy. It took two days to build, and because it's native, everything just works.
PWAs as a platform have so much potential, this app being a great example. It's frustrating that developments aren't further along than they are. I'd think Google especially would have interest in supporting such a platform
That can be disabled: https://stackoverflow.com/questions/59732074/disable-double-...
Actually, all of the layout and gesture jank problems in web apps can be fixed, but it does take some effort. I’m tempted to put in the time to open-source a reference for this, but then I cynically wonder if Apple would then find a way to break it. ;)
This a hobby project for now, so I tried to do it in a cheapest way possible, and PWA looked like a good approach, as there is no need to buy developer subscription.
Have you used Swift to develop your IOS app or any cross-platform solution?
I basically did whatever chatgpt told me, which was Swift with UIKit, and Storyboards for the interface design.
Took me a bit to learn some of the conventions and syntax, but they've come a long way in making it much more intuitive for web dev folks.
That's objectively BS and 100 % skill issue on your side. A simple "disable zoom PWA" search on google would definitely give a bunch of sites telling you how to do it. It's super simple, just add a viewport meta tag.
And it doesn't work consistently. Very easy to break it if you double tap on the background and not somewhere in the text, for example.
Thanks for your... encouragement?
Why so aggressive?
@ Mar 03 2024 08:00
# Unit: kg
# Bodyweight: 70
Squat:
40 12r
65 8r 2s
40 12r
Assisted Pull Up:
bw-20 12r
bw-5 6r
bw 2r
It's much more free-form than this, which is a bonus for me and allows me to track metadata such as weight, time of day I'm exercising at, or general mood/feeling about the workout. I can ultimately just take these plain markdown files from the app (I use a basic Android app that visualizes this Markdown[2]), import them and do whatever processing I like in Python.Highly recommended!
Anyway thanks for sharing!
I've been using my own homebrewed toml spec, but since I am more experienced with code than training, I was concerned if it would still work well as I become more experienced. Not sure if I'll use this, but good to see another interpretation of this kind of data!
I've been using the Strong app on my iPhone for over a year as it seems to provide the simplest approach to workout tracking with enough detail without over cluttering the UI.
This solution needs more way exercises, particularly those using barbells, dumbbells, for instance there is no lat pulldown in the upper body section.
The solution needs the ability to add in the weight, sets and reps performed on particular exercises. I should then be able to reorder these exercises as part of the developed routine. Once I created a workout I could seem to create other different workouts, or replace/edit the workout I'd just created.
I think these are core requirements.
Then you can add in other nice to haves like timed rest periods between sets. Statistics around total volume, PB's both in a rep and set.
I implore you to check out the Strong app to see a well built app that is simple, not overly complicated and includes key features.
I use a simple Seinfeld-style habit tracker for mine:
https://play.google.com/store/apps/details?id=org.isoron.uha...
> A web application is considered a PWA if it satisfies the installation criteria, thus can work offline and can be added to the device's home screen
When putting the iPhone in Flight Mode and deactivating WiFi, this site won’t load after it got added to the home screen.
As of owning the data, right now everything is stored in the localstorage of your browser. So you technically own it. There is no way to export it yet though, will be added in future
Just want to point out that its also open source and available on F-Droid.
If I've completed a habit every day for even 10 days, I want my 100%, but this required more than 200 when I used it.
There is no server syncing right now; everything is stored in the local storage of your browser. Current features will remain free. I might add a paid subscription for syncing data between devices in future.
Why does it have to be so complicated?
Entering a workout should not be so difficult. This app requires clicking 5 times to add a workout.