mochadwi / android-etalase-app

Test clean Architecture

Etalase app

Feature

• local-storage dengan Room
• menggunakan view-model dan live-data
• Hit API di background process dengan work-manager
• Mengimplementasikan kotlin-coroutines
• arsitektur berbasis offline-first
• format commit dengan git-karma
• Use modular approach per-feature
• Add use case / interactor
• Add mapper / transformation prefer to this template I used to build

Nice to have:

• mengimplementasikan navigation component dari jetpack
• menggunakan dagger koin

Instruction

• Buat sebuah aplikasi untuk menampilkan list of post
• Dan membuat post baru yang bersumber dari API: https://jsonplaceholder.typicode.com/.
• Aplikasi harus mengacu pada paradigma offline-first

Tech Stack

• Git
  • Git karma convention used for git commit message
• CI / CD
  • Using Travis
• Kotlin
  • with idiom style: Extension
  • Refactor (!!) marks with safety-call (?)
  • Custom set/getter
• Kotlinx Serialization
  • Used to replace GSON
  • Kotlinx is reflection-less, support many data types
  • Easy to use for retrofit. E.g: @QueryMap, using NetworkExt#QueryParam.toQueryMap without building map (key, value) one by one
• Coroutine
  • Couroutine adapter for retrofit to use Deferred return type
  • Combined with room to have a suspend function (this only available on latest room 2.1.0-beta01)
  • Mostly used for Retrofit and Room
  • Channel used for search query (send & consumeEach)
• Data Binding
  • I'm trying to implement atomic design ( tag) combined with Data binding powerful features e.g: (custom_error.xml, custom_loading.xml)
  • I also creating a custom Databinding adapter, to customize *View related attributes e.g: setPriceTag, configuring recyclerview, and many more
  • Using ObservableField from Databinding to update and observe value changes without hassle
• Room
  • Configuring sqlite never been this easy with room, no more cursor loader and manual sql statement to have a CRUD
  • FTS4 (Full-text search) used for searching local SQLite data
• Koin
  • Easy injection on unit / ui test
  • injecting viewmodel and sharedViewModel (share same viewmodel along fragment)
• MyPreferenceFactory
  • (with kotlin extension: operator function, prefs reader)
  • No more bloated shared preference set/getter e.g: prefs["key"] = "this-value"
• Building Bundle with ease
  • (with kotlin extension: bundleOf( "key0" bundleTo "val", "key1" bundleTo 100 ))
• Unit / Instrumentation test
  • ./gradlew test to check for the test or
  • ./gradlew clean build to build everything including check for the test
  • Use sharedTest directory for commonly used utils for both test & androidTest
• Better gradle managament (buildSrc directory)
  • Kotlin-DSL used
  • easy search & navigation across dependency management
• AndroidX stable Used
  • room, lifecycle, paging to get latest update and backward compatible
  • one of great feature exist Fragment#getViewLifeCycleOwner() so we don't have to manually configure to destroy the viewmodel
• Android Studio 3.5 Beta1
  • Used to have latest feature from google io 19
  • most important was: Data binding compiler error now arrived, refactor on xml much easier and make sense, no more lags
  • Improved Gradle Sync performance by adjusting for deleted build cache
  • Improved performance and UX with the Layout Editor
  • Incremental annotation processing (kapt and databinding, faster build)
  • Using latest IntelliJ IDEA 2019.1 which is more powerful

Ref

• Still not used the 100% clean arch