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
年間50登壇、単著出版、雑誌寄稿、Podcast出演、YouTube、CM、カンファレンス主催……全部やってみたので面白さ等を比較してみよう / I’ve tried them all, so let’s compare how interesting they are.
nrslib
3
130
Reactive ❤️ Loom: A Forbidden Love Story
franz1981
2
200
ロボットのための工場に灯りは要らない
watany
12
3.2k
今こそ押さえておきたい アマゾンウェブサービス(AWS)の データベースの基礎 おもクラ #6版
satoshi256kbyte
1
210
Claude Codeログ基盤の構築
giginet
PRO
7
3.8k
Nuxt Server Components
wattanx
0
210
Claude Code Skill入門
mayahoney
0
450
AI 開発合宿を通して得た学び
niftycorp
PRO
0
180
Geminiをパートナーに神社DXシステムを個人開発した話(いなめぐDX 開発振り返り)
fujiba
0
120
へんな働き方
yusukebe
6
2.9k
Tamach-sre-3_ANDPAD-shimaison93
mane12yurks38
0
200
我々はなぜ「層」を分けるのか〜「関心の分離」と「抽象化」で手に入れる変更に強いシンプルな設計〜 #phperkaigi / PHPerKaigi 2026
shogogg
2
710
Featured
See All Featured
Evolving SEO for Evolving Search Engines
ryanjones
0
170
How STYLIGHT went responsive
nonsquared
100
6k
The Illustrated Guide to Node.js - THAT Conference 2024
reverentgeek
1
320
Neural Spatial Audio Processing for Sound Field Analysis and Control
skoyamalab
0
240
Measuring & Analyzing Core Web Vitals
bluesmoon
9
800
How to Think Like a Performance Engineer
csswizardry
28
2.5k
Templates, Plugins, & Blocks: Oh My! Creating the theme that thinks of everything
marktimemedia
31
2.7k
Distributed Sagas: A Protocol for Coordinating Microservices
caitiem20
333
22k
The Invisible Side of Design
smashingmag
302
51k
Improving Core Web Vitals using Speculation Rules API
sergeychernyshev
21
1.4k
Building an army of robots
kneath
306
46k
The Anti-SEO Checklist Checklist. Pubcon Cyber Week
ryanjones
0
110
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