AI-powered
podcast player
Listen to all your favourite podcasts with AI-powered features
2min chapter
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
Episode notes
Get the Snipd
podcast app
Unlock the knowledge in podcasts with the podcast player of the future.
AI-powered
Discover
highlights
Listen to the best highlights from the podcasts you love and dive into the full episode
Save any
moment
Hear something you like? Tap your headphones to save it with AI-generated key takeaways
Share
& Export
Send highlights to Twitter, WhatsApp or export them to Notion, Readwise & more
AI-powered
podcast player
Listen to all your favourite podcasts with AI-powered features
Discover
highlights
Listen to the best highlights from the podcasts you love and dive into the full episode