Upgrade to Pro — share decks privately, control downloads, hide ads and more …

ScaleUp. Modular Android Development

Ciprian
June 18, 2014
Programming
3
1.1k

ScaleUp. Modular Android Development

Modular Android Application Development

Ciprian

June 18, 2014
Tweet

Other Decks in Programming

See All in Programming
Click-free releases & the making of a CLI app
oheyadam
2
120
NSOutlineView何もわからん:( 前編 / I Don't Understand About NSOutlineView :( Pt. 1
usagimaru
0
340
初めてDefinitelyTypedにPRを出した話
syumai
0
420
受け取る人から提供する人になるということ
little_rubyist
0
250
Modular Monolith Monorepo ～シンプルさを保ちながらmonorepoのメリットを最大化する～
yuisakamoto
5
330
Realtime API 入門
riofujimon
0
150
アジャイルを支えるテストアーキテクチャ設計/Test Architecting for Agile
goyoki
9
3.3k
Remix on Hono on Cloudflare Workers
yusukebe
1
300
エンジニアとして関わる要件と仕様(公開用)
murabayashi
0
310
3 Effective Rules for Using Signals in Angular
manfredsteyer
PRO
0
120
Jakarta EE meets AI
ivargrimstad
0
190
OSSで起業してもうすぐ10年 / Open Source Conference 2024 Shimane
furukawayasuto
0
110

Featured

See All Featured
Docker and Python
trallard
40
3.1k
Stop Working from a Prison Cell
hatefulcrawdad
267
20k
A Tale of Four Properties
chriscoyier
156
23k
Building Adaptive Systems
keathley
38
2.3k
Building Your Own Lightsaber
phodgson
103
6.1k
Gamification - CAS2011
davidbonilla
80
5k
RailsConf & Balkan Ruby 2019: The Past, Present, and Future of Rails at GitHub
eileencodes
131
33k
Building Applications with DynamoDB
mza
90
6.1k
Exploring the Power of Turbo Streams & Action Cable | RailsConf2023
kevinliebholz
27
4.3k
Raft: Consensus for Rubyists
vanstee
136
6.6k
Music & Morning Musume
bryan
46
6.2k
[RailsConf 2023] Rails as a piece of cake
palkan
52
4.9k

Transcript

  1. ScaleUp Modular Android Application Development Ciprian Ursu Android developer @XING

  2. None
  3. None
  4. None
  5. None
  6. None

  7. Scale number of developers/teams working on the App

  8. None
  9. None

  10. UX consistency by reusing Code and custom components.

  11. None

  12. Now what?!?!

  13. Modules

  14. None
  15. None
  16. None

  17. +   +   vs  

  18. Project (in AndroidStudio) == Workspace (in Eclipse)

  19. Module (in AndroidStudio) == Project (in Eclipse)

  20. None

  21. © Alan Cannistraro Engineering Manager @Facebook http://y2u.be/OJ94KqmsxiI

  22. None
  23. None
  24. None
  25. None

  26. URL schemes

  27. URL schemes

  28. But still… it’s weird. What happens with the manifest??

  29. Every module has its own manifest.

  30. Every module has its own manifest. All of them get

    merged at build time.
  31. None
  32. None
  33. None

  34. minSdkVersion from the main module has to be >= the

    lowest of the submodules

  35. Please note! •  You can have conflicts when the manifests

    are merged.

  36. Resources

  37. None

  38. Please note! •  Don’t reuse the names of the resources!!!

    At the end you’ll end up with the wrong layout on the screen!!!

  39. Every module should have its own tests!!!

  40. None
  41. None
  42. None
  43. None

  44. PROs •  Automatic process

  45. PROs •  Automatic process •  The major issues should be

    seen before they reach a big number of users (THAA)

  46. 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

  47. 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

  48. 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

  49. CONs •  It takes longer to deliver to all your

    users

  50. 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

  51. @ursucip   +CiprianUrsu   Ciprian_Ursu