Re-stitching Plaid with Kotlin
summary
Refactors convert Plaid to Kotlin and Android Architecture Components, replacing tangled code with explicit layers: RemoteDataSource, LocalDataSource, Repository, UseCases, ViewModel, UI. Coroutines become the app backbone with ViewModel-scoped launches and suspension functions returning a sealed Result (Success/Error) so failures are values not thrown exceptions; a top-level safeApiCall wraps try/catch for all network calls. LiveData stays strictly between ViewModel and UI, DataBinding is used, and extension functions plus data class copy simplify transformations and tests.
AI-written summary · about
chapters (8)
- 0:00Intro
- 0:12Plaid overview
- 2:18Architecture
- 4:38Live Data
- 5:38Asynchronous Operations
- 6:41Seal Classes
- 12:56Lambdas
- 14:45Conclusion
related talks
29mShaping Your App's Architecture with Kotlin and Architecture Components
35mShaping your app’s architecture with Kotlin and Architecture Components
39mRefactoring Plaid App – A reactive MVP approach
41mMaking a Kotlin, Architecture Components, Rx and Coroutines sandwich
26mApp Architecture Then and Now: Lessons from the DroidKaigi Conference App History
58mModern Android Development
18mRescuing Old Code with JetPack
42mArchitecture Round Table