Today I’m excited to announce the availability of Stencil Enterprise, Ionic’s official toolchain for building blazing fast web components. Designed exclusively for teams building enterprise-scale Design Systems, it includes access to world-class Support and Advisory teams, priority fixes and issue resolution, and more.
Stencil Enterprise is ideal for large businesses with multiple web development teams, a portfolio of web-based applications to maintain, and a desire to standardize on a single UI library across all apps and projects.
Last year we held our first-ever conference for Ionic developers and the wider developer community. With twelve speakers from the developer community and an opening keynote from our own Max Lynch (Co-Founder & CEO), Ioniconf 2020 was a smashing success. That is why we are incredibly excited to hold Ioniconf again this year, bringing in more community experts to share their knowledge and experience. Without further ado, please welcome your Ioniconf 2021 speakers!
Ioniconf 2021 is a one-day, single-track conference that will be held online. We’re working with some awesome partners to provide an online platform where you can watch presentations and interact with the speakers and other attendees during the conference. Register for free to get access to the conference platform and join the conversation!
When people talk about Ionic Framework, they often put it in the “Cordova” or “Angular” buckets, because historically that’s what Ionic was: a UI kit for Cordova and Angular apps.
That was fine for the first few years of Ionic’s life, but up to around 2018 things started changing. Ionic started working on a new native runtime to replace Cordova that was fully built in house and deeply integrated into the Ionic developer experience: Capacitor. And then a year later, Ionic Framework added support for its first non-Angular framework: React (and later, Vue).
And last week, we rolled out the biggest release of Capacitor yet: Capacitor 3.0, further cementing the future of the Ionic stack as one built on the foundation laid by Capacitor.
That means, in 2021, it’s not accurate to say that Ionic Framework is just a framework for Cordova or Angular anymore, because it’s actually a framework for Capacitor that has official support for Angular, React, Vue, and unofficial support to be used in pretty much any JS stack out there.
In fact, Capacitor installs on npm recently eclipsed Cordova, and the vast, vast majority of new apps created using the Ionic CLI and online app creation wizard use Capacitor. It’s time to fix this misconception once and for all!
Here are some thoughts on how the Ionic community can change this misconception:
Today I’m thrilled to announce the 3.0 release of Capacitor, Ionic’s native runtime that makes it easy to build web apps that run on iOS, Android, Desktop, and on the web as Progressive Web Apps — all powered by a single codebase.
Capacitor connects the web to native, enabling the best of both worlds by providing the tooling and runtime that make it possible to take any modern web app and deploy it natively to all the platforms you care about.
With the release of Capacitor 3.0, we’re unlocking a new approach to building native apps with web technology — a category we’re calling Web Native apps.
In fact, Capacitor is quickly becoming the de facto standard for web developers building for mobile. It’s installed half a million times per month and growing rapidly, with thousands of new apps kicked off every week. It was also rated #1 in satisfaction among mobile development tools on the latest State of JS survey.
With the release of Capacitor 3.0, we’re planting a stake in the ground: Capacitor is now the standard for web developers building mobile apps. We’re firmly committed to making mobile development just as good as web development, and that’s exactly what Capacitor enables. Whether you have an existing web project or are curious about starting a new mobile project, we hope you’ll check out Capacitor.
Now, on to Capacitor 3.0’s major updates, which include improved performance, enhanced developer experience, and greater community involvement.
This is part three of a new series on monorepos. By the end of the series, you’ll have the tools you need to adopt monorepo setups in your organization.
Rounding out our series on monorepos, we take a look at an old friend, but a newcomer to the monorepo game, npm. Npm has long been the de-facto solution for managing dependencies, and it only makes sense that, with the release of npm 7.0, we finally have a built-in solution for creating a monorepo without relying on external tools. Compared to other solutions, however, npm workspaces lack a few features and still have some rough edges. While it is possible to build something with it, for simplicity, I’d suggest looking at Lerna as an alternative. With that being said, let’s look at how we can configure an npm workspace to work with Ionic and Vue.
Today, we are excited to announce the alpha of a new product from the Ionic team: Ionic Portals. Ionic Portals is our first product aimed at native mobile app developers and provides a supercharged Web View native control to enable native and web teams to better collaborate and bring new and existing web experiences to mobile in a safe, controlled way.
The vast majority of apps in the app stores need to integrate web assets for specific screens and experiences. It could be for authentication forms, features such as mortgage applications, or to bring web experiences to mobile without needing to port them to native. And this is the case even for teams that are fully invested in a traditional native app development stack.
But bringing these web experiences to native mobile apps and code bases is anything but straightforward. Teams struggle to integrate web apps with native functionality and do it in a safe, controlled way that doesn’t disrupt the roadmap of the traditional native development teams, and they are stuck reinventing the wheel by extending stock Web View controls such as WKWebView.
Ionic Portals is built on the industry leading Capacitor hybrid app runtime used by companies like Burger King, Paylocity, H&R Block, and Aflac to deploy mission critical apps. It’s essentially a supercharged Web View native control with a ton of features missing from the stock Web Views on iOS and Android.
Today we’re opening our alpha product waitlist looking for teams struggling with this exact problem to help us make sure we are building this the right way. Interested? Read on to see how to join the list.
This is part two of a new series on monorepos. By the end of the series, you’ll have the tools you need to adopt monorepo setups in your organization.
Between sharing code, managing dependencies across projects, and more, monorepos can require a lot of investment to get right. Thankfully, there are many different tools out there that can streamline the process and get developers on the right path. There’s Lerna, Yarn workspaces, npm workspaces (with npm v7), and the one we’ll look at today, Nx.
Let’s look at setting up an Nx workspace and looking at a few packages that can help Ionic Angular developers manage complex app setups and ship their apps faster.
This is part one of a new series on monorepos. By the end of the series, you’ll have the tools you need to adopt monorepo setups in your organization.
Building and maintaining multiple development projects comes with a unique set of problems teams need to solve. How do you share common bits of code between projects? How do you sync dependencies across projects? How do you optimize collaboration between projects?
With solutions to those problems, it’s not shocking to see that monorepos are rapidly growing in popularity. In fact, we use monorepos here at Ionic! Several monorepo tools are available to development teams: Nx, Yarn workspaces, npm workspaces, Lerna, Turborepo…and I’m sure more that I’m not even aware of.
In this blog post we’ll be building out a monorepo using Lerna. I personally like how lightweight it is, and it works well with Ionic Framework React projects and Ionic Appflow.
Our monorepo will consist of three packages (monorepo speak for subprojects); two Ionic Framework React applications, and a shared React library that will supply a React context each application will use.
Since the beginning, Ionic’s focus has been empowering web developers to build powerful mobile apps with their web skills. To date, we’ve helped millions of devs build mobile apps with web tech, collectively powering more than 15% of the public app stores.
Many web development teams have been successful with this approach. But, with a new project we’re working on, we think there’s a way to bring the best aspects of web development to existing native apps as well.
Today I’m happy to share that Ionic’s starter projects now ship with modern linting, powered by ESLint. This gives us a consistent linting tool across all project types, but also removes a deprecated dependency. Let’s dive in and rewind the clock to 2018.
Now in 2021, the TSLint repo has been archived and the TypeScript-ESLint team, headed up by James Henry and others, have been working to support developers.