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.

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 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.

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.

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

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

I didn't have the time to create applications for Android or iOS so I started using Ionic to code and deploy builds. For me, it was very easy to use. I didn't have to learn Android or Script for iOS and could use one source code for different platforms.

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.

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.

We are using Ionic for tracking our internal applications.

Ionic is uploaded within the Google Cloud console. I am using it to complete general tasks in Google Cloud locations and Deskforce.

My primary use case of this solution is for its web application development. We are customers of Ionic and I'm a project manager.

I use Ionic for app development.

I mainly use Ionic to create hybrid applications.