Please log in to watch this conference skillscast.
Most Android applications consist of one big, monolithic application project. As your application grows this single project can become harder and harder to manage, responsibilities become unclear and build times grow. Marvin will share how you can split up such an Android application into multiple, smaller modules. We will discuss how doing so might change the way you work in your applications codebase and how it can help in setting up clearer interfaces and responsibilities across teams. As modularizing an application changes the way you interact with the build system we will talk about how your build setup and times might change and how different build systems (such as Gradle, Buck and Bazel) interact with multiple modules.
YOU MAY ALSO LIKE:
- Alberto Brandolini's DDD Modelling Workshop (in London on 22nd - 24th January 2018)
- Simon Brown's Software Architecture for Developers Workshop (in London on 29th - 30th January 2018)
- Greg Young's CQRS, Domain Events, Event Sourcing and how to apply DDD (in London on 31st January - 2nd February 2018)
Modularizing Android Applications
Marvin is a Software Engineer working on the Android application at SoundCloud. He wants to make codebases easier to work with, safer and faster to iterate on. Likes staying on the bleeding edge of things by trying new ideas, APIs and libraries in sample projects scattered all over his hard drives and repositories.