Holds the user’s hammock model and account details
Unless you’re a seasoned hammocker, you may not know some of your gear measurements. For most users, any measurements (hammocks, clothes, furniture, etc) are going to be a high-effort input field.
Maybe the user has to go find their hammock because the measurement is written on the tag. Is it nearby or packed up somewhere? Is this input field worth the effort to go find measurements? UI is the confirmation of input. UX is the acknowledgement of effort.
User interviews highlighted how often a hammock would hold varying weight throughout its lifetime. Even though a single input field for ‘weight’ meets the requirements, the actual steps a user would go through to fill in that field accurately may not be as easy.
Wireframes are useful as a birds-eye-view of a system, and as a reference document for states and flows. Though, as testing and development proceed, wireframes can quickly fall out of sync with the evolving design.
For user testing an augmented reality experience, marker-based prototypes are quick and effective, even if the final product is markerless.
Wtih this user test, I am going to prep a grove with AR markers, each attached to the trunk of a tree as a representation of a hang point. Users will be provided with a mobile prototype on their phones that is set to scan any markers that match their hammock model.
This test focuses on the core functionality of the app: selecting hammock spots.