Get in touch →
+61%
+85%
74%
+80%
Hyperledger
This framework was chosen for being a good fit for the business model.
Hyperledger is a software framework for developing blockchain-based applications and specialized business solutions.
The solution has a modular architecture that allows for plug-and-play use of various components and uses container technology to execute smart contracts that implement the system's application logic.
Golang
This programming language was used as the back-end engine because it goes well with Hyperledger.
Its high performance and simple syntax make it possible to develop applications much faster. The simplified syntax makes it easier not only to write your code but also to read code written by other programmers, which is especially important in teamwork.
Docker
Docker is open-source software used to develop, test, deliver and run web applications in containerized environments. It is needed for more efficient use of system and resources, rapid deployment of finished software products, as well as for their scaling and migration to other environments with guaranteed preservation of stable operation.
Kubernetes
Kubernetes was used mainly for Docker management and scalability.
It is a portable open-source platform for managing containerized workloads and services that facilitates both declarative customization and automation.
React
React is an efficient, declarative, and flexible open-source JavaScript library for building simple, fast, and scalable frontends or web applications. React allows developers to utilize individual parts of their application on both the client-side and server-side, which ultimately boosts the speed of the development process. React code is easier to maintain and is flexible due to its modular structure. This flexibility, in turn, saves a huge amount of time and cost to businesses.
The specification is always required to enable a clear understanding of architecture, business objectives, overall goals of the product, design, features, and list goes on.
Goal:
The project initially was at the Proof of Concept stage. We needed to create a Minimum Lovable Product and then take into account behavior data and feedback from the users.Main flow:
The main flow for the user included simple functionality like user accounts, product data, search with filters, cart, contracts, check-in / check-out processes, truck history, reports, user behavior analytics.Oleg Svet
Mikhail Bobrovsky
Vlad Serdiukov
Andrey Melnychenko
Bogdan Kusch
Maria Grekova
We always try to shed some light on the processes behind the scenes to make sure we`re on the same page with our clients.
With a clear board of tasks, Jira was our main communication tool. We also complemented it with additional tools like Email and Slack. All epics and tasks were added to Jira. The description of functionality was added to Confluense.
The scrum approach was chosen as the most optimal option both for us and for the client. Sprint started on Wednesday, meet-ups, as well as any other team-wide activities were coordinated with the time zone of the client. Demo and retro happened on the last day of the sprint. The team had a retrospective, sprint planning, and task grooming after each 2 weeks sprint.
CONSULTING
Product DESIGN
Product Engineering
Working on product design, we primarily develop its architecture, as this has a great influence on how the design will be built in the future, and how ways of promoting and upgrading the product will be organized.
1.
Launch
Before the initial launch, we have followed up with the client to check every single sprint is completed and everything runs smoothly.
2.
Transfer
As we worked on the client`s Git, there were no issues with the project`s transfer.
3.
Education
No post-support or education was required from the client.