Recently, Apple introduced a new App Submission warning stating that they are formally deprecating UIWebView. We wanted to let the Ionic community know what this warning is all about and how the Ionic team plans to address it.
Update 01/15/2020: On December 23rd, 2019, Apple clarified plans for UIWebView: “The App Store will no longer accept new apps using UIWebView as of April 2020 and app updates using UIWebView as of December 2020.” Please follow the instructions below to either update to a newer version of Cordova or migrate to Capacitor.
Update 11/25/2019: The Cordova team has released Cordova iOS 5.1.0, which disables UIWebview at compile time. To use it, ensure you have a WKWebView plugin installed, then add
<preference name="WKWebViewOnly" value="true" /> to your
config.xml file. Complete details below.
The bottom line: It’s time to update your apps! Apple will only accept submissions of Ionic-based iOS apps that contain references to UIWebView until April 2020 (new apps) and December 2020 (existing apps). To meet the new requirement, simply update to the latest version of Capacitor. If you’re using Cordova, see below.
Storing photos in a Cordova-based Ionic app can be challenging. Several concepts and layers of the app development stack are involved, including selecting the best Camera plugin configuration, saving files to permanent storage, and understanding how to render an image in a WebView.
In this post, we’ll use the Ionic Native Camera plugin to take photos, then save them to the app’s filesystem using the Ionic Native File plugin.
Note: For a guide covering similar concepts using Capacitor’s Camera and File plugins, see Josh Morony’s great guide here. For more advanced Cordova examples covering images, video, and audio, see Simon Grimm’s Ionic Media Files guide.
With the success of the last Ionic Show episode, we wanted to keep the momentum going and make sure we keep creating new episodes to keep our community up to date with all the latest and greatest happenings inside of Ionic. With that, I’m pleased to announce that the latest episode of the Ionic show is now available!
Today we are excited to announce that the Release Candidate for Ionic React has launched and is now available!
We released the first Beta of Ionic React in February, and since then, we have received a ton of feedback and contributions from the community. Based on this feedback, we have been working to make Ionic React a great experience not only for React developers but for anyone looking to jump into web development.
Ionic React RC marks the first major release of our vision to bring Ionic development to more developers on other frameworks. This was made possible by Ionic v4.0, which was completely re-written from the ground up focusing on web standards and not dependent on a particular framework. Ionic v4.0 makes it possible for us to target many frameworks while still having our core components be a single code base shared across all these frameworks.
We’re officially hiring for a number of engineering roles at Ionic. I wanted to quickly expand on what those roles entail and what the day to do day looks like, and also share some insight into what we do here at Ionic day in and day out!
Senior Engineer – Desktop IDE (Studio)
Link to job
Want to come build awesome desktop developer tools that make app dev easier than ever before? We’re looking for a strong frontend engineer that is comfortable with modern frontend app dev, such as React, Angular, or Stencil, along with state management systems like Redux (or otherwise), and with production experience using Node.js. You should have experience building complex frontend apps, though don’t worry if you haven’t done much Electron development.
Today we’re excited to introduce support for Capacitor to Ionic Appflow, covering all features such as cloud-based native builds, real-time updates, and CI/CD automation.
If you’re already a user of Appflow and Capacitor, feel free to skip down to the section below, Setting Up Capacitor, for instructions on how to get started.
Ionic Appflow is a Mobile DevOps solution for developers and teams building apps with Ionic. It helps increase agility and app quality while speeding up time-to-market by automating key phases of the development lifecycle. By generating and streamlining the native app build process, shipping real-time updates, and organizing approval workflows, your team is free to focus on the good stuff (innovation).
Facebook Login and
Admob. Follow him on Twitter @rdlabo.
Ionic 4 provides excellent performance out-of-the-box. Even so, I’m a fan of pushing the limits of my web applications. In this post, I’ll be covering some recent experiments I conducted that look at how to improve the performance of Angular within an Ionic 4 app. These hypotheses included:
- Using Eager Loading (Instead of Lazy Loading)
- Preloading Ionic Components
We’re halfway through 2019, and I thought it would be a good time to take a step back and share a bit about what is going on at Ionic the company.
We don’t often talk about the “business side” of Ionic, at least not in the way that we do our open source stuff. Part of that is because we don’t want to confuse people into thinking we’re becoming all-commercial and stopping our open source efforts, but a big part of that is because our commercial offerings are largely focused on bigger teams which make up a relatively small part of the community, and all of our business is fueled fundamentally by our open source work anyways.
Making money and open source are not mutually exclusive. In fact, we think that open source projects that are sustainable and have a real business model on top are one of the best project structures in the ecosystem. For Ionic the company, our open source software powers a huge chunk of our top of funnel, not to mention the core fabric of our product offering, meaning most of our customers started out by being users of our open source projects, and we are known best in the community for our open source work. For the community, that means our open source efforts are the most important thing that we do, so our interests are highly aligned around creating the best open source app development platform in the world.
We’ve always been driven at Ionic not solely by traditional business metrics, but by usage, adoption, and quality metrics first, with the belief that you have to get those right first in order to get the business metrics right. At the same time, investing in open source is difficult, expensive, and time consuming. We realized that if we could crack the nut on an innovative and strong business model on top, we would have our own nuclear reactor of sorts: a reliable supply of resources to build out the open source platform, with a natural and compelling hook to introduce commercial offerings to teams that need them on top.
So, I would like to talk today about that open source business model we’ve built, how it works, how it’s working today, and where we plan to take it from here.
Well hello there, Ionic community! I wanted to take a moment and tell a story about a hashtag on Twitter. This hashtag brought so many smiles to my face and everyone at the Ionic office that we decided it deserved more notoriety.
This is the story of how
#MyIonicStory came to be and why it matters so much to us.
This week, we’re excited to introduce Ionic Auth Connect, a new security solution that makes it easy to add single sign-on and secure user authentication to any of your Ionic apps.
Auth Connect provides a simplified interface for developers attempting to implement authentication flows using common authentication services such as Microsoft Active Directory, AWS Cognito, Auth0, or any auth provider that uses the OpenID Connect protocol.
Before I get into the details of why we built Auth Connect and which problems it solves, it’s helpful to start with a quick primer on how authentication flows work — and the common pitfalls that you’re likely to encounter if implementing auth on your own. Anyone who has recently attempted to add an auth workflow to a mobile app will appreciate how complicated it can be.