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
Let's Write a Train Tracking Algorithm
twocentstudios
0
220
ИИ-Агенты в каждый дом – Алексей Порядин, PythoNN
sobolevn
0
150
Pull-Requestの内容を1クリックで動作確認可能にするワークフロー
natmark
2
450
プロダクト開発をAI 1stに変革する〜SaaS is dead時代で生き残るために〜 / AI 1st Product Development
kobakei
0
490
Introducing ReActionView: A new ActionView-Compatible ERB Engine @ Kaigi on Rails 2025, Tokyo, Japan
marcoroth
3
920
株式会社 Sun terras カンパニーデック
sunterras
0
220
CSC509 Lecture 02
javiergs
PRO
0
400
Web フロントエンドエンジニアに開かれる AI Agent プロダクト開発 - Vercel AI SDK を観察して AI Agent と仲良くなろう! #FEC余熱NIGHT
izumin5210
3
380
エンジニアとして高みを目指す、 利益を生み出す設計の考え方 / design-for-profit
minodriven
23
12k
iOSエンジニア向けの英語学習アプリを作る!
yukawashouhei
0
180
Web Components で実現する Hotwire とフロントエンドフレームワークの橋渡し / Bridging with Web Components
da1chi
3
1.7k
プログラミングどうやる? ~テスト駆動開発から学ぶ達人の型~
a_okui
0
190
Featured
See All Featured
Side Projects
sachag
455
43k
The Language of Interfaces
destraynor
162
25k
個人開発の失敗を避けるイケてる考え方 / tips for indie hackers
panda_program
114
20k
[RailsConf 2023 Opening Keynote] The Magic of Rails
eileencodes
31
9.7k
How to Think Like a Performance Engineer
csswizardry
27
2k
Into the Great Unknown - MozCon
thekraken
40
2.1k
Visualizing Your Data: Incorporating Mongo into Loggly Infrastructure
mongodb
48
9.7k
Product Roadmaps are Hard
iamctodd
PRO
54
11k
Build your cross-platform service in a week with App Engine
jlugia
232
18k
Six Lessons from altMBA
skipperchong
28
4k
Optimising Largest Contentful Paint
csswizardry
37
3.4k
Rails Girls Zürich Keynote
gr2m
95
14k
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