Guide for the lazy developer

Building an app is a lot of work - from UI to network layer there's many different components that need to be written. Luckily there's thousands of dependencies available to make building Android apps simpler. However, picking the wrong ones can make your work difficult.

This session will take you through how to decide on when to use a dependency, how to pick the right one and how to integrate them to make your work easier, not harder.

Presented at Droidcon Italy 2018
https://www.youtube.com/watch?v=WqtCo5E2xuo

Transcript

1. GUIDE FOR THE LAZY DEVELOPER Working with dependencies Maria Neumayer - @marianeum
2. Write minimum code
3. Write code more efficient
4. Let others write it
5. WHEN use a dependency
6. WHEN WHICH dependency to choose use a dependency
7. WHEN HOW WHICH integrate a dependency dependency to choose use a dependency
8. WHEN? Considering a dependency
9. WHY? Considering a dependency
10. I want to be in control
11. Somebody thought about it
12. Somebody thought about it A LOT
13. Focus on something else
14. Dependencies evolve
15. Shape it together
16. Will it bloat my app?
17. You need control
18. WHEN? Considering a dependency
19. WHEN It makes sense
20. WHICH? Choosing a dependency
21. Paco Did i write it? @pacoworks
22. Use the community
23. Use your team
24. Every app is different
25. Check the license
26. Check the license
27. Check the readme
28. Check pull requests
29. Check pull requests
30. Check issues
31. There will be other priorities
32. Check past releases
33. Be aware of risks
34. Check the code
35. Check the code AND LEARN
36. Check the tests code
37. Check the samples code tests
38. Check the dependencies code tests samples
39. Glide Picasso Fresco
40. Glide Picasso Fresco ~1,000 methods >10,000 methods ~3,000 methods
41. Check the popularity 57,275
42. It’s a team choice
43. WHICH Choosing a dependency ?
44. WHICH works for you EVER
45. HOW? Integrating a dependency
46. implementation 'com.lib:lib:1.0.0' 1.0.0
47. 1.0.0 Major Minor Patch
48. implementation 'com.lib:lib:1.+' !
49. implementation 'com.lib:lib:1.0.0'
50. Keep them up to date
51. ./gradlew dependencyUpdates https://github.com/ben-manes/gradle-versions-plugin Keep them up to date
52. Check the change log
53. implementation 'com.lib:lib:1.0.0' implementation 'com.lib:lib-tool:1.0.0'
54. ext {a libVersion = '1.0.0' }a implementation "com.lib:lib:$libVersion" implementation "com.lib:lib-tool:$libVersion" (lib)
55. ext {a libVersion = '1.0.0' }a implementation "com.lib:lib:$libVersion" implementation "com.lib:lib-tool:$libVersion" (lib)
56. ext {a lib = [ "com.lib:lib:$libVersion", "com.lib:lib-tool:$libVersion" ]a }a implementation(lib)
57. ext {a lib = [ "com.lib:lib:$libVersion", "com.lib:lib-tool:$libVersion" ]a }a implementation(lib)
58. You already know how to use it
59. Add abstraction
60. Add abstraction WHERE IT MAKES SENSE
61. Start small
62. Start small AND IMPROVE
63. Give credit
64. Give credit startActivity(Intent(this, OssLicensesMenuActivity::class.java)) https://developers.google.com/android/guides/opensource
65. Integrating a dependency HOW?
66. it’s safest HOWEVER
67. No choice is final
68. THANK YOU Maria Neumayer - @marianeum