Ionic Reviews

We are using it for mobile applications that we are publishing to iOS, Huawei, and Google Play Store. It's a very nice hybrid framework for mobile applications.

Being able to have one set of code is valuable. I don't have to recode for different platforms. I don't have to recode for Xcode, Angular, or Android. So, the biggest feature for me is that it's a hybrid system, and I can have one set of code, and then the tool sets that are in there convert my code for Xcode or Play Store. It makes work a lot easier. I don't have to develop three or four code sets for one application. I can do everything from Ionic. 

It has a very powerful Node.js engine as well. It has also got some nice widgets, icon sets, templates, and things like that, but you do need to have some coding background there.

They've created a professional platform where there's a little drag and drop to create apps. For me, integrating or connecting to databases and things like that is very easy. I can integrate any type of backend, such as MySQL or PHP, by using web services and things like that.

The last project I worked on with Ionic was for a popular medical company. We had to build a platform that could work in both mobile and web environments, and we chose Ionic because it allows you to do a one-code deployment to all kinds of solutions.  It was easy for us to deploy to the stores and web.

The most valuable feature is the one code deployed to all solutions, which means you do not need to have multiple teams. Your web team can be the mobile team, and it can be the iOS team. It reduces the number of overheads and the amount of cost per developer.

The main reason we use Ionic is because it is designed to be cross-platform. If you need to build an application with the same functionality on iOS and Android, you don't need to worry about maintaining two separate applications. We can build and deploy on Ionic, and then enter the apps into the Apple App Store and Play Store. With Ionic, only one source code needs to be managed across multiple applications.

Ionic also provides their own tools to deploy the application along with Ionic Capacitor, but I was mostly using custom manual deployment along the lines of, "Let's run some commands in Android and Xcode", and then generating net-aware applications. Additionally, Ionic supports web applications and PWAs (Progressive Web Apps).

In our company, we have multi-member developers where some are working on Ionic using React Native, some are working on web apps and Vue JS, and we are all working in a parallel fashion. In my group we currently have around 10 people working on Ionic, even though they're also working on React Native and other languages that have different skill sets. For myself, I have more than three years of experience in Ionic using Angular, until I switched to working on Ionic with React Native.

When I first started working on Ionic, I noticed that what they were doing is just creating a WebView of native code in the background, and then rendering everything on WebView. That means that it's converting our code to HTML, and the HTML was being rendered on WebView for native Android and iOS. For this reason the performance wasn't very good, and at times they were using code or a plugin for this until version five, when they introduced Capacitor.

Capacitor provides a lot of features we can use, including libraries and code for the camera plugin, post notifications, and so on. The thing is that if they are not using WebView, they have to internally build some native modules for Android and iOS. Whenever we import those modules from Android and iOS and we are busy creating the APK and building the applications, they are converting into native components instead of WebView, and that's why we're seeing such good performance now.

Our company uses the solution to develop hybrid mobile applications that include PWAs, Android apps, and iOS apps. 

Our developers rely heavily on Storage, PWA, and CodeOver but prefer that our laboratory designs other components to ensure a homogeneous work environment. 

The solution is secure, reliable, and packed with features so we can easily implement apps even in the most complex situations.

The solution provides flexibility with useful components such as a date picker, Storage, biometric and CodeOver plugins, and end-to-end payments. 

For example, we used the solution to develop banking apps for a client because its features met banking requirements.

We started building with Ionic mainly for our hybrid mobile application development projects, and as we got a little bit more comfortable and the toolchain improved, we've also used it for web development that we've done for some of our customers.

There are two main things. Because it's a hybrid mobile app framework, it is easy for us to develop iOS as well as Android apps for our customers with the same resource skills. We didn't have to have separate iOS teams and Android teams to build the apps. We still have to use the Apple Xcode for iOS, but the main development happens with JavaScript, HTML, and CSS. We don't have to write separate code bases in scripts for iOS and Android. We create apps using web-based technology. 

Another advantage is that it comes with a lot of free, inbuilt components. It has UI components that are already mobile-friendly. It also has a very good in-built navigation for the mobile context. It makes development very easy. You do it for one platform, and it is automatically done for both platforms.

We use this solution for angular application development; these are Android apps on the mobile platform.

The main value of this solution for our business, is that it is a hybrid product that allows us to write code that is compatible with IOS, Android, and web documents.

I use Ionic to design the printing phase per customer requirements. I use the ID screen, which is usually coded, to create the pages of the Android and iOS mobile applications.

Ionic is easy to upgrade and is helpful for design purposes. It also is quite common and easy to use.

It is a very reliable application. It's easy to write on and print.

The UI is easy to use as well.

My organization chose to go with Ionic because we can access both Android and iOS applications.

It's very flexible for UI development, and we use it for front-end tasks.

It supports JavaScript, Bluebird, Node.js, and Angular. Inside the Ionic Framework, if we want any control from the Angular perspective, we can include it.