Try our new research platform with insights from 80,000+ expert users

IBM MobileFirst vs Ionic comparison

 

Comparison Buyer's Guide

Executive Summary

Review summaries and opinions

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Categories and Ranking

IBM MobileFirst
Ranking in Mobile Development Platforms
13th
Average Rating
8.4
Number of Reviews
3
Ranking in other categories
Mobile App Platforms (7th)
Ionic
Ranking in Mobile Development Platforms
8th
Average Rating
8.6
Reviews Sentiment
7.3
Number of Reviews
14
Ranking in other categories
No ranking in other categories
 

Mindshare comparison

As of January 2025, in the Mobile Development Platforms category, the mindshare of IBM MobileFirst is 1.7%, up from 1.7% compared to the previous year. The mindshare of Ionic is 7.8%, up from 7.6% compared to the previous year. It is calculated based on PeerSpot user engagement data.
Mobile Development Platforms
 

Featured Reviews

MT
Streamlines development of hybrid applications, and has ability to integrate device-native code
It was a cakewalk for us to develop mobile apps for three different platforms using IBM MobileFirst. Since it was a consumer application built for large-scale events, it was very crucial for us to manage application compatibility with all sort of devices. With MobielFirst, we could actually achieve this with very little trouble. With help of this product, we have been able to develop mobile applications without having complete knowledge of each mobile OS's native programming. App development, delivery, and code management have been very efficient using this product.
Roche De Kock - PeerSpot reviewer
Allows us to create cross-platform mobile apps from a single code base, but should have a complete set of libraries for Capacitor
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.

Quotes from Members

We asked business professionals to review the solutions they use. Here are some excerpts of what they said:
 

Pros

"With help of this product, we have been able to develop mobile applications without having complete knowledge of each mobile OS's native programming technology. App development, delivery, and code management have been very efficient using this product."
"I like Its capability for developing hybrid applications, with an ability to integrate device-native code as well"
"IBM MobileFirst has one of the most feature-rich admin panels."
"The most valuable feature is the one code deployed to all solutions, which means you do not need to have multiple teams."
"It's very flexible for UI development."
"The solution can support many languages."
"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."
"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."
"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."
"The most valuable feature of Ionic is the ease of use and the simple connection of the applications. Additionally, the documentation is good in the Ionic application, and beginners can easily learn and download their own application using Ionic. Everyone can easily switch out, their domain, from native applications to hybrid applications."
"Ionic's best features are its hybrid app development, design, and tags."
 

Cons

"There are issues with push notifications, especially for Windows mobile apps. JSONStore also crashes abruptly at times."
"I would like to see improved support for native device functions."
"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."
"There could be better support for augmented reality and other things. Geolocation and background app activity are some of the things that are a little more clumsy at the moment and could be improved."
"As a developer, I would say one of the improvements is more plugins."
"Ionic would be improved with dynamic design features."
"The navigation within this solution could be improved; it is currently quite complicated to move through the different tabs."
"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."
"Ionic's UI component doesn't always look like the native mobile app."
"Ionic could improve in the Native mode because while we do testing it is difficult to find the root cause of problems. It could be more user-friendly."
 

Pricing and Cost Advice

"Cost depends upon various factors. Size of the overall application and product usage matter a lot. For an enterprise-grade application, this certainly comes out as an economical solution. However, for small-scale applications, it can turn out to be on the higher side."
"I think most of the plugins for Ionic are open source, and you can do a lot with many of the basic features. However, if you need to use a premium plugin for something like extra scroll list functionality, Ionic will ask for a certain sum of money."
"We pay 50,000 dinars per month."
"Ionic is an open-source solution, it is free."
"Ionic is an open source solution, and there are no hidden fees."
"You don't have to pay anything except for certain projects. For example, Appflow has some costs related to it but you don't have to use it. You can also pay for extra support."
"The starting cost for the enterprise option is around one hundred dollars per month."
"The solution's open source option is free with no licensing fees."
"You can use the free version, but if you still want to buy it, the price starts from $499/month."
report
Use our free recommendation engine to learn which Mobile Development Platforms solutions are best for your needs.
831,265 professionals have used our research since 2012.
 

Top Industries

By visitors reading reviews
Financial Services Firm
24%
Computer Software Company
19%
Real Estate/Law Firm
9%
Government
7%
Computer Software Company
19%
Educational Organization
11%
Comms Service Provider
8%
Insurance Company
7%
 

Company Size

By reviewers
Large Enterprise
Midsize Enterprise
Small Business
No data available
 

Comparisons

No data available
 

Also Known As

MobileFirst, Worklight
No data available
 

Learn More

Video not available
 

Overview

 

Sample Customers

UniCredit Business Integrated Solutions, Gruppo Unipol, Raymond James Financial, Toshiba GCS, CST, ABK-Systeme GmbH, BNP Paribas
MRA, Napa Group, Sworkit, Airbus, Sense Corp, Interactive Gaming Company, Pacifica, Untapp'd, Diesel, National Museum of African American History and Culture
Find out what your peers are saying about IBM MobileFirst vs. Ionic and other solutions. Updated: January 2025.
831,265 professionals have used our research since 2012.