After this lesson you will
- Read a use case with four questions: input, output, dependencies and policy
- Tell a business operation apart from a UI event when naming
- Find where use cases are wired into the app in SharedDomainModule.kt
Duration11 min
DifficultyIntermediate
Use Case: The App's Unit Of Business Logic
Why a short function deserves its own class.
- 01Lesson Goal
- 02Part 1: What Does The "Sign In Use Case" Do?
- 03Part 2: What Is The Use Case Base Class For?
- 04Part 3: Where Are Use Cases Wired?
- 05Part 4: Name It After The Task, Not The UI
- 06Code Reading Path
- 07Bad Smells
- 08Key Takeaways
Topics: mobile-action-pro, clean-architecture
8 sections left in this lessonUnlock all of Mobile Action ProLesson Goal, Part 1: What Does The "Sign In Use Case" Do?, … — plus 114 lessons in this course, source code and checklists.
Unlock Mobile Action ProOne-time payment — lifetime access — 7-day money-back. Already purchased? Sign in