Currently the table view vs card view contains the same information, Ideally users would have clear use cases, and each view would have a "time and a place" based on those use cases.
Owner
GT
Description
Be consistent about which is the default, and what the different views offer in terms of unique information. "As a user when I see the full list of cover crops I feel confused about what to do next, I expected to get a few reccomendations". CC Selector: As a user I'd prefer hard data as opposed to just a visual scale (others report scale taking up too much room)
AC
Ensure this works well on mobile.
Display how crops are detailed and visualized across tools.
Define what data is best fit within each view
The similar wording between "My List" and "List View" confused users. Refine naming
Rationale
Currently the table view vs card view contains the same information, Ideally users would have clear use cases, and each view would have a "time and a place" based on those use cases.
Owner
Description
Be consistent about which is the default, and what the different views offer in terms of unique information. "As a user when I see the full list of cover crops I feel confused about what to do next, I expected to get a few reccomendations". CC Selector: As a user I'd prefer hard data as opposed to just a visual scale (others report scale taking up too much room)
AC
Issues