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:
- Uncle Bob's Clean Architecture (in London on 26th - 28th November 2018)
- Lightbend Akka for Scala - Expert (in London on 26th - 27th November 2018)
- Scala eXchange London 2018 (in London on 13th - 14th December 2018)
- Alberto Brandolini's DDD Modelling Workshop (in London on 27th February - 1st March 2019)
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.