Senior Developer at a consultancy with 11-50 employees
Real User
2022-12-14T11:53:52Z
Dec 14, 2022
When they jumped from version 3 to version 4, 5, and 6, they introduced something called Capacitor, which is basically the tool that you use to convert your code to Xcode, etc. They have a few plugins that are still using, for instance, PhoneGap. So, you have to jump between Capacitor and PhoneGap. Their documentation is good, but there are some versioning control issues. For example, if you want to bring up a phone dial-up or a map, you have to decide whether to use Capacitor, PhoneGap, or Cordova. They started writing Capacitor to get rid of PhoneGap and Cordova, but they haven't yet got all the libraries and all the functionalities. They want you to start using Capacitor, but they don't have all the libraries there. They're developing them as they go. So, currently, you have to mix and match the three. When it comes to mobile applications, I would only like to use Capacitor. I don't want to jump between Cordova and Capacitor or have both of them. That's the main thing for me, but they have been working on it. They have started to bring them closer and closer so that you don't have to use two different sets of libraries. They're close to where you don't have to use Cordova or PhoneGap, and you can only use Capacitor. In versions 5 and 6, they have improved it a lot. They can also improve it in terms of publishing to different stores. For instance, I'm using Firebase to make my Ionic app web compatible. If I don't have a Node.js server to host on, I have to host it on Firebase or something like that. Currently, if I need to publish to different stores, such as the Microsoft store or the Huawei store, the only way I can publish to, for instance, the Huawei store is by creating the APK and uploading it. If they can start adding a little bit more integration to publish to different stores, such as the Samsung store, Huawei store, or Microsoft store, it would be good. Currently, there are no problems with iOS and Google Play Store, but for the other stores, you have to do a little bit of a workaround to get things done. Its stability could be better. For me, jumping between versions 3, 4, and 5 was a big problem because it wasn't seamless. Jumping from version 5 to 6 is more seamless. Jumping from version 3 to 5 has been a nightmare because I had to recode quite a lot to be compatible with version 5. I totally skipped version 4 because it was just too quick. Jumping between versions has definitely been a problem for me. If I have to do a lot of plugins and redo a lot of my coding because they're jumping versions, I'm going to look for something else.
Ionic is a cross-platform framework, so when we compare Ionic with native Android and iOS, we can see the drawbacks. For example, if you need to work on very high-level aspects of an application such as animation, even if everything else is not putting load on the app, you will still see high load from the server side. You will eventually find yourself getting lots of image, video, and hardware-related work to deal with. This is the main limitation of Ionic because we still have to depend on the native Android and iOS code. However, in other ways we can achieve the same performance with Ionic as we can achieve with native Android code. One feature I would like to see added is the code post. The code post is a very good feature I encountered when using React Native. Inside the code post, you don't need to deploy your application again when you're modifying your code. You just need to run one command, and each and every server will automatically receive the latest modification. A similar feature in Ionic would be appreciated. Another drawback of Ionic has to do with the no-code service that they provide, where you just need to drag and drop your components to build your application. I feel that, coding-wise, it isn't a good feature. And, for instance, if you're making an API call, they would only provide the UI, so you would still need to take some time to modify it. Because of this, I considered simply building our UI from scratch. Apart from that, one other disadvantage is when you're using a type of plugin like AdSense for putting adverts in your application, Ionic would take a percentage of whatever profit you make.
Senior Software Engineer at Huawei Technologies India
Real User
2022-09-16T20:06:21Z
Sep 16, 2022
It would be good if the mobile version uses something other than JavaScript and HTML. I would like to see the addition of more performance and security features to the next release.
Previously, Ionic didn't release many updates but they now do this every year. They have also improved their support documentation. In a future release, we would like to have a little more support for the desktop environment. Currently it is still focused on mobile devices.
The supported document on this solution could be improved. (ionicframework.com) When you look at the above doc page. There are bunch of plugin references on the left side. And you click on any topic of them, the main page will show you only a short sample code in Angular section of the Usage Title. For React, there is always a "See here" link there. When you click on the "See here", the next page always shows camera related code in Angular section and barcode-scanner related code in React section, which is not related to the topic you clicked. BTW, Vue is always missing there.
Ionic is an open-source UI toolkit for developing high-quality mobile and desktop apps with web technologies such as HTML, CSS, and JavaScript. Ionic focuses on the frontend UX and UI interaction of an app – UI controls, interactions, gestures, and animations. It is simple to learn and can be used without any frontend framework by utilizing a simple script inclusion.
While previous versions of Ionic were strongly connected to Angular, version 4.x of the framework was re-engineered to serve as...
When they jumped from version 3 to version 4, 5, and 6, they introduced something called Capacitor, which is basically the tool that you use to convert your code to Xcode, etc. They have a few plugins that are still using, for instance, PhoneGap. So, you have to jump between Capacitor and PhoneGap. Their documentation is good, but there are some versioning control issues. For example, if you want to bring up a phone dial-up or a map, you have to decide whether to use Capacitor, PhoneGap, or Cordova. They started writing Capacitor to get rid of PhoneGap and Cordova, but they haven't yet got all the libraries and all the functionalities. They want you to start using Capacitor, but they don't have all the libraries there. They're developing them as they go. So, currently, you have to mix and match the three. When it comes to mobile applications, I would only like to use Capacitor. I don't want to jump between Cordova and Capacitor or have both of them. That's the main thing for me, but they have been working on it. They have started to bring them closer and closer so that you don't have to use two different sets of libraries. They're close to where you don't have to use Cordova or PhoneGap, and you can only use Capacitor. In versions 5 and 6, they have improved it a lot. They can also improve it in terms of publishing to different stores. For instance, I'm using Firebase to make my Ionic app web compatible. If I don't have a Node.js server to host on, I have to host it on Firebase or something like that. Currently, if I need to publish to different stores, such as the Microsoft store or the Huawei store, the only way I can publish to, for instance, the Huawei store is by creating the APK and uploading it. If they can start adding a little bit more integration to publish to different stores, such as the Samsung store, Huawei store, or Microsoft store, it would be good. Currently, there are no problems with iOS and Google Play Store, but for the other stores, you have to do a little bit of a workaround to get things done. Its stability could be better. For me, jumping between versions 3, 4, and 5 was a big problem because it wasn't seamless. Jumping from version 5 to 6 is more seamless. Jumping from version 3 to 5 has been a nightmare because I had to recode quite a lot to be compatible with version 5. I totally skipped version 4 because it was just too quick. Jumping between versions has definitely been a problem for me. If I have to do a lot of plugins and redo a lot of my coding because they're jumping versions, I'm going to look for something else.
Ionic is a cross-platform framework, so when we compare Ionic with native Android and iOS, we can see the drawbacks. For example, if you need to work on very high-level aspects of an application such as animation, even if everything else is not putting load on the app, you will still see high load from the server side. You will eventually find yourself getting lots of image, video, and hardware-related work to deal with. This is the main limitation of Ionic because we still have to depend on the native Android and iOS code. However, in other ways we can achieve the same performance with Ionic as we can achieve with native Android code. One feature I would like to see added is the code post. The code post is a very good feature I encountered when using React Native. Inside the code post, you don't need to deploy your application again when you're modifying your code. You just need to run one command, and each and every server will automatically receive the latest modification. A similar feature in Ionic would be appreciated. Another drawback of Ionic has to do with the no-code service that they provide, where you just need to drag and drop your components to build your application. I feel that, coding-wise, it isn't a good feature. And, for instance, if you're making an API call, they would only provide the UI, so you would still need to take some time to modify it. Because of this, I considered simply building our UI from scratch. Apart from that, one other disadvantage is when you're using a type of plugin like AdSense for putting adverts in your application, Ionic would take a percentage of whatever profit you make.
It would be good if the mobile version uses something other than JavaScript and HTML. I would like to see the addition of more performance and security features to the next release.
Ionic would be improved with dynamic design features.
Previously, Ionic didn't release many updates but they now do this every year. They have also improved their support documentation. In a future release, we would like to have a little more support for the desktop environment. Currently it is still focused on mobile devices.
The supported document on this solution could be improved. (ionicframework.com) When you look at the above doc page. There are bunch of plugin references on the left side. And you click on any topic of them, the main page will show you only a short sample code in Angular section of the Usage Title. For React, there is always a "See here" link there. When you click on the "See here", the next page always shows camera related code in Angular section and barcode-scanner related code in React section, which is not related to the topic you clicked. BTW, Vue is always missing there.