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
290
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
180
Building Shared UIs across Platforms with Compose
heyitsmohit
1
560
Building Multiplatform Apps with Compose
heyitsmohit
2
430
Building StateFlows with Jetpack Compose
heyitsmohit
6
1.7k
Building Android Testing Infrastructure
heyitsmohit
1
400
Migrating to Kotlin State & Shared Flows
heyitsmohit
1
710
Using Square Workflow for Android & iOS
heyitsmohit
1
390
Strategies for Migrating to Jetpack Compose
heyitsmohit
2
510
Challenges of Building Kotlin Multiplatform Libraries
heyitsmohit
1
390
Other Decks in Programming
See All in Programming
Итераторы в Go 1.23: зачем они нужны, как использовать, и насколько они быстрые?
lamodatech
0
1.4k
GitHub CopilotでTypeScriptの コード生成するワザップ
starfish719
26
6k
ドメインイベント増えすぎ問題
h0r15h0
2
570
ESLintプラグインを使用してCDKのセオリーを適用する
yamanashi_ren01
2
250
watsonx.ai Dojo #6 継続的なAIアプリ開発と展開
oniak3ibm
PRO
0
180
最近のVS Codeで気になるニュース 2025/01
74th
1
130
ASP.NET Core の OpenAPIサポート
h455h1
0
120
HTML/CSS超絶浅い説明
yuki0329
0
190
『改訂新版 良いコード/悪いコードで学ぶ設計入門』活用方法−爆速でスキルアップする!効果的な学習アプローチ / effective-learning-of-good-code
minodriven
28
4.2k
ecspresso, ecschedule, lambroll を PipeCDプラグインとして動かしてみた (プロトタイプ) / Running ecspresso, ecschedule, and lambroll as PipeCD Plugins (prototype)
tkikuc
2
1.9k
PHPとAPI Platformで作る本格的なWeb APIアプリケーション(入門編) / phpcon 2024 Intro to API Platform
ttskch
0
390
return文におけるstd::moveについて
onihusube
1
1.4k
Featured
See All Featured
Being A Developer After 40
akosma
89
590k
A Tale of Four Properties
chriscoyier
157
23k
Music & Morning Musume
bryan
46
6.3k
Git: the NoSQL Database
bkeepers
PRO
427
64k
VelocityConf: Rendering Performance Case Studies
addyosmani
327
24k
Statistics for Hackers
jakevdp
797
220k
Bash Introduction
62gerente
610
210k
Product Roadmaps are Hard
iamctodd
PRO
50
11k
YesSQL, Process and Tooling at Scale
rocio
170
14k
Raft: Consensus for Rubyists
vanstee
137
6.7k
GraphQLとの向き合い方2022年版
quramy
44
13k
Cheating the UX When There Is Nothing More to Optimize - PixelPioneers
stephaniewalter
280
13k
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