This post is intended as a guide that can serve as a basis when considering the design process of a mobile application for either Android or iOS from scratch.
A basic premise that we must consider at all times:
“Designing mobile apps is not just about creating a look and feel awesome, also based on the application to work correctly allowing the user to perform a series of specific tasks within a particular context and according to specific needs.”
PREVIOUS RESEARCH
That said, before grabbing a pen, a mouse or open any tool wireframing my advice is to stop and answer the following questions, indeed, write down your answers and make sure you have all of this information to not lose focus :
- What is the business objective of the mobile application ?.
- Who will be your target audience? Catalógalos, create your individual model for you design.
- What is the main and most common task performed your users? Think of yourself and determines what action is to take place more often.
- How does the competition? What do well and what not? Spend some time researching your competitors, this includes checking out the usual market places, download and try other similar applications and read the reviews and user ratings of competition.
NEXT STEPS
- Become a diagram of the application like a web sitemap it were, there are plenty of online tools that will be useful, but simply write it down.
- Check sketch: for now forget about colors and special effects, just focus on what basic functionality. Start with the most important task to be performed by your users, you’ve given in Question 3. I personally soil myself ready with a common statement as if a user story in question. Each professional has their resources, I am one who or what I write down all or leave it, so like I already know I write sentences like “As a user I would …”. Every sentence is a task that must be reflected in the application. I usually start with the most important and I’m losing priority.
- Find your inspiration: most of the time we perfectly clear how to resolve depending on which user action but others simply or we get stuck or apply a solution we know is much improved. For this reason it is essential that we have 3 or 4 websites of inspiration for us to go in these cases. I usually visit sites like Dribbble , Useryourinterface , Patterntap or Mobile-Patterns . The truth, always work !.
- Forward your wireframe! Surely by now you’ve already started “wireframear” I would not have been avoided but if you have not done it is time to get. You know, Omnigraffle, Photoshop, Illustrator, Proto.io, “pencil and paper” … whatever !. Again, forget the colors and special effects for now;) Focus on the layout, navigation and functionality.
- It tests! Once you have a first test it internally with a companion version that, if possible, is not directly involved / a in the draft development and creation of that application. Someone in marketing, your CEO or someone from another department will suffice. Your goal here is to evaluate the user does well with the application. Find someone as close to your hearing and ask him to perform the most basic tasks. Listen and record. I insist, listen and record. Repeat this step as many times as you think necessary until you see the user moves with relative ease within the application. Use tools like Proto.io , Invision , UXPin or Justinmind . Spending time on this stage will save many problems later, believe me. Do not get the jump, do not take much time and do important discoveries. Maybe your ego will see something touched, will reviews will not like you, my advice is to listen and learn. Teach your partner to provide “constructive criticism” and be humble, is the only way to grow.
- Coloring Time! Now yes! Creativity to power. Open Phostoshop or Illustrator, climbing fidelity of your designs and establishes the necessary interactions. Share them with your computer, collect their feedback and time prepares all required deliverables for the development team can begin to develop. Please follow closely the development process each delivery conducting review it as if you were a QA more.
In the next installment delve more into the most productive processes to create design deliverables to the development team. I’ll do both iOS and Android separately. We’ll see what techniques, processes and tools are useful for everything we need for the design of an app is concerned.
