The gritty truth about app modularization

location_city Melbourne schedule Nov 9th 11:00 - 11:30 AM place L10 Large Room

Have you heard of micro services or micro frontends? This recent trend in the industry is about breaking up monolith apps into multiple smaller components that be more easily managed. Google wants us to modularise our apps but what exactly does this involve and should you actually to do this on your app? I will talk about the dos, the don’t and what they don’t tell you about modularisation in those online articles. You will hear many terms such as scaling, clean architecture when people talk about modularisation but with my approach you don't have to re-architect your app to start your journey towards modularisation.

This talk is a companion to my online article which was published in both issue 374 and on the Noteworthy blog which has over 30K daily active readers. This article attracted more than 2.1K views and resonated with many readers as most online articles only talk about modularisation on simple apps that they rebuilt from scratch.This talk will focus primarily on the technical aspects that i don't cover in my article such as solving common problems like navigation using 3rd party libraries. I will also talk about our unique build archetypes and runners which will help you understand how you run small parts of your app so you significantly speed up your builds.

Modularisation isn’t a sprint it’s more like running a marathon, it’s really long and hard and you are going to feel totally exhausted by the end of it. The tips that i share during this presentation should help you get started on your own modularisation journey.


Outline/Structure of the Talk

This talk is based on this presentation that I prepared for our internal Android Community of practice

This presentation will be modified for this talk to reduce the number of slides.


The why? Reasons to modularise.

A history of modularisation

The 3 steps or stages that you go through to get a fully modularised app. The reality and the effort required at each step or stage

Step 1

Step 2

Step 3

Common issues

  • Navigation
  • Circular dependencies
  • Interfaces
  • Contracts

How to create specialised runners to run a portion of your app.

Explain why merging is so hard and how it will be avoided now.

Show what a modularised app should look like.

Talk about he quantitive benefits - cost savings, developer happiness etc

Learning Outcome

Developers will learn how to approach modularisation on their apps and incrementally add it while also delivering their product features.

Managers will learn about the effort, costs and benefits that modularisation will bring to their app.

Target Audience

Android developers who haven't modularised their app.

Prerequisites for Attendees


schedule Submitted 1 year ago