Here’s a scary stat for anyone interested in building a mobile app: according to TechCrunch, 79% of mobile users will try an app a second time if the user experience is less than optimal, but this number plummets to 16% after users try the app one more time! What does this mean? It means users have a REALLY low tolerance for buggy apps, so you better get it right the first time. Luckily, prototyping is a tried and tested method for making sure your app is on track in terms of UI/UX from the very start.
Prototyping involves creating a wireframe or skeleton, in order to establish the flow and function of your app. For example, what information should the home screen display? How does a user navigate from one page to another? These are the sorts of things we deal with when prototyping.
Prototyping is not just about design. An often overlooked aspect of prototyping is the integration of business rules into the flow of your application. Normally, there will be set business rules outlined in a contract. (Now, writing a contract that is thorough and works well is an entirely different topic for a different post). Assuming though that your business rules are firmly established, it’s important to reflect these rules in your prototype. For example, let’s say that displaying the user’s geo-location is outlined in the business rules. If so, it’s probably a good idea to reflect this in your prototype (this way, it definitely will not get neglected when the app moves into design and development).
Here are some reasons why we’re all about prototyping at USAWeb:
In short, prototyping is a crucial step in mobile app development that can not be skipped. Taking a little time to get your prototype right will help your design and development process immensely – and can help ensure that your end product reflects the initial vision for the app.