Severe
Incomplete Flows
Issue: Not all of our buttons were clickable in our Figma prototype, and occasionally pressing the back button would lead to a screen from an entirely separate flow
Solution: Add a “Coming Soon” screen for features that have yet to be implemented, and use Figma conditionals to ensure users navigate between screens as desired. We will run thorough testing on a variety of different paths that the user could take to ensure comprehensiveness.
Lack of Guidance
Issue: Without guidance from Team Moose, it is not clear what the app’s purpose is from the login flow.
Solution: Add instructional screens to the login flow to inform the user about our app’s purpose and what the fish and bowls represent.
Bowl Purpose
Issue: Not clear what the purpose of bowls are.
Solution: Splash screen explaining the purpose of fish and bowls, and how they are related
Fish-Phone Number Association
Issue: Unclear that a fish is associated with a phone number
Solution: Create area in “Create a Fish” screen that allows input of phone number
No Holistic View of Bowls
Issue: Cannot view entire fish bowl and all of its contained fish
Solution: Add a “zoomed out” view of each bowl and make all the contained fish visible
Fish vs Bowl Flow
Issue: When adding a new fish from contacts, the create a fish flow interrupts the bowl creation flow.
Solution: Add conditional headings to fish creation flow to show which bowl the fish is being created for
Moderate
Login vs Sign Up
Issue: Users only have the option to login even if they haven’t made an account
Solution: Create separate sign up and login flows to reduce confusion
Handling Large Bowls
Issue: Swiping through each fish in a bowl one at a time can be cumbersome in larger bowls.
Solution: In future iterations, add the option to search for a particular fish in a bowl. For now, allow users to click a certain fish from the holistic view of the bowl that was discussed earlier.
Trivial
Bowls View UI Preferences
Issue: Some users would have preferred to view all of their bowls at once, rather than having to scroll through and view them one at a time
Solution: Keep scroll view for now, and iterate if users continue to indicate preference for the other option
