Mobile Engineering for Scale at GOJEK

Transcript

1. Mobile Engineering for Scale at GOJEK Raditya Gumay @r_adiit
2. Agenda • Mobile App Milestone • Engineering at Scale • Engineering Mantra • Best Practices in Mobile Development
3. Go-Jek 1.0 Call-center for ojek service 01 Mobile App First mobile app was launched 02 More Apps! Incl. growth of Go-Pay into P2P, withdrawal, etc 03 2010 2015 2017 Milestone 04 2018 Even more!
5. I have an idea Engineering at Scale
6. I have an idea I have an idea I have an idea I have an idea I have an idea
7. I have an idea I have an idea I have an idea I have an idea I have an idea
8. *Having lot engineer doesn’t means can speed up features delivery
10. Engineering mantra : ship fast, iterate often, and don't crash
11. 01 02 Coding at scale Releasing to the world
12. 01 Coding at scale
13. Centralize engineer
19. 02 Releasing to the world
21. Another Problems • Semantic Version • Slow gradlew clean build • OnBoarding
22. Semantic Versioning a
23. Semantic Versioning a-core a-core-base
24. Semantic Versioning a-core a-core-base a-analytic a-analytic-core
25. Semantic Versioning
26. Semantic Versioning
27. Semantic Versioning
28. This might be break people, but who?
29. foo foo foo foo
30. Slow build time
31. App Component Common Analytics Common- Android-Test Feature A Feature B Feature C Feature D Feature E Feature F
32. App Component Common Analytics Common- Android-Test Feature A Feature B Feature C Feature D Feature E Feature F
33. App Component Common Analytics Common- Android-Test
34. There are solutions out there…
35. solution # 1: Deal with the pain
36. solution # 2: Sharing nothing
37. solution # 2: Sharing nothing little
38. solution # 3: Monorepo
39. App Component Common Analytics Common- Android-Test Feature A Feature B DI Model Constant Feature C Gojek Module Remote Config Gojek Module Foo Modules Base
41. Clean Architecture Best Practices
42. Test - Always do regression test - UI and Unit test is test behavior not implementation detail
43. Team Above things are useless if team members is not care each other
44. Team - Ask for help - Do discussion - Accept other opinions, don’t defense
45. Reference - Ribs Framework - SOLID Principle - Clean Architecture Reference - Object-Oriented Programming in C# Succinctly by Sander Rossel - Solid Principle by Gaurav Kumar Arora - Java Design Pattern by Vaskaran Sarcar - Clean Code by Robert C. Martin - Effective Java 3rd Edition by Joshua Bloch - Working with legacy code by Michael C. Feathers - Refactoring to Patterns by Joshua Kerievsky - Pragmatic Programmer by Andy Hunt and Dave Thomas Fundamental Android - Android Programming: The Big Nerd Ranch Guide 3rd Edition - Kotlin in Action by Dmitry Jemerov - Kotlin for Android Developers by Antonio Leiva - BDD in Action by John Ferguson Smart Test
46. https://www.slideshare.net/radityagumay/mobile-engineering-at-gojek-scale Slide : https://github.com/radityagumay Github :