November 1, 2017, Google announced the fifth version of Angular, code-named "pentagonal donut." This made many business owners carefully consider once again whether their project is in need of a complete “renovation.” The reasons are significant. The new version includes new features and fixes existing bugs, and in the same breath, it focused on reducing the size of Angular, making it quick and easy to use. Read more about all novelties of Angular 5 in our previous article.
But what to do if you feel quite good with Angular.js?
-start writing applications.
-learn it, as Angular.js had excellent documentation and a lot of fantastic tutorials.
-write your own modules and use them as plug-ins or parts of your application.
What is more, Angular.js somewhat gave birth to Vue, Aurelia, and Angular 2/4/5. Aurelia is an offshoot of Angular.js. Angular (Angular 2+) is a continuation of Angular.js. Some developers call Vue.js the new Angular.js because of the directives such as v-if, v-bind, v-on, etc.
Yet, it is high time to move on. With this, Angular 5 may turn out to be something your project lacks. Everything depends on you. If you understand that money invested in the development of your project will see a great return, then you’ll continue to read this article, in which we’d like to talk about our experience with migration.
K&C on the benefits of migrating to Angular 5 and how this all began.
K&C has already been working with a certain Germany-based client for a long time, whose project is built on the white label approach and realized through a microservice architecture. Thus, the web application is a set of widgets, completely independent of each other by code.
The project was designed to manage a kind of a taxi station. The main office owns cars. Each has its account and administrator. Thus, the manager is able to control all information about trips, how much fuel was burned, and where a driver was at a certain hour. The project is especially useful for Germany, where finance reporting is strict.
Around half a year ago, we got the task to develop one more widget. It’s rather small: just 2-3 pages and half a dozen requests to the backend. When we started planning further actions regarding 2018, it turned out that we had too few functional tasks that the customer wanted and too much free time, thus, we offered a variant of migration from Angular 1 to 5.
The migration was reasonable because of:
1.Minimized risks. The migration from Angular 1 to Angular 5 is a risky business. However, we had the chance to experiment by dealing with a small application, with no risk of breaking someone’s working process. We were able to observe how much time it would take, how convenient it is, the general process of migration, and possible benefits.
2.The speediness of Angular 5. Working with Angular.js, we had to download the whole file - and it took a lot of time. One of the most important benefits of Angular 2+ is that a project is divided into many separate parts. Thus, we could connect certain functions to the certain module where it is needed. This reduced the load time and the total amount of code.
3.Attractiveness to developers. The more modern the code is, the easier it is to attract new people to the project. It's no secret to anyone that people leave projects because they do not like to support the old code. Finding a developer for the latest version of any framework, not necessarily Angular, is much easier than saying that eventually in the future we will need to migrate.
If you want us to manage the migration of your product, reach out to our agile development team, which will allow you to control the overall working process with a stable budget.
The first thing we paid attention to was the architecture, as the main demand of our client was the opportunity to customize the widget so that a customer sees only his/her personalized themes and settings, whereas all the customer styles are kept on repos.
URL structure. After architecture, we thought about routes (URLs), that is, how URLs change while one is surfing the website.
Data. We have new libraries, such as NGRX. With the old version of Angular, we took data from the backend and inserted it into the page, and if we needed this data, we had to make another request. With the help of NGRX, we made just one request, saved all the needed data, and that’s it.
These three steps are the most crucial. After they are completed, it’s possible to start writing code, basing on a new architecture and a new model of how to work with data.
Translation. Clients are different. We never know to which website (regionally) our widget will be connected. This also needs to be worked out while considering the architecture.
However, if everything is carefully thought out, then there is nothing to worry about.
The K&C team wants to wish you success in your migration from Angular 1 to Angular 5. Do not forget that the main thing here is to wrap your mind around completely embracing the latest version of Angular. If this is ignored, then there is no sense in further actions.
You'll still see some benefits, but not all. However, if you take Angular 5 without connecting it with Angular 1, you’ll gain a lightweight project functioning on desktop as well as mobile devices.
If you do not know how to execute your project, and are afraid of operational risks, then get in touch with us, a full-cycle product Delivery Management team. We know how to minimize costs and deliver a quality project within a strict deadline.