I feel when you push yourself too hard it will make you look less forward to your next workout. Best to end on a good/interesting note similar to how TV episodes do - making you want to come back for more.
I got a prototype of the Lulzbot mini, which I used to print it (and I still have that printer!).
I designed it in a ruby thing that translates things into openscad (crystalscad was the name, but I deprecated it for multiple reasons. There's jenncad in my github repository as its successor, but I didn't have the chance to get it anywhere to stable)
The Google Distance API does not require an API key, but this is something that should be supported for business licenses and per-key quota limit tracking.
Here are the quota limits:
Users of the free API:
100 elements per query.
100 elements per 10 seconds.
2 500 elements per 24 hour period.
Maps for Business customers:
625 elements per query.
1 000 elements per 10 seconds.
100 000 elements per 24 hour period.
It actually might be a good idea to fetch the value fields as well, since that would make conversion to other metrics easier. Thanks for the suggestion.
I do think it would be valuable to fetch the value field, as then the user can format the text however they want - for example, I may want to say "96 minutes" instead of "1 hour 36 minutes".
Additionally, it's much easier to compare two values (e.g. if one wanted to compare distances between X and Y versus X and Z).