![]() ![]() This is especially important when they have internal or off-shore development teams. However, their internal workflow may require a fully-realised prototype. They understand that the additional work will take more time and budget. While I’ve used this approach in the past and generally use the fastest, simplest technique to communicate an interaction, some clients just want it all. I know some of my Lean UX peers are probably asking why not simply demonstrate the full menu depth with a single path and explain the limitations to client. I set myself the challenge of creating a deep, 4-level mobile menu without manually having to create over 20 different menu states. The mobile menu was my second attempt at testing the limits of what is possible with repeaters. ![]() Testing out the repeater functionality on a listing page revealed some limitations. It wasn’t until a tight deadline on a table-based calculator project forced me to hack together a prototype with screenshots that I was determined to master this final Axure functionality.Īs I began to learn more, I realised I might be able to simplify my workflow using repeaters. I mistakenly believed that they were intended exclusively for tabular data. While repeaters were introduced as part of Axure 7 in December 2013, I didn’t start experimenting with them until September 2015. ![]() Before then, it would be worth explaining how I came to develop this menu prototype and when you should use it. Hopefully, this mobile menu tool will immediately save you days of work.īelow I’ll describe how to utilise the off-canvas, mobile menu framework. The project was feature on the Axure Blog. In my research and development time, I created an Axure tool that automatically creates a full mobile menu prototype from spreadsheet data. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |