739 Like 13 Dislike
As much as we complain about leaking memory, it’s important to know that there some “small” leaks, and some huge, problematic, city-destroying leaks. And in that category sits the ever-so-humble “VIEW” object in your application. As Colt McAnlis describes, leaking VIEW objects can have massive ramifications to the memory and stability of your application… so.. please.. PLEASE don’t do it… Watch more Android Performance Patterns here: http://goo.gl/4ZJkY1 Join the G+ Community here : http://goo.gl/g7mxmI Subscribe to Android Developers: https://goo.gl/88dzea #PERFMATTERS
The Java Language typically suggests that programmers use ITERATORS in order to walk over containers, due to a whole list of very important code stability reasons. That’s all fine and-dandy, but we have to ask if they are performant, as well as easy-to-use. To find the answer Colt McAnlis wrote some code, measured some containers, and presents the information in this video. Watch more Android Performance Patterns here: http://goo.gl/4ZJkY1 Join the G+ Community here: http://goo.gl/g7mxmI Subscribe to the Google Developers channel here: http://goo.gl/mQyv5L
Cow Transporter Truck | Cow Race Water Slides | 3D Nursery Rhymes | Songs For Children | LAC TV LIVE Like , Comments video and Subscribe channel. Thank you. * Subscribe LAC TV FOR KIDS: https://goo.gl/D9Fhx0 LAC TV FOR KIDS
Read the blog post (https://goo.gl/rGH4uJ) for all the details on scheduling background work with JobScheduler, available on Android Lollipop (API 21) and higher. JobScheduler batches jobs together across all apps making it a great choice for conserving battery, reducing overall memory pressure on API 24 and higher, and using JobScheduler means you are automatically aware of Doze and App Standby. Jobs can be persisted across reboots, scheduled to repeat at a set interval, automatically backoff in response to failures, or scheduled with set requirements such as network connectivity or only when the device is idle. Learn about all of the mechanisms available for scheduling jobs in the documentation: https://goo.gl/PKg7u3 #BuildBetterApps #androidn #jobscheduler #battery #adp #background
Let’s say you’ve got some 20 bitmaps being decoded on a worker thread. Well, what happens if your activity is destroyed before that work completes?
In this video Doug Stevenson explains Loaders. A super-helpful class that can give you insight into how the activity lifecycle is changing, so that you can better understand how to address threaded work that might be in flight.
See Android Architecture sample code here: https://goo.gl/MWXVav
Watch more Android Performance Patterns here: http://goo.gl/4ZJkY1
Join the G+ Community here : http://goo.gl/g7mxmI
Subscribe to the Android Developers channel at http://goo.gl/GEh1ds