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
Honoをフロントエンドで使う 3つのやり方
yusukebe
7
3.2k
Honoとフロントエンドの 型安全性について
yodaka
7
1.2k
SwiftUIで単方向アーキテクチャを導入して得られた成果
takuyaosawa
0
270
Ruby on cygwin 2025-02
fd0
0
140
GoとPHPのインターフェイスの違い
shimabox
2
180
Pythonでもちょっとリッチな見た目のアプリを設計してみる
ueponx
1
550
Formの複雑さに立ち向かう
bmthd
1
840
Writing documentation can be fun with plugin system
okuramasafumi
0
120
Immutable ActiveRecord
megane42
0
140
TokyoR116_BeginnersSession1_環境構築
kotatyamtema
0
110
Bedrock Agentsレスポンス解析によるAgentのOps
licux
3
840
CNCF Project の作者が考えている OSS の運営
utam0k
6
710
Featured
See All Featured
Testing 201, or: Great Expectations
jmmastey
42
7.2k
Refactoring Trust on Your Teams (GOTO; Chicago 2020)
rmw
33
2.8k
How to train your dragon (web standard)
notwaldorf
91
5.8k
Building Adaptive Systems
keathley
40
2.4k
Save Time (by Creating Custom Rails Generators)
garrettdimon
PRO
29
1k
Thoughts on Productivity
jonyablonski
69
4.5k
A Tale of Four Properties
chriscoyier
158
23k
Site-Speed That Sticks
csswizardry
4
380
Being A Developer After 40
akosma
89
590k
GitHub's CSS Performance
jonrohan
1030
460k
Building an army of robots
kneath
303
45k
Making Projects Easy
brettharned
116
6k
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