The product used a combination of serverless and microservice approaches with plain JS functions. Right off the bat, our developer introduced a Nest.js framework along with a practice of writing a separate function per endpoint. On the developer’s initiative, the team started writing libraries for all code that runs on more than one service, adding it to the CI/CD pipeline.

The product’s front-end used its own data types that had to be updated with each backend update. Using the contract programming approach, our developer moved these data types into a separate library. The front-end now just has to update the contract version to use the updated data types.   

• Introducing Lambda functions with Nest.js, standardized backend response formats, code libraries, programming by contract, and more.
• Unit and Integration test coverage on all services increased from 0% to 90%.
• Improving team collaboration with detailed Swagger documentation.

Our developer initiated several practices that improve teamwork. With a Nest.js serverless starter repository, Nomoko engineers can now quickly add any Lambda function. The product benefits from React Query, React Hook Form, request caching, and improved frontend performance. 

An unexpected challenge came from the need to integrate Nomoko with 2 partner systems. They both had incredibly outdated REST and SOAP APIs with poor documentation. Only by working proactively with the partner stakeholders, our developer managed to translate business requirements into tech tasks. A third integration required our developer to rewrite most of the front-end to change data rendering principles.  

• Establishing the process of keeping all dependencies updated to improve security.
• Introducing libraries for working with AWS services.
• Client team mentoring and a smooth project hand-off.

We help you validate ideas as early as possible to ensure their ultimate success. 

This starts with documenting the product requirements. After the initial analysis, we proceed to user research, competitor analysis, and rapid prototyping. The idea is to validate the solution before writing a single line of code. Another priority is to identify the possible risks and success metrics, learning how your solution could outcompete the alternatives. 

Outcomes: Lean/Value Proposition Canvas, product wireframes, rough roadmap & costs, market research, user personas, solution proposal.

Product discovery isn’t a one-time activity. 

Our designers and architects work iteratively to detail its every aspect. We focus on testing assumptions in real-world conditions with focus groups and user surveys. This helps to prioritize the key features. A work breakdown structure (WBS) allows the team to estimate the project costs. You can then sign the development contract or take the project to another company.

Outcomes: high-fidelity prototype & testing, solution architecture, WBS, product roadmap, cost estimate, risk mitigation plan.

We develop your product using an iterative Scrum approach. 

Every team member focuses on making the product work instead of delivering this or that feature. You, too, can attend our daily meetings or get weekly status updates. Early validation is still a priority, each iteration ends with a live demo. We also try to collect feedback from real users as early as possible to understand what works and what doesn’t.

Outcomes: beta user testing, working features delivered with each iteration.

A product manager helps you determine an optimal release date. 

When the launch is set in stone, we help you make the necessary preparations. This includes checklists and training for your staff, service-level agreements, marketing consulting, and setting up all analytical tools. As soon as the product goes live, we start tracking the success metrics and collecting user feedback.

Outcomes: go/no-go checklists, staff training, SLAs, setup of analytics, beta testing, customer surveys, product growth plan.

Iterative development continues along with user testing until your product reaches the maturity stage.

The team fixes any remaining bugs, collects feedback, and manages change. We may involve data analysts to track success metrics and user actions and prepare a next-action plan based on the data. 

Outcomes: new features, next-action plan, product optimization.

You can delegate the support to another team or stay with MindK. This phase usually lasts until the product must be retired or improved to stay relevant.