In the React world, the primary way to build native iOS and Android apps has been React Native. Created by Facebook in 2015, React Native enables developers to use their React skills to build iOS and Android apps using platform native UI elements. React Native is popular and widely used, and it’s a great solution for many teams.
However, React Native comes with a number of tradeoffs. First, it requires developers to build in a React Native specific way, using views/JSX for each platform, and using libraries that support react-native (as opposed to most React libraries that support react-dom). But perhaps most importantly, React Native is not a web environment, so it’s not possible for teams to take their web-based React apps and libraries to deploy native apps.
The net effect is that it’s not possible to take, say, a Material-UI React web app, and deploy it natively to the Apple App Store or Google Play Store with React Native.
To do that, we need to take a look at Capacitor -- a native runtime for cross-platform web apps, including any and all React web apps.
Today at the first ever official Ioniconf, we unveiled a number of exciting updates to Capacitor and the Capacitor community.
In no particular order, we announced:
Today we are excited to announce Capacitor 2.0!
Capacitor 2.0 offers some key platform updates as well as security and bug fixes. These include:
We documented the whole update and talked about what's next for Capacitor over on the Ionic blog.
Check it out:
Today I’m thrilled to announce the 1.0 release of Capacitor, Ionic’s new Native API Container that makes it easy to build web apps that run on iOS, Android, and the web as Progressive Web Apps—with full access to native functionality on each platform.
We documented this momentous occasion over on the Ionic blog, complete with a comparison to Cordova and where Capacitor is headed from here.