Tag: Google I/O

Highlights

1. All android support library code is moving to the androidx namespace. No more android.support.v4 or android. support.v7 namespaces.
2. Android app bundle to split the app into downloadable modules
3. Navigation library to set up navigation between different activities/fragments.
4. Use WorkMananger for background work – this is an improvement to JobScheduler
5. Major improvements to Android Studio. Most standalone tools were deprecated in favor of adding the same functionality into Android Studio.
6. Major improvements to Android Vitals which in Google Play to learn more about what’s going on with the Android app’s performance.
7. Android P does more profiling to improve code locality for faster execution.

Modern Android Development

1. hierarchy viewer is replaced by ViewTree in Android Studio
2. TraceView is replaced by Systrace in Android Studio
3. Profiler (DDMS) is replaced by Android Profiler in Android Studio
4. Dalvik is replaced by ART
5. Java is replaced by Kotlin as a preferred language
6. Layouts
   1. Absolute Layout – deprecated
   2. Linear Layout – still OK
   3. Frame Layout – still OK
   4. Grid Layout – discouraged
   5. Relative Layout – discouraged
   6. ConstraintLayout – recommended
7. ListView, GridView, and Gallery are deprecated. RecyclerView is recommended with ListAdapter for updations.
8. Platform Fragments (android.app.fragments) are deprecated. Support library fragments are recommended.
9. Single activity app recommended
10. Rather than managing activity lifecycle use Lifecycle to observe state changes
11. Rather than keeping plain data with views, use LiveData to update views automatically. Use ViewModel to deal with screen rotation.
12. Room is recommended in place of SQLite
13. CursorAdapter and AsyncListUtil are discouraged. Use Paging instead with a neat, graceful offline use-case handling trick.
14. Don’t do manual bitmap management. Use Glide, Picasso, or Lottie instead.
15. Between TextureView and SurfaceView, use SurfaceView.
16. Nine patches are discouraged. Use Vector Drawables.
17. Use FusedLocationProviderClient for fetching the device location. Wi-Fi access triangulation is coming to Android P. FusedLocationProvider will eventually add support for that for indoor location tracking.
18. MediaPlayer is discouraged, use ExoPlayer instead. A detailed hands-on presentation on ExoPlayer

Performance

1. 42% of 1-star reviews mention crashes/bugs
2. ANR/crash rate reduces engagement – use StrictMode to catch them early
3. Avoid IPC on the main thread, StrictMode won’t catch the violation, and you would never know what’s happening on the other side of the IPC call which can block the main thread
4. If BroadcastReceiver#onReceive is going to take more than 10 seconds, then call goAsync for background processing and call PendingResult#onFinish() once that’s finished
5. WakeLocks – avoid using them. All except PARTIAL_WAKE_LOCK are deprecated with Android P.
   1. Use FLAG_KEEP_SCREEN_ON for keeping the screen on in an activity
   2. Use WorkMananger for background work
   3. Use AlarmManager for short-interval callback
6. enums are not discouraged anymore. Platform code avoids it but unlike in prior Android versions, the penalty for enums is low now.
7. A good introduction to Android’s display rendering
8. A good introduction to Android’s text handling
9. Text handling issues
   1. Only framework spans can be parceled, don’t mix custom spans with framework spans since only the frameworks will be part of the copied text
   2. After ~250 spans or more, SpannableStringBuilder ends up being more performant than SpannableString since the former internally uses trees.
   3. Metrics affecting spans cause measure-layout-draw calls, while appearance affecting spans cause layout-draw calls, therefore, the former is more expensive.
   4. Text measurement takes a lot of time on the UI thread, consider creating PrecomputedText on the background thread.
   5. android:autoLink = true works via RegEx and has bad performance. Consider using Linkify on the background thread. Android P also supports deep learning-based TextClassifier which is also invoked on the background thread.
10. Testing your app for background restriction – adb shell apps set <package name> RUN_ANY_IN_BACKGROUND ignore # applies background restriction (change “ignore” to “allow” to remove restriction)

Next Billion Users

1. 28% of searches in India are voice searches
2. 2-wheeler mode added to Google Maps
3. Google Tez uses Ultrasound for pairing and sending money to the nearby receiver
4. Files Go – Folder-based hierarchy won’t work for users who have never had a PC before. Therefore, shows photos based on associations like “WhatsApp Images” or “Camera”. Supports P2P file sharing for fast transfers.
5. Design for next billion users – http://design.google/nbu
6. Android Go
   1. 25% of devices in 2018 shipped with <= 1GB RAM (target for Android Go)
   2. Every 6 MB app size reduces the install rate by 1%
   3. India – largest market for Go. The USA – is the second largest market for Go.
   4. 5 seconds cold start goal
   5. Users opt for smaller apk sizes with a lower rating.
   6. The average apk size is 30 MB. Go recommends a 40MB max app size for non-game and 65MB for game apps.

MLKit

1. On-device + cloud APIs. On-device APIs are free.
2. Firebase supports downloading models and even doing A/B testing.
3. Experimental support to convert TensorFlow models to TensorFlow Lite models.

Compiler

1. D8 – new Dexer, now default. Enable/disable via “android.enableD8 = true/false”
2. R8 – new optimizer, now default replacing proguard, still opt-in in 3.2. Enable via android.enableR8 = true

Kotlin – talk can be here

1. Use properties instead of default getters/setters
2. Use data classes to generate equals, hash method, etc.
3. Use default args instead of method overloading
4. Use top-level functions as well as local functions (function inside functions for better encapsulation
5.  Use function extensions to make the code more readable, eg. extend String class with isDigit to be able to later write the code like “1234”.isDigit
6. Use smart casts
7. Use sealed classes for a superclass which should not be extendable beyond the compile-time
8. Use string interpolation in println, eg. println(“name is ${name}”)
9. Use val (read-only values) by default, only use var (read-write variable) when there is a strong reason
10. Declare lambda functions as inline to remove the cost of having an extra class
11. Use co-routines via async instead of creating new threads
12. Use suspend + async to convert callbacks into more readable synchronously written code