Dr.Head Mobile Commerce

Buying specialist audio involves more than finding a product: shoppers need to compare evidence, check stock and delivery, choose compatible accessories, and reach expert help. I explored how those decisions could stay connected in a Dr.Head mobile commerce concept.

Organize the store around the buying job

I modeled the journey as discover, narrow, decide, configure, and get help, then assigned those needs to Home, Find, Product, Bag, and Service. This was a design model to test. Keeping search and filters available within those destinations was intended to let shoppers narrow a choice without losing their place.

01 — Mobile commerce concept
Journey problem
Information architecture
Proposed journey and navigation model. The five-device architecture illustration explains the concept; it is not evidence of a shipped app.

Answer the purchase questions before the description

The wireframes made the order of decisions explicit. Product evidence and purchase conditions come before a long description; configuration stays with the product rather than becoming a disconnected step. The category states explore moving deeper into the catalog while retaining a route back to the previous choice.

Decision hierarchy
Discovery navigation
Product configuration
Wireframes and discovery states from the design source, followed by a recomposed presentation of the configuration proposal.

Make the proposal testable

The result is a prototype and the complete presentation shown here, from the opening through the proposed validation questions. It was not shipped or measured. The next step would be task-based testing of navigation, product evaluation, and configuration; the closing slide defines what those sessions should establish.