A solution could be to measure it but not really track / visualize it day to day.
Is it about inducing more exercise? Or is it the timer aspect that it records how long your workout is? (in which case I don’t understand why it’s so much better than a stopwatch?)
For me, and those around me, the fitness feature seems vestigial and has very little impact on actual fitness levels of the individual.
An example here is how I made sure my parents are getting their exercise in by making completing their Move rings and 10K steps every day. This pushes them to take a walk in the evening instead of doom scrolling / watching TV.
Another example - Check trends like resting heart rate to see if my body has fully recovered from covid19, SP02 at night indicating potential sleep apnea etc.
Basically what Whoop is doing with their strap - but minus the subscription model. I know a ton of people who tried the whoop but felt it was extremely pricey and didn't have the accuracy of an apple watch.
I would be happy to pay ~$400-500 up front for hardware that integrates with Apple Health and provides solid, reliable health tracking without a need for a subscription.
And by health/fitness - features expected would be sleep tracking, activity (gps), heart rate, Sp02, skin temperature sensors, fall detection. Then secondarily - additional things like ECG/EKG, apnea, AFib detection
The in-accuracy of some of the devices in the market is why I still choose to remain with my Apple Watch.
This youtube channel may help understand a consumer's perspective on health accuracy - https://www.youtube.com/@TheQuantifiedScientist
With TestContainers - I've perceived that running integration tests / a single test repeatedly locally is extremely slow as the containers are shut down when the java process is killed. This approach allows for this while also allowing to keep it consistent - example, just mount the migrations folder in the start volume of your DB container and you have a like-for-like schema of your prod DB ready for integration tests.
I've found the https://github.com/avast/gradle-docker-compose-plugin/ very useful for this.
Not entirely sure why this story is throwing shade at Google Pay in India, since the service there has been a runaway success. It's a furiously contested space, but GPay came out of nowhere to grab the #1 or #2 spot depending on what metric you use:
https://yourstory.com/2020/12/google-pay-phonepe-upi-market-...
But I agree with the article that while going aggressively mobile-first/only makes a lot of sense in India, it's going to be quite different in a mature market like the US and the transition is going to ruffle a lot of feathers. The biggest sticking point is really how dysfunctional US banking is: in India, thanks to UPI you can pay anybody if you know their phone number, but this is not a thing in the US and that's why you can only do P2P transfers to other GPay users.
For what it's worth, though, I've been using GPay (outside the US) for quite a while now and I've never found myself wishing for a desktop client. P2P payments are almost always to people you're already messaging from your phone or physically interacting with.
From a UX perspective, it has been notoriously slow and is prone to failures. For example, if the transaction could not go through, it remains pending for 3-ish days while Google retries internally. For real-time transactions, like buying groceries from a street vendor, it isn't practical to wait so long to find out - and mostly results in people paying twice for a product.
Aside from marketing gimmicks and usage by vendors, who by the way use a single QR across 5 different UPI vendors, I'm not sure it really is a "runaway success".
Edit:
Another point to note is that GPay (and other vendors like PhonePe) went around sticking their own QR codes on every shop. This meant that if you wanted to pay by UPI at that shop, you had to install GPay.
This prompted NPCI to issue a circular and ensure QR codes were interoperable across UPI apps - but as I've seen, there still remain tons of shops which have only the GPay proprietary QR Code. Ref: https://razorpay.com/blog/npci-circular-on-upi-interoperabil...
Lethargy by vendors to move over to the new QR could also be one of the reasons why these 2 players hold the lions share in the UPI market.
Right now I'm focused on building out a globally distributed API platform. I'm looking for a challenge.
I learn fast.
---
Location: Bangalore, India
Remote: Yes
Willing to relocate: Yes - after the pandemic. Preferably to a country with good healthcare and low/no racial discrimination.
Résumé: [link here](https://bit.ly/3bb15kY)
Technologies: mentioned on my résumé.
Email: mentioned on my résumé.
---
Trying to develop a budget to pay off debts, my partner made this elaborate Excel spreadsheet and the output was that basically she had no spending money and I had very little, until one or both of us got a raise. It was far more austere than either of us were willing to go. So I started over using a different equation for 'fairness', and a different layout because something about her tables was just confusing and messy. When I was done, we had $300 a month of extra spending money between the two of us, despite using the same targets for pay-down, savings and bills.
I spent about 90 minutes poking at her spreadsheet and mine looking for the error and never did find it. I don't know what the right solution is to this sort of problem, at least for non-developers. But if I was skeptical of Excel going in, I was doubly so after that. Especially for something that is going to be used to make decisions that will affect every day of your life.
Everyone who sees me paying for an app (I'm from India) ask me - "why can't you just use excel and do the same thing for free?". Excel sure is powerful, but in real life, your mileage may vary.