We listen to the customer's wishes and ideas and give initial recommendations. If necessary, we sign a non-disclosure agreement and then process the information received. If there are terms of reference, we study them and prepare a list of questions.
At the end of this stage, we need to understand the product idea, the platforms for which the development is intended, the target audience, the business model, and monetization (if any). At this stage, we often involve representatives of the development department to analyze the complexity of the project and the resources required to fulfill the order. As a rule, by the end of this stage, it is possible to formulate approximate prices and approximate deadlines.

Based on the information we received, we proceed to formalize the requirements for project development - our experts work on user stories for each role in the project. This stage involves creating a user flow and Customer Journey Map – how users of the future product will achieve their goals and get value from the product.
User stories are generated in the Jira project management system and submitted to the customer for approval. At this point, the pricing of the project is agreed upon – at a fixed price or hourly. This usually depends on the complexity of the project, its scale, and the customer's grasp of the ultimate goal. In any case, the result of this stage is an agreed terms of reference that is attached to the contract, and a model of financial interaction is approved.

Once the scope of work and complexity of the functionality are determined, the project manager begins to form a team according to the expertise and experience of our specialists. The team is built taking into account both professional skills and the level of communication, speed of decision-making, teamwork, and interaction between different specialists. It is a rather creative process, as it depends on many factors, yet it directly affects the efficiency of work and the success of the result.
Meanwhile, the project charter is being formed, defining all the rules of internal and external communication, the format of reporting to the customer, the customer's representatives involved in the project and their roles, and the frequency and format of status discussions. The product development methodology is chosen depending on the project.

This is where we take into account the customer's wishes regarding the sequence of product releases, as this may involve other activities that are not direct development: advertising and marketing campaigns, press releases, staff training, preparation of packaging for equipment, etc. We need to synchronize all the people involved, including those outside the development team, so the further success of the commercial launch or pre-release depends on proper planning.
At this very moment, with the involvement of the entire development team, we formulate stages and sprints that will be followed by the process of design, coding, testing, and submitting to the client for review. In addition, at the planning stage, we generate a list of features that will be included in the MVP.

The agile development methodology requires that each sprint should end with the implementation of a specific function or business value that the customer has the opportunity to observe and approve or give feedback on. Depending on the project stage, each sprint implements a certain number of functions so that the product gets closer to the final development goal with each stage. Each sprint ends with a presentation of the deliverables, feedback, and adjustments in accordance with the customer's wishes. The number of sprints in a project depends on the complexity of the task and the timing of its implementation.

As we approach the final stage of development, previously approved by the customer, we hand over the prescribed test cases and product testing scripts to the customer's representatives or an involved focus group. At this point, the test version of the product is usually already published on the server or in mobile markets with limited access only for approved persons. In international practice, this stage is called User Acceptance Testing. Its purpose is to transfer the integrated system as a whole, rather than individual components, for testing and review. It is worth noting that, at this stage, some functions are still being developed, and testing takes place exclusively according to approved scripts. Upon completion of this stage, we make all the adjustments to the system and proceed to the software release.

At this stage, our specialists publish the software for public access. Depending on the platforms, it can be the AppStore or PlayMarket, virtual servers in the cloud, or physical servers of the customer. Our DevOps has extensive experience with Microsoft Azure and AWS Cloud and migrates products to the customer's infrastructure. Depending on the agreement, we develop project documentation - public offers, privacy policies, which are essential for publishing applications in accordance with international and Ukrainian requirements. After the official release, the warranty period begins, where we eliminate all unexpected inaccuracies for free to ensure the correct operation of the software.

If our customer does not have the resources to support server software and servers, we offer such services as an option. Our experts continuously monitor databases, set up data backups, and configure the environment to reduce the possibility of hacker attacks. For mobile applications, our team monitors all updates to iOS and Android operating systems and promptly publishes updates to the relevant mobile markets. Depending on the product and the geography of its use, our lawyers monitor changes in legislation and service providers' policies and initiate product updates to ensure compliance with all updated regulations and requirements.