Marviq’s path to success
A few years ago, Marviq was committed to an older framework: backbone.js. It was cumbersome to program in it and hard to find developers with experience or willingness to work in it. But we then came across a small project, which we could use to experiment. At this point, we didn’t have a favourite yet as far as the front-end framework is concerned, so we faced an important decision.
Angular – yes, we chose Angular v.2. I personally insisted on choosing this framework. By browsing through articles about new frameworks and their capabilities and potential. I chose it based on the difficulty. I saw potential in it – more difficult than others, but able to train developers to improve their programming skills and best practices. It forces developers to expand their knowledge of technology, not just “patting” the code.
While working on the small project, we tried to make the product as “scalable” as possible. This means that in the event of a problem or failure, we could learn from this for other projects and frameworks. We were also creating libraries in Angular when working on a project (yes, back then Angular already provided a nice way to do this). After a few sprints, we managed to achieve our goal – we had it! Thanks to a good approach and scalable application development, we used the given solutions in subsequent projects. Time saved in re-implementing the same things was spent on expanding our libraries.
After some time, we could see that Angular developers, thanks to its complexity, are better at adapting to a change or adapting to another framework. Unfortunately though, Vue or React developers have a harder time switching to Angular.