Rosie: use case framework
summary
Karumi ships Rosie after 1.5 years of iteration as a concrete app framework focused on testability, scalability and readability, with internal code on GitHub and real reuse across many short‑deadline projects. Implementation details: presenter/passive-view UI, explicit domain use-case task scheduler (synchronous test runner plus threaded implementations), dynamic proxies to avoid nulls, and a repository pattern with memory cache and persister that populates Realm/Retrofit sources. It removes boilerplate, avoids heavy retained instances to prevent leaks, and proves workable in production apps.
AI-written summary · about
chapters (8)
- 0:00Intro
- 9:41UI Framework
- 15:32Memory Leaks
- 16:32Dynamic Proxy
- 18:49Domain Layer
- 28:32Library
- 30:52Dependencies
- 34:22Conclusion
related talks
35mSweet Architecture
30mHighly testable app architecture with Mobius
39mPractical TDD for Android
32mArchitecture at Scale
46mFRP In Practice: Taking a look at Reactive[UI/Cocoa]
35mcomponentization architecture with RxJava + Kotlin
38mArchitecture Agnostic UI Development
31mHanami 2: New Framework, New You
