Build your modern android app from scratch

In this talk, we will be building a composable app from scratch by following up on modern Android development best practices. You’ll leave the presentation with an understanding of the overview of all pieces you need to know for your real-world modern android app development.

Transcript

1. George Town Su Myat Senior Android Developer, Lomotif.SG Building your modern app from scratch
2. What ’ll talk about today 1. Android: overview things need to know before we build our Android app from scratch 2. Importance: the problem with the way we build apps without architecture and why it will tire you out 3. App in Action: let’s get our hands dirty ;)
3. What ’ll talk about today 1. What do we need to know before we build our Android app from scratch a. Android : brief overview b. Language : for developing our apps c. Android Studio : we use it to build apps 2. Hands on simply app in MAD way :)
4. Android Overview
5. Overview of Android 1. Mobile Operating System designed by Google 2. Support many different devices such as Phones/ Tablets/ TVs/ Wears and even Cars. 3. Career Demanding since most use in the world 4. Easy to start, probably easier than you think, plenty of fress courses including google official videos/ codelabs/ gudile will guide you along the way
6. What will you need 1. Powerful computer >= 8GB run 2. Stable Internet connection 3. Download and Install Android Studio 4. Need to have any experience with Android,you can even start learn with programming knowledge in general
7. Download and Install Android Studio https://developer.android.com/studio
8. Go this link if you need more detail setup https://bit.ly/3EgdmQs
9. Importance Why do we need an architecture?
10. The common problem with how we do things 1. Retrofit: REST Api communication 2. Coroutine: managing background work like fetching movie list 3. ViewModel: store UI-related that survive configuration changes such as rotate screen 4. Stateflow: reacts UI when the underlying data has updates 5. Coil: Image Preview
11. 1. All code inside activities/fragments 2. The views unnecessarily complex and massive 3. A small changes have to redo entire views 4. The views aren’t easy to test because of massive size and complexity 5. The code cannot be reused,tested,refactored and easily debugged. The common problem with how we do things
12. Why an architecture will make you life easier 1. Complex tasks are split into simpler tasks and are easier to solve. 2. Smaller objects, less bugs,easier to debug 3. View and UI state holders like ViewModel classes stay neat and classy 4. Readability, Scalability and Portability,Testability 5. if requirements change, usually it’s quite easy to pinpoint exactly you need to change in your code with minimal implications
13. App in Action Let’s make our hands on dirty
14. Example Feature Display latest movies Add to favorite
15. App’s dependencies 1. Retrofit: REST Api communication 2. Coroutine: managing background work like fetching movie list 3. ViewModel: store UI-related that survive configuration changes such as rotate screen 4. Stateflow: reacts UI when the underlying data has updates 5. Coil: Image Preview
16. Architecture Perform Business logic Obtains and exposes app data Data UI
17. Architecture Perform Business logic Obtains and exposes app data Data UI expose data Reactive UI Display data on the screen
18. Architecture Perform Business logic Obtains and exposes app data Data UI expose data Reactive UI Display data on the screen Events UI layer does not pull data, only collect. Data layer handles events, updating underlying data and omitting any changes back.
19. Architecture Perform Business logic Obtains and exposes app data Data UI expose data Reactive UI Display data on the screen Events Reactive UI Single source of truth Unidirectional flow
20. Example Feature Display latest movies Add to favorite
21. Architecture in Example coroutine store movie list Data UI movie list Display move list on screen
22. Architecture in Example coroutine store movie list Data UI movie list Display move list on screen
23. Architecture in Example coroutine store movie list Data UI movie list Display move list on screen Save/ Unsave Favorite Movie
24. Data Layer Repository Data source Obtains data Centralizes data changes
25. Data Layer in Example MovieRepository NetworkDatasource movie list load movie list
26. Data Layer MovieRepository NetworkDatasource movie list load movie list REST API
27. Example Feature Data UI Display Movie list movie list
28. UI Layer Screen ViewModel Hold UI state Display UI State
29. UI state composition MovieRepository MovieViewModel MovieUiState Jetpack Compose
30. UI design LazyColumn Card View
31. Modularization MainActivity MovieViewModel MovieScreen MovieRepository NetworkDatasource app:module UI Data
32. Types of module :app :feature :core Responsible for Bringing features together Single user-facing functionality Single area of common functionality
33. Modules :app :feature:movie :core:data :core:network NetworkDataSource MainActivity MovieScreen, MovieViewModel MoviewRepository
34. Keep learning: goo.gle/android-arch https://github.com/android/ nowinandroid goo.gle/android-local-tests