The rapid prototyping reminded me of the importance humans place on self-built items. I'm much more likely to use something I designed and built myself than a similar device purchased from a store. While my app already employed a certain degree of "building" on the part of the user, it was dancing around the idea. Why not make it the centerpiece?
I've now re-imagined my project as an experience that one might find next to the sales counter in a bike shop. It would be a large touch screen displaying an environment that looks like a bike shop work bench. The user could select from a huge database of products (most likely limited to whatever brands the bike shop carries) and "build" his or her dream bike. The user could first select a frame make and model, "hang" it from the rack, and then work through selecting wheels, saddles, handlebars, components, colors, etc. for the bike. After the user is done, the system would present a document with a picture of the custom ride and the total cost as well as a breakdown of what components cost what. The document could also contain complementary products the shop carries, or other information about services the bike shop offers. The document could be printed off, emailed, or simplified and texted to a user. Here's a rough sketch of the idea:
Next steps involve redesigning my system map, scenarios, and possibly my content map. I'll be able to move forward after I fix what needs to be changed.