Previously if you were to add a new workout, then
add a set for that workout immediately afterwards,
the rest timers would be the default 3:30.
Now, they are the actual value set when creating the
workout.
Previously we were trying to get the max # of sets
from our query on the number of sets completed for today.
This meant if we hadn't completed any sets today, we would
get no result for that workout.
Previously we didn't have a period selector,
so the description was "Best weight per day"
and "Best volume per day". Now that the user
can also select the period (daily, monthly, yearly)
it doesn't make sense to label them as "per day".
I tried out a bunch of formulas as well as
having them as options, and I ended up liking
the Brzycki formula the most.
https://en.wikipedia.org/wiki/One-repetition_maximum#Brzycki
All of them produced similar trends (for me) and the one using
exponents wouldn't work with the SQLite version on android
(can't use POWER function). Also having all the options looked
kind of cluttered. If people ask for it I'll add the other ones
later.
Doesn't feel right to open the reps immediately on
a page with so much content. The keyboard hides some of the
stuff on the bottom. Also I find myself opening a plan up just
to see what's on that day rather than editing right away.
This way reacts better to changing the screen sizes.
I think there was one bug where the fab wouldn't be
precisely at the bottom of the page depending on the
flat list length.
Typically rest timers don't have double digit minutes.
This doesn't prevent that, but will save space 99% of the time,
and in the odd situation where a rest duration is >9 minutes
will be slightly uneven.
Repeating the word sets and rest looks a bit
funny. This way leaves a bit to the imagination,
but looks simpler. If a user doesn't understand what
the description is talking about they will probably
just tap the item to read it.
Brandon Presley