Choose Language:

Our Process

We described the perfect product development process. Our development process minimizes errors and speeds up product creation.


In our company, the process of working on a project begins with interviewing the customer with the help of a brief. The manager determines the project category with which it is necessary to work and sends to the customer a prepared brief that corresponds to the subtleties and details of the desired project category. If necessary, the manager provides all the necessary assistance in filling out the brief.
After receiving the completed brief, the manager together with the technical writer formalizes the terms of reference and translates it into tasks for evaluation by technical specialists.


After the end of the briefing and the formalization of the terms of reference, the interview begins with the design specialist (UI / UX).
The process consists of 10-15 questions that are created specifically for the project, taking into account the specifics, scope, subtleties, wishes. The questions help designers to effectively understand the mechanics of the business, the problems faced by the owners / customers and on the basis of this information to create an ideal model of interaction with users.


Prototype creation

The prototyping of the project (framing) begins after the design team processes the information received in the interview and builds the development concept. The UX Specialist is working on options for creating the most convenient to use schematic web application, using generally accepted standards and rules for creating web applications, relying on global and our most successful cases.
Next, using Mockflow / Figma, frames are created for all future application screens, based on the initial input from you. After the creation of the first version of the prototype, we make it interactive and upload it to the cloud for review. The client makes his edits and wishes, the team again changes to the new wishes and again uploads to the cloud for approval. After the approval of the prototype and each screen separately - the process of creating a design begins.


At this stage, the design team begins the process of creating a design based on the prototype created. Each frame from the prototype is separately drawn in the Figma program, it is brought under the corporate identity and begins to look like the page of the finished web application.
During the development process, the entire board with pages is available in the cloud and the client can make changes on each of the screens.

Architecture Development

Architecture development begins with defining key input parameters, such as:

Server architecture

  • The expected attendance of a product for the first 6 months of operation (unique in day and maximum online)
  • Fault tolerance, how critical is
  • What time is required Uptime
  • Region to host servers

Front-end / Back-end / Mobile Architecture

  • Determine and select the most appropriate Framework (if appropriate)
  • Split business logic into separate independent logic modules.
  • General flowcharts, flowcharts of algorithms

Next, the architect proposes his server architecture options for hosting the services that are necessary for work product that will satisfy customer input parameters. Variants will be provided in the form of flowcharts, as well as visualization of the placement of servers and the links between them and services.


After creating and approving an architectural plan, the teams Back-end / Front-end / Mobile, headed by the technical director, begin the process of creating the application.
The process begins with the configuration:

  • Environment.
  • Docker-based virtualization.
  • Staging servers for product testing.
  • CI systems for automatically running tests and downloading updates to Staging.
  • CI and CD systems for debugging and testing the application.
  • Review systems for Code Review.

Next, development is carried out using the Agile methodology, creating sprints of 1 week duration. In parallel with the development, starting from the second sprint, the testing department is connected to the work, which conducts testing in parallel with the development.


Testing is conducted in parallel to develop, but behind the one sprint. Testers create their own test case for each functional unit, according to which then, when uploading updates, they conduct regression testing of the product by testing it holistically.
All the bugs and inconsistencies found by the testers are indicated by a comment in the JIRA / Trello project management systems, and the task itself is transferred to the “Reopened” mode, which is a signal to the developer that the task needs to be improved.

of the project

After completing the development and testing process, the project enters the finalization stage, in which programmers create documentation on the code written by them, and testers conduct final testing before going out to the world.
After the approval of all the final details and the decision to go online, the specialists begin the process of unloading the product to the combat servers, and the testing department begins a large regression test. Further, we offer the client options for project support under the SLA and continue 24/7 to monitor and refine the product.