Android Performance Patterns: Invalidations, Layouts, and Performance

Views are the backbone of your Android Activity, but have you ever really understood how much updating the visual properties of a view affects your performance? In order to hit the middle ground between performance and flexibility, Android’s UI Toolkit must execute a number of stages to prepare data before rendering it to the screen. So every time you change one of those views, this pipeline has to spin up, and start doing work again.

In this video, +Colt McAnlis introduces the required…


  1. I am including a layout twice in another layout . So on changing orientation , whatever is contained in one include also gets populated in another include.

  2. Why did you position an annotation at the bottom of the video? It's too easy to accidentally click the youtube clip controls instead. No need to present more proof Google has no idea what it's doing when it comes to user interface design. đŸ™‚

  3. I remember that calling invalidate(Rect) is better than calling invalidate. Is this true? If so, where can I read about it?

Leave a Reply

Your email address will not be published. Required fields are marked *