There are two main types of work with mobile apps – redesigning an existing app and creating a new app from scratch.

If we’re talking about redesigning an app, then there’s a lot to start with. There’s analytics, user feedback, and business feedback. It’s possible to plug in usability audit tools and based on the findings, already optimize the design of the mobile app to increase conversions.

Designing an app from scratch requires a very different approach, which consists of several stages.

Gathering information and requirements
Mobile app design starts with gathering information and requirements. In turn, the requirements are divided into 2 types:

  1. user requirements – for whom the application is created, what tasks it should solve, what this product is needed for in terms of the target audience (TA), etc.

2) Business requirements – this is how the business sees the product, what functions it should perform, and how it thinks users should perceive the application. In case it is a startup, additional information is required, from which the mobile app will be built:

What niche will the app fill?
What tasks should the product solve?
How will the mobile app be monetized?
How will the app position itself in the marketplace? What is its unique selling proposition (USP)?
Who are the main competitors?
What are the best practices on the market?

Creating architecture and navigation
At this stage of mobile app design, the main task is to think over the information and navigation architecture, i.e. what elements the product will consist of, what functions must be included and how the user will interact with them. It is worth specifying the complexities of implementation and other technical nuances associated with the design and functionality of the mobile application.

This is also the stage where user scenarios and stories are written, from the first touch to the targeted action, i.e. the application is modeled. Use cases define the necessary functionality and screens for the future application. Next, block diagrams are drawn to visualize these stories and scenarios, and low-detail mock-ups of the mobile app GUI are created.

Prototyping
After the idea is approved and the architecture of the mobile app is discussed, mockups are created – a low-detailed prototype to determine the priority and location of interface elements on the screen, and to provide a convenient location for them to be accessed.

High-level prototypes are discussed within the team and with the client. And because this approach takes a bit of time, they can be quickly tweaked.

Afterwards, detailed, clickable prototypes are created with the necessary dynamics, animations, and microinteractions for user testing.

At the prototyping stage it is worth consulting with the development team to understand which design elements can negatively affect the cost and time of implementing a mobile app, what should be abandoned, or what can be replaced with a simpler but no less effective solution.

Testing a mobile app prototype
The advantage of interactive prototypes is that it is possible to interact with them as with an already existing application. Thus, it is possible to test the interface by going through the user’s path, collect detailed feedback and understand how interesting the product is for the target audience. At this stage of development, you can perform a number of tests to identify the optimal user path.

Mobile app design and development
At this stage, interactive prototypes are given to designers to make the product more engaging, lay the styling, and refine the micro-interactions with the product design in mind. Once the mobile app design is approved, the product is given to the developers.

Content Preparation for Stores
At this stage a description is created for the mobile app and its main functions, and interface pictures are created for the user to see in the App Store or Google Play. Correctly chosen screenshots which show the features and benefits of the app will help increase the installation figures of the app.