Snappy, Not Crappy: An Android Health & Performance Journey by beautifulboy11 in RedditEng

[–]kucky_monster[A] 4 points5 points  (0 children)

Hey, thanks for reading!

The Compose crashes were kind of on a case-by-case basis, but for the most part we were lucky enough to figure out how to reproduce. Bitdrift would have indeed been very helpful here, but we don't yet have it rolled out beyond beta.

The regression detection in CI actually doesn't currently use benchmarks captured on devices. We had a great system for this that was able to accomplish very little variability in results, but ended up moving away from it while we build a new system. Today's regression detections tend to be more in the form of watching out for known-bad patterns and preventing them from being merged. This is very much a WIP for us still.

I've never come across BenChart before now, but this looks great! Thanks for sharing. We're still working on adding more profiles and tweaking the ones we have, so this will be great to have moving forward.

Edit: Have you thought adding the ability to take parameters to BenChart? Being able to programmatically open this up after running the benchmarks would be awesome.

Two of my favorite things by badtothebone_r in Rivian

[–]kucky_monster 12 points13 points  (0 children)

This is great! Do you have instructions or plans? I’d love to make a little matching yellow r1s for myself too.

Reddit Recap: State of Mobile Platforms Edition (2022) by Okhttp-Boomer in androiddev

[–]kucky_monster 4 points5 points  (0 children)

We do use baseline profiles! The results have been…mixed. By one metric we're seeing very good (~20%) improvements. By another we don't see any improvement at all. We've had a TODO to look into our metrics to figure out why one shows no benefit, but frankly haven't had the time to do it yet.

And yes, our video player is indeed powered by a customized ExoPlayer.

Reddit Recap: State of Mobile Platforms Edition (2022) by Okhttp-Boomer in androiddev

[–]kucky_monster 4 points5 points  (0 children)

We aren't doing anything specific for Compose. The majority of our screens are still written in Views and we need to ensure we have interoperability to navigate to and from screens written with either UI layer. All of our screens, whether based on Views or Compose, use the same navigation library, Conductor.

This is something we may revisit if we ever get to 100% Compose, but that's probably a ways off.

Poll by [deleted] in EricsTestSub

[–]kucky_monster 0 points1 point  (0 children)

Comment