In business world there is a dilemma that always takes place: how to combine outstanding quality of the product with minimal expenses. It is normal for clients to expect quality and at the same time try to save up on money and time. After all, the clients are paying to the company so they want to make sure their finances are spent efficiently. In the IT world with overwhelming amount of companies, constantly popping out, competition is everything and one has to come with really good competitive advantage. It can be a cutting-edge technology that you use to optimize your processes and improve the delivery.

Using new technology is always a bit risky as you cannot be 100% sure in it. In our article we want to compare two frameworks that we use, React Native and Ionic, and point out the main pros and cons of each.

Because we always strive to improve our work, we are doing our best to solve a question: how we can cut on time and costs and keep the quality on the satisfactory level. It is well-known that development costs are quite high even to develop one platform, either Android or iOS. And development for two platforms makes the costs grow twice (or even more).

One of our experiments included Cordova, but it did not feel as something we could get value of.

Then Ionic got our attention. It seemed perfect for the engineers – it’s modern, focuses on mobile apps and is not very complicated. We utilized Ionic as a component in a couple apps and built around dozen apps on this framework.

But as time went, we began to notice some cons with this framework. Debugging took a lot of time and we frequently missed the deadlines. At first we thought the problem is with our processes that needed improvement in design or architecture. However, the problem was about technology and our processes were fine.

As this article is dedicated to the framework comparison, let’s first have a look at the problems with Ionic that we noticed:

• Response took too much time;It was uncomfortable to work with slideout keyboard, especially on great amount of devices;
• Debugging;
• In order to find the best solution, we try to use different technologies and see what works the best. So at the same time with Angular we started to work with React and soon noticed its advantages over Angular.

You can read more about our opinion on React in part 2 of this article in our blog. Sign up for our newsletter and never miss  updates from DashBouquet!