3 Posts getaggt mit "android"

Late last year, Google communicated with us on an observation they had with our App in the Play Store: our Android sessions were being flagged for excessive partial wake lock usage. We did not see significant impact on our build. Battery life wasn't trending in support tickets, and app reviews showed nothing unusual. But the signal was there, and we worked with Google to dig in and fix it.

At the time, we knew something was off. What we didn't know yet was which background workers were responsible, or how wake lock time was distributed across them. Finding out would make Android connectivity more robust and insights delivered more efficiently to members.

🥊 Wake Locks: 1 — WHOOP: 0. Google flags ~15% of sessions. It did not appear to affect production.

At WHOOP, we work on interesting yet challenging features. Unlocking human performance isn’t trivial. We’re also a subscription-based business, which means we strive to consistently deliver new value for our members.

My name is Dan Peluso, and I’m a co-op on WHOOP’s Community Team. We’re responsible for the social page in our app, including all teams, leaderboards, and communications available through this landing page. I joined the team as a Junior Android Developer this July, and immediately began work on the all-new navigation component our Product team wanted to launch by this fall. Today, I’m super excited to talk about our new Android navigation architecture, and some examples of where we’re refactoring.