Improving Productivity while developing in Android

It is important to leverage some available tools and resources in order to improve efficiency and productivity while developing an Android project.
These slides were presented in Medellin Android Meetup on November 2 of 2016 in Medellin, Colombia.

Transcript

1. November 2nd,, 2016 Improving Productivity while developing in Android @MedellinAndroid MeetUp
2. Improving productivity while developing in Android Carlos Daniel Munoz I. - Android Dev at Huge @MedellinAndroid November 2, 2016
3. 1. Developing in Android 2. About the method count 3. Inspections to analyze traces 4. Optimizations 5. Assets 6. Builds 7. Keymaps 8. Libs & plugins Agenda
4. The only way to fast is to go well ( The higher the quality, the faster you go )
5. 5 Developing in Android • It is like waves • How many projects • Continuously learning • A few things I have learned • Working with team members: Code Reviews! Android Labs! • Having proper toolset Resources: • Android Developers Official • Stack Overflow • Medium
6. 6 Method Count • Methods Count • APK method count
7. 7 Inspections • Stheto → Debug → BuildTypes → JS • Leak Canary
8. 8 Assets • Android Asset Studio → Action Bar → App icon → SVG → Nine patch • Material Design Icons • Material Palette → XML → Png
9. 9 Builds • Buck → High performance build tool • Gradle please • Proguard → Optimizing bytecode
10. 10 Emulators • Genymotion ◦ External and fast ◦ Virtualbox ◦ Free ◦ Optimized resources
11. 11 Some optimizations • Merged Manifiest Viewer ◦ This tool will show how our AndroidManifest merges with our project dependencies based on build types, flavors, and variants.
12. 12 Some optimizations • Instant Run ◦ Run/debug ◦ Rerun ◦ Run > Clean and Rerun • JRebel • Build gradle is too slow? → ./gradlew --stop • Measure Execution Time
13. 13 UI optimizing • Pixel Perfect - Youtube • Hierarchy Viewer
14. 14 UI optimizing • Layout Bounds ◦ Developer Options • Surface Updates
15. 15 Give a shit!
16. 16 Other good practices • Crashlytics → Crash reporting solution ◦ Spend less time finding crashes ◦ When app is getting bigger ◦ Dependency in build + API Key + Call in Application/Base Activity class + watch the report → Done! • Keep testing on various OS versions ◦ Min SDK? ◦ Max SDK? ◦ Backgrounds, shadows, SVGs ▪ IN Android Kitkat 4.4.4 no SVGs but a picture • Formatting code for a better reading - Android Square (Code Style) • Lint tool Genymotion :)
17. 17 Keymaps / Shortcuts • Cmd + Shift A (Mega power!) • Commit** • Alt+Enter • Command+Shift+k • Ctrl+Enter (Generate) • Alt+Enter (Suggestions) ** We can map keys combination to a behavior
18. 18 Some Dev libraries & plugins • Picasso or Glide • RxJava for Async Tasks or Keep each async task as a separate class :( • Use ConstraintsLayout to flatten your view hierarchy.* • Use plugins like Parcelable: ◦ Android Studio -> Preferences -> Plugins -> "Parcelable" (Repositori - Install * Currently in beta 2 version
19. ...I’m not the best software developer, I’m a good software developer with good practices...
20. Questions?
21. September 2016 45 Main St #220 BKLN / 718 625 4843 / hugeinc.com