APPLICATION DEVELOPMENT
APPLICATION DEVELOPMENT

prologue

First, the client comes up with the idea of a mobile application. We ask the client to provide us with the terms of reference (TOR), and if he is not there, we will send a brief on the development of the mobile application. Brief helps to prioritize, identify goals and objectives of the application.

00. CHARACTERS

Client - customer of an application and the ideological inspirer;

MDM - application developers;

PM - project manager;

Business Analyst - researcher and keeper of product requirements;

UI/UX designer - creator of an intuitive and attractive interface;

Developer -engineer who writes application code;

Engineer -Application Testing Specialist.

00. CHARACTERS

Client
Customer of an application and the ideological inspirer;

MDM
Application developers;

PM
Project manager;

Business Analyst
Researcher and keeper of product requirements;

UI/UX designer
Creator of an intuitive and attractive interface;

Developer
Engineer who writes application code;

Engineer
Application Testing Specialist.

01. PLANNING & EVALUATIONS

The first question that interests the client: “How much will it cost?” Next to it: “When will the mobile application be ready?” To answer both questions, MDM conducts an assessment and draws up a work plan.

At this point, the project manager usually joins the project. He can speak on the part of the customer or on the part of the development team. The tasks of the project manager: to coordinate the work of the team and communicate with the customer.

02. ANALYTICS

The first question that interests the client: “How much will it cost?” Next to it: “When will the mobile application be ready?” To answer both questions, MDM conducts an assessment and draws up a work plan.

At this point, the project manager usually joins the project. He can speak on the part of the customer or on the part of the development team. The tasks of the project manager: to coordinate the work of the team and communicate with the customer.

03. Application Design

Sometimes customers come with a finished design. If the customer has no design, we create UI / UX from scratch. When the analyst gives the designer the basis of the graphical interface, the wiring frames, we proceed to the visual design. We draw a map of screens, graphic elements, a detailed prototype taking into account various usage scenarios.

At this stage, the UI / UX designer creates static prototypes and, at the request of the client, interactive prototypes of the application. So we show what the application will look like and what behavior to expect from it, taking into account the planned features. It all depends on the specific tasks and wishes of the client.

During design rendering, the application acquires its future look. It is very important to get feedback from a business analyst and a client so that the design fully meets the requirements for the application.

03. Application Design

Sometimes customers come with a finished design. If the customer has no design, we create UI / UX from scratch. When the analyst gives the designer the basis of the graphical interface, the wiring frames, we proceed to the visual design. We draw a map of screens, graphic elements, a detailed prototype taking into account various usage scenarios.

At this stage, the UI / UX designer creates static prototypes and, at the request of the client, interactive prototypes of the application. So we show what the application will look like and what behavior to expect from it, taking into account the planned features. It all depends on the specific tasks and wishes of the client.

During design rendering, the application acquires its future look. It is very important to get feedback from a business analyst and a client so that the design fully meets the requirements for the application.

04. Development

When there is a detailed TK and evaluation, the design is ready and the prototype of the mobile application is approved, hardcorebegins. The development team writes code to implement the planned behavior of the application and connect the application logic with the server side, if one is provided. And also we embody the finished design in the code - we prescribe all the styles and elements of the UI with which the application user interacts.

05. Testing and
bug fixing

MDM QA engineers connect to the project at startup and test as often as possible. This guarantees a high level of quality and helps the client not to inflate the budget.

At the assessment stage, we test TK. In parallel with the development, we are writing test documentation, for example, test cases. When part of the functionality is ready, testing begins. We introduce all the bugs into the bug reporting system, after the correction we check that the bugs were fixed and this did not affect the rest of the functionality. Before the release of the application, we do acceptance testing: we go through the main business cases of the application to make sure that the application’s behavior complies with test documentation and client requirements.

06. Release & SUPPORT

When a series of tests and improvements of the application is completed, and developers, analysts, testers and designers unanimously approve the result, the time comes to add the application to the application store - Apple App Store, Google Play or any other service at the request of the client.

In order for the application to go through the review of the store, the client can contact the developers for help in the release, and can prepare and put the application into the store on their own.