Episode 199: Compose performance
Android Developers Backstage
The Cost of Compose
The goal is really to pay what you, what, for what you use, right? One of the examples when we were designing compose that kept coming back was button in text view. When you do text, it does only text and nothing more. And if you add scrolling, then you pay for scrolling. That's why I keep so much cheaper. So we talked a lot about sort of CPU cost. What about memory cost? I think with compose at least, you know, we have modern and or development now. It's a little harder than it used to be too. You're kind of encouraged not to just pass around these objects that point to everything.
00:00
Transcript
Play full episode
Remember Everything You Learn from Podcasts
Save insights instantly, chat with episodes, and build lasting knowledge - all powered by AI.
