Upgrade to Pro
— share decks privately, control downloads, hide ads and more …
Speaker Deck
Features
Speaker Deck
PRO
Sign in
Sign up for free
Search
Search
Building Android Infrastructure Teams at Scale
Search
Mohit S
May 05, 2022
Programming
3
270
Building Android Infrastructure Teams at Scale
Mohit S
May 05, 2022
Tweet
Share
More Decks by Mohit S
See All by Mohit S
Guide to Improving Compose Performance
heyitsmohit
0
110
Building Shared UIs across Platforms with Compose
heyitsmohit
1
450
Building Multiplatform Apps with Compose
heyitsmohit
2
390
Building StateFlows with Jetpack Compose
heyitsmohit
6
1.7k
Building Android Testing Infrastructure
heyitsmohit
1
360
Migrating to Kotlin State & Shared Flows
heyitsmohit
1
650
Using Square Workflow for Android & iOS
heyitsmohit
1
350
Strategies for Migrating to Jetpack Compose
heyitsmohit
2
480
Challenges of Building Kotlin Multiplatform Libraries
heyitsmohit
1
380
Other Decks in Programming
See All in Programming
標準ライブラリの動向とイテレータのパフォーマンス
makki_d
3
180
利用者視点で考える、イテレータとの上手な付き合い方
syumai
4
210
いまあるチームにフィットさせる Serverless そして Platform Engineeringへの挑戦 / Serverless Fits the Team You Have and Platform Engineering
seike460
PRO
2
1.2k
CDKを活用した 大規模コンテナ移行 プロジェクトの紹介
yoyoyopg
0
230
sqlcを利用してsqlに型付けを
kamiyam
0
220
CSC305 Lecture 01
javiergs
PRO
1
140
Taking LLMs out of the black box: A practical guide to human-in-the-loop distillation
inesmontani
PRO
3
1.1k
クラウドサービスの 利用コストを削減する技術 - 円安の真南風を感じて -
pyama86
3
230
NEWTにおけるiOS18対応の進め方
ryu1sazae
0
180
XP2024 っていう国際会議に行ってきたよの記 / XP2024 Conference Report
bonotake
4
150
[KR] Server Driven Compose With Firebase
skydoves
1
100
Subclassing, Composition, Python, and You
hynek
3
100
Featured
See All Featured
How to Think Like a Performance Engineer
csswizardry
16
1k
Visualizing Your Data: Incorporating Mongo into Loggly Infrastructure
mongodb
41
9.2k
We Have a Design System, Now What?
morganepeng
49
7.1k
Optimising Largest Contentful Paint
csswizardry
31
2.8k
Imperfection Machines: The Place of Print at Facebook
scottboms
263
13k
Fireside Chat
paigeccino
32
2.9k
Distributed Sagas: A Protocol for Coordinating Microservices
caitiem20
327
21k
Understanding Cognitive Biases in Performance Measurement
bluesmoon
26
1.3k
XXLCSS - How to scale CSS and keep your sanity
sugarenia
246
1.3M
Helping Users Find Their Own Way: Creating Modern Search Experiences
danielanewman
29
2.2k
Fashionably flexible responsive web design (full day workshop)
malarkey
403
65k
CSS Pre-Processors: Stylus, Less & Sass
bermonpainter
355
29k
Transcript
Mohit Sarveiya Building Android Infra Teams at Scale @heyitsmohit
Building Android Infra Teams at Scale • Purpose & Motivations
• How to build an infra team • Best practices
What is an Android Infra Team? • Focuses on Arch,
CI and Tooling • Customers are devs.
Motivations Team Size Complexity
Greenfield Phase • Small team size • Iterate quickly •
Minimal processes
Motivations Team Size Complexity
Scaling Up • Larger team • Developer Experience • Tooling
Scaling Problems • Gradle build setup & build times
Scaling Problems Teams Monorepo
Scaling Problems Monorepo Gradle
Gradle Setup • 100+ Gradle Modules • Gradle Plugins (KAPT)
• Library Dependencies
Scenario • Upgrade Gradle Plugin
Scenario • Upgrade Gradle Plugin • Causes Out of Memory
Exception
Scenario • Upgrade Gradle Plugin • Causes Out of Memory
Exception • Effects whole team (Slows down development)
Motivations for Infra • Need to maintain Gradle setup •
Detect build regression
Scaling Problems • Gradle build setup & build times •
Architecture Fragmentation
Scaling Problems Codebase
Scaling Problems Codebase Legacy code
Arch Fragmentation • Legacy Architecture • Example - MVC/MVP •
Older design patterns
Arch Fragmentation Codebase Legacy code Feature A
Arch Fragmentation Codebase Legacy code Feature A Feature B
Motivations for Infra • Uniform app arch • Specify how
to migrate legacy arch
Building Infra Team
Team Charter • Ownership areas
Ownership Areas • Architecture • Shared Libraries • Build tools
(Gradle, Buck, Basel) • CI
Ownership Areas Team Size Complexity 100+
Ownership Areas Infra Org
Ownership Areas Infra Org CI Arch Dev Ex Build Tools
Teams
Ownership Areas Team Size Complexity 30+
Ownership Areas Infra Org Single Team (CI, Arch, Build Tools)
Teams
Challenges • Diverse skill set
CI • How to build pipelines • Jenkins or CircleCI
• Setting up automation
Challenges • Diverse skill set • Prioritizing
Ownership Areas • Architecture • Shared Libraries • Build tools
(Gradle, Buck, Basel) • CI
Team Charter • Ownership areas • Key Performance Indicators (KPIs)
Key Performance Indicators (KPIs) • Service Level Objectives
Service Level Objectives • Build times • Infra for performance
metrics • Infra for network metrics
Service Level Objectives Codebase Feature A Feature B Feature C
Scenario 9:41 • Scroll performance • Network Latency
Service Level Objectives Platform Monitoring
Team Charter • Ownership areas • Key Performance Indicators (KPIs)
• Objectives and key results
Objectives & Key Results (OKRs) • Top down approach •
Bottom up approach
Objectives & Key Results (OKRs) • Determine important problems to
solve • Prioritize
Team Surveys • Challenges • Build times • Architecture •
Testing
Building Roadmap Team survey OKRs & Priotrize projects Execute
Examples OKRs • Improve local build times by 10% •
Reduce onboarding to 10th commit • Refactor navigation
Team Charter • Ownership areas • Key Performance Indicators (KPIs)
• Objectives and key results
Best Practices
Best practices • Feedback
Acquisitions Feature Teams Infra Team Continous Feedback
Acquisitions Improvement POC Details Serialization Performance Feature Team A Feature
Team B
Planning Review acquisitions Priortrize/Plan Setup Roadmap
Bi-Weekly Updates Feature Teams Infra Team Digests
Bi-Weekly Digests • Project Status • Improvements • Infra Asistance
Example • Improved Gradle build times by 10% • Created
tools to improve dev workflow • Assisted in project
Best practices • Feedback • Expectations
OKRs • Not every OKR can have a metric
OKRs • Not every OKR can have a metric •
Continuous team survey feedback
Best practices • Feedback • Expectations • Setup processes for
using new tech
Introducing New Libraries Request for Comments Proposal
Introducing New Libraries Request for Comments Proposal Reviewed by Infra
Introducing New Libraries Request for Comments Proposal Reviewed by Infra
Approval & Follow up
Best practices • Feedback • Expectations • Setup processes for
infra • Automate best practices
Automate Best Practices • Static Code Analysis • Custom lint
rules
Best practices • Feedback • Expectations • Setup processes •
Automate best practices • Open source libraries
Open source libraries Team B Team A Team C Distribute
ownership
Open source libraries Team B Team A Team C Distribute
ownership SDK
Open Source libraries (Infra ownership) • Gradle tools • Custom
Lint repo • Arch frameworks
Open Source libraries • Prioritize OSS issues in planning •
Setup milestones for releases
Best practices • Feedback • Expectations • Setup processes for
new tech • Automate best practices • Open source libraries
Building Android Infra Teams at Scale • Purpose & Motivations
• How to build an infra team • Best practices
Thank You! www.codingwithmohit.com @heyitsmohit