As you can see in the “storytelling” post, some of the elements or actions repeat after a precise pattern. In this post we will explain some of the pattern we will use for making Beethoven’s live better.
- Always-visible tools – Like the name says, Always-Visible Tools are always visible instead of hiding them until the user needs them. We have “Home” and “Help” buttons always there ready to be used in any circumstance.
- Navigation – The user needs to navigate among sections of the application while having clear indication of what section the user is currently looking at.
- Undo – People tend to make mistakes when interacting with applications. Making one mistake can throw away hours of work. Therefore users should have an option to easily undo their actions and get their work back. We have “Backspace” button and the entire “Edit” section of the application built for this.
- Input feedback – The user has entered data into the system and expects to receive feedback on the result of that submission. In our case, the users will have the device vibrating and an audio warning when they made a mistake.
- Display collection – The user has created a collection and wants to share it with other people.
- Direct manipulation – Actions take place with no apparent wait time.
- Edit in place – Offers an editor directly in the place where the user could modify a composition.
- Spring loaded mode – permitting users to change the mode of interaction by pressing a button (“Change” button).