Modularizing Our Driver App for Android: The Process (Part-2)
Article Summary
The article link appears to be broken or unavailable. This is a 404 error page from Medium, not the actual Gojek engineering article about modularizing their Android driver app.
Unfortunately, I cannot access the content of 'Modularizing Our Driver App for Android: The Process (Part-2)' as the provided URL leads to a Medium 404 page. The article was originally published on Gojek's engineering blog but is no longer accessible at this link.
Key Takeaways
- Article content is unavailable due to broken link
- Original source was Gojek Engineering blog on Medium
- Topic was Android app modularization process
The article cannot be summarized as the content is inaccessible via the provided URL.
About This Article
Gojek's driver app had poor feature organization. Infrastructure code got duplicated across modules, and cyclic dependencies made it hard to scale.
The team set up four logical layers: core, utilities, features, and app. They wrote scripts to automate the modularization work, moving packages, resources, and dependencies in about 5 minutes per task.
Two developers working together extracted 14 feature modules in 2 sprints instead of the planned 2. Manual extraction time dropped from several hours to under 5 minutes per module.