All applications are different, and we use different development methodologies: cascading model – Waterfall, and flexible – Agile. Whatever you choose, the process of creating a mobile application includes evaluation, analytics, design, development, testing, bug fixing, release, and post-release support. The key difference is in approach. In the cascade model, the product is developed immediately completely.
The first question that the client is interested in: “How much will it cost?”. Next to it: “When will the mobile application be ready?” To answer both questions, Azoft evaluates and draws up a work plan. At this stage, the project manager usually joins the project. He can speak on the part of the customer or the part of the development team. The tasks of the project manager: to coordinate the work of the team and communicate with the customer.
But what does the mysterious word “rating” mean? At this stage, we study the technical documentation. We calculate how long it will take for development and testing. We identify not described scenarios and bottlenecks in the assignment.
Analytics is not always part of the mobile app development process. It happens that clients independently perform business analysis of the application, or come with a ready-made list of requirements. But those applications that have passed this stage from the developer company win – it is analytics that helps the business and developers to achieve a common vision, and based on this, reassess the required work and get a detailed project budget.
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 wireframes, we start visual design. We draw a screen map, graphic elements, a detailed prototype, taking into account various use cases.
At this stage, the UI / UX designer creates static prototypes and, at the request of the client, interactive prototypes of the application. This is how we show how the application will look and what behavior to expect from it, considering the planned features. It all depends on the specific tasks and wishes of the client.
When there is a detailed technical assignment and assessment, the design is ready and the prototype of the mobile application is approved, hardcore begins. The development team writes code to implement the intended behavior of the application and connect the application logic to the back-end, if 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.
At the testament stage, we test TK. In parallel with development, we write test documentation, for example, test cases. When part of the functionality is ready, testing begins. We add all bugs to the bug reporting system, after fixing 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 behavior meets the test documentation and the client’s requirements.