From Bob's Screaming Architecture post:

I poked into your example here and it didn't scream "Clean News!" to me. Consider packaging by feature and doing Clean in one vertical slice at that level.

• WebView to url
• Shared toolbar with link to detail

Am I missing something, or is this Flux and not Redux? By this I mean you have a Store created for each ViewModel instead of one Store for the entire application state. Seems misleading.

Add feature so users can share HN threads. Use bottom sheet for intent picking.

• Detail header similar to list item
• Collapsable comments
  • Recursive CommentView

Expected behavior

Navigating to item details should show details for that item

Actual behavior

Navigating to item details shows details for that item and all other subsequent item detail navigations

Steps to reproduce the behavior

• Navigate to item details
• Navigate back
• Navigate to another item's details
• Displays item details of first item

Analysis

Dagger scoping is what allows us to create a singleton of the view model to allow it to survive rotation, however this also prevents new view models from being created for other items. We need another way to manage scopes.