To see if the construction assumptions work in practice, we usually build the first copy of our project in the form of a prototype. Usually, after running the prototype, it turns out that some detail needs to be changed – correct or removed, that sometimes you should use a different component, or change must relieve the software, because not everything works as it should.
This is the nature of the prototype and we never get offended if something went wrong. Our goal is always to achieve success in the shortest possible time and with the lowest possible financial outlay. We always make efforts in the design process and at the stage of building a prototype to avoid any corrections. We are happy when our customer is satisfied.