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
ScaleUp. Modular Android Development
Search
Ciprian
June 18, 2014
Programming
3
1.1k
ScaleUp. Modular Android Development
Modular Android Application Development
Ciprian
June 18, 2014
Tweet
Share
Other Decks in Programming
See All in Programming
Go製Webアプリケーションのエラーとの向き合い方大全、あるいはやっぱりスタックトレース欲しいやん / Kyoto.go #50
utgwkk
6
1.9k
Domain-Driven Transformation
hschwentner
2
1.5k
デフォルトにして至高、RubyMineの大好きな所
ruzia
0
1.1k
Kotlin Multiplatform at Stable and Beyond (Android Makers 2024)
zsmb
0
540
業務ツールとして使うPostman
msys75
0
120
Three ways to use AI on Android: The Good, the Bad and the Ugly
marxallski
0
110
MicrosoftのPlatform Engineeringガイドを読んで実際になにかやってみた
ymd65536
1
530
Elm 0.19.0 Changes
bkuhlmann
0
510
Apache Hive 4 on Treasure Data
ryukobayashi
1
450
Compose-View Interop in Practice (mDevCamp 2024)
stewemetal
0
170
Implementing Design Systems in Swift
seyfoyun
2
490
Exploring the Implementation of “t.Run”, “t.Parallel”, and “t.Cleanup”
akarin
1
140
Featured
See All Featured
In The Pink: A Labor of Love
frogandcode
138
21k
個人開発の失敗を避けるイケてる考え方 / tips for indie hackers
panda_program
66
14k
The Psychology of Web Performance [Beyond Tellerrand 2023]
tammyeverts
15
1.6k
Let's Do A Bunch of Simple Stuff to Make Websites Faster
chriscoyier
501
140k
Product Roadmaps are Hard
iamctodd
45
9.8k
From Idea to $5000 a Month in 5 Months
shpigford
378
45k
No one is an island. Learnings from fostering a developers community.
thoeni
16
2.1k
Build The Right Thing And Hit Your Dates
maggiecrowley
25
2k
Java REST API Framework Comparison - PWX 2021
mraible
PRO
18
7k
Why You Should Never Use an ORM
jnunemaker
PRO
51
8.7k
Into the Great Unknown - MozCon
thekraken
15
1k
How to name files
jennybc
65
93k
Transcript
ScaleUp Modular Android Application Development Ciprian Ursu Android developer @XING
None
None
None
None
None
Scale number of developers/teams working on the App
None
None
UX consistency by reusing Code and custom components.
None
Now what?!?!
Modules
None
None
None
+ + vs
Project (in AndroidStudio) == Workspace (in Eclipse)
Module (in AndroidStudio) == Project (in Eclipse)
None
© Alan Cannistraro Engineering Manager @Facebook http://y2u.be/OJ94KqmsxiI
None
None
None
None
URL schemes
URL schemes
But still… it’s weird. What happens with the manifest??
Every module has its own manifest.
Every module has its own manifest. All of them get
merged at build time.
None
None
None
minSdkVersion from the main module has to be >= the
lowest of the submodules
Please note! • You can have conflicts when the manifests
are merged.
Resources
None
Please note! • Don’t reuse the names of the resources!!!
At the end you’ll end up with the wrong layout on the screen!!!
Every module should have its own tests!!!
None
None
None
None
PROs • Automatic process
PROs • Automatic process • The major issues should be
seen before they reach a big number of users (THAA)
PROs • Automatic process • The major issues should be
seen before they reach a big number of users (THAA) • Some bugs are VERY hard to find in the test environment
PROs • Automatic process • The major issues should be
seen before they reach a big number of users (THAA) • Some bugs are VERY hard to find in the test environment • Get early feedback
PROs • Automatic process • The major issues should be
seen before they reach a big number of users (THAA) • Some bugs are VERY hard to find in the test environment • Get early feedback • Increase the device and screen sizes range
CONs • It takes longer to deliver to all your
users
CONs • It takes longer to deliver to all your
users • Some of the people in the alpha/beta groups might get frustrated about the crashes they encounter
@ursucip +CiprianUrsu Ciprian_Ursu