Android UI Development - Tips, Tricks, and Techniques from Google's Anrdroid UI Toolkit Team
Why Stack Overflow recommends it
Stack Overflow users link it when answering Android questions about redraw and invalidation, bitmap memory, garbage collection from boxed types, and animation smoothness.
Recommended by 3 people across 4 different months, 2011 to 2015.
What it is
A 2010 Devoxx talk by Google Android UI Toolkit engineers Romain Guy and Chet Haase on building faster, better-looking Android interfaces. It covers avoiding garbage creation, memory leak tips, allocation tracking tools like DDMS, ViewStub and ListView usage, and graphics optimization.
What people said
Recommends Marvin Pinto · 2011-12 · Stack Overflow · on “Android FPS, how to make it smoother?”
Have a look at this [this video] video (around the 34:07 mark) I don't do any animations myself but this might apply to your situation.
Recommends Marvin Pinto · 2012-01 · Stack Overflow · on “Android: How do I circumvent invalidation / redraw of not effected layers?”
Assuming you're using invalidate() on your View , perhaps you can try one of the other [LINK] ones instead? This would theoretically only redraw the affected (dirty) area. void invalidate(Rect dirty) void invalidate(int l, int t, int r, int b) void invalidateDrawable(Drawable drawable) See also this [this video] video (around the 34:07 mark). They have a nice little demo that describes this in detail.
Recommends jtt · 2012-02 · Stack Overflow · on “Android OOM, memory is never released”
This is quite a topic that is kind of hard to tackle, specifically if you keep a reference to your Bitmaps, then you start overloading memory. This is because images are VERY heavy in terms of memory/VM. You should have a look at what Romain Guy says about graphics and Bitmaps and how to handle it. Here: [LINK] [this video] They are lengthy videos, but have lots of good information and some of this includes how to handle this with best practices.
Recommends Daniel F · 2015-03 · Stack Overflow · on “When to use wrapper class and primitive type”
Here's a video from a Google Usergroup Meeting where this specific float vs Float topic is covered in the context of Android's animation framework, mostly regarding Garbage Collection issues [this video] This is presented by the guy working at Google on the animation framework (Chet Haase)
Recommends Daniel F · 2015-03 · Stack Overflow · on “Java: Should I use float or Float?”
Here's a video from a Google Usergroup Meeting where this specific float vs Float topic is covered in the context of Android's animation framework, mostly regarding Garbage Collection issues [this video] This is presented by the guy working at Google on the animation framework (Chet Haase)