A few months ago, we wrote about the release of Chrome 70, its slew of new features, and what this update meant for the future progressive web apps (PWAs).
To quickly recap, Chrome 70’s release allowed PWAs to be installed on a user’s device via the browser, much like a native app with new features that improved the user experience. Given that Chrome holds the majority of browser market share, it was an exciting move by a major industry player to add more capabilities that helped inch PWAs closer to the mainstream.
Cut to earlier this month, when Chrome’s latest PWA update dropped in Chrome 72, which added a new feature that opened up the Google Play Store to PWAs as first-class citizens. The news initially broke through a developer’s Medium post, with Google following up a few days later when it published more information about using Trusted Web Activities (TWAs): The newly released feature that allows PWAs to be hosted in its Play Store.
At Ionic, we are big fans of TypeScript and use it in several of our important projects, including Ionic Framework, Stencil, Studio, and AppFlow. We find TypeScript beneficial for a number of reasons, but mostly because it helps us scale our large (and fairly complex) codebases in many areas, including:
- Catching bugs before build time through static type checking
- Providing code completion and refactoring support in many of our favorite editors, like VS Code, WebStorm, and even Vim
We think TypeScript is great, and we think many of our Ionic Angular developers would agree. We have also found TypeScript to be beneficial outside of Angular as well. In fact, we use it in our own AppFlow dashboard, which is a large React app.
Over the past couple of years, TypeScript has started to gain momentum in the React world and, now, has official support in create-react-app. So, we thought it would be helpful to share a little tutorial on how to kick off a new React project using TypeScript.
Navigating the Change with Ionic 4 and Angular Router
This is a guest post from Simon Grimm, Ionic Developer Expert and educator at the Ionic Academy. Simon also writes about Ionic frequently on his blog Devdactic.
In this tutorial we will look at the new navigation system inside Ionic Framework 4.0 to learn how to use the powerful CLI, to understand how your Ionic 3 logic can be converted to v4, and, finally, the best way to protect pages inside your app if you plan to use an authentication system at any point.
Getting ready to kick off your next mobile application project and not sure whether to build a native mobile app or a Progressive Web App? This guide is for you!
At Ionic, we are fans of both traditional mobile apps (the kind you download from the app stores and install on your device) and Progressive Web Apps (PWAs). And, we have the tools you need to build either, or both, types of apps. To help you decide which is better for your next project, we’re going to take a practical look at some of the top considerations for each one. We’ll break it down into four categories: Device reach, app-like look and feel, device integrations, and distribution. Let’s dive in!
When it comes to choosing a cross-platform development approach, it can be difficult to know where to begin. Frequently, we’re asked by teams who are comparing frameworks to explain how Ionic stacks up against React Native, Xamarin, and others in our space.
Often, the expectation is that all of these frameworks work similarly and the decision to choose one is based largely on your current tech stack. For example, choose Xamarin if you like C#/.NET, React Native if you prefer React, or Ionic if you’re an Angular shop.
However, the decision isn’t nearly that simple. And the choice you make carries implications far beyond your current tech stack.
The truth is there are some pretty big philosophical differences that separate Ionic from these other cross-platform tools. We put together a brief guide to walk you through the key similarities and differences.
To keep it actionable, we limited our comparison to Ionic vs. React Native, two of the most frequently compared options. That said, nearly all the distinctions highlighted apply equally to Xamarin or NativeScript. As you’ll see, the real distinction comes down to two opposing worldviews: What we call, Hybrid-Native vs. Hybrid-Web. While we have great respect for these other frameworks, the fact is our approach is very unique. Hopefully, the following guide will help you make the right decision for your next project.
Check out our post, Ionic vs. React Native: A Comparison Guide, in the new articles section of the Resource Center. And, be sure to look out for more practical guides and emerging coverage in this space.
Happy reading! 💙
By now, you likely have heard the news that Ionic 4.0 is here! If you’re currently maintaining an older Ionic app though, you might have concerns about the challenges of upgrading to the latest version. While there will be some work involved to migrate over, there’s never been a better time to do so. Take a look below for some of the benefits of upgrading to Ionic 4.0, plus links to our migration guides to ease the process.
It was almost a year ago at Ng-Conf, when I sat in on a session about TypeScript. One of the speakers that caught my attention was Alex Eagle, a software engineer at Google on the angular-core team, who shared an update about Google’s plan to integrate a new version of TypeScript internally before releasing it to the public.
This was of particular interest to me at the time because I had been working with our architecture team at SpaceX and the adoption of new architecture components had always been a pain point for us. When I discussed this issue with Alex, he explained that his team had been using TSLint fixers (more on those in a bit) to roll out changes to their projects’ code, which got my wheels turning on how I could implement TSLint in my own projects.
Today I am thrilled to announce the 4.0 release of Ionic Framework, lovingly known as “Ionic for Everyone.” 🎉
Ionic 4 represents the culmination of more than two years of research and hard work transforming Ionic from “mobile for Angular” into a powerful UI Design System and app framework for every web developer in the world.
There are so many things to talk about with this release, but first I’d like to talk about how we got here.
Few things in the frontend world are as hot as Design Systems, the idea of building a design spec or library of reusable components that can be shared across a team or company. Design Systems enforce style and branding guidelines, reduce design fatigue for engineers, and consolidate component engineering to one single set of components and a team that builds them. Basically, they help teams manage design at scale.
Smart companies like Hubspot, Salesforce, and Intuit have invested considerable resources in not only building their own internal design systems, but also sharing their knowledge with the rest of the frontend design world.
I’m not going to convince you that Design Systems are valuable since the proof is pretty easy to find. Rather, assuming you agree your company needs a Design System, I want to talk about the hard decisions that need to be made in order to build one.
We’re excited to share with you the results of our second annual Ionic Developer Survey with input from more than 10,000 community members.
The full dataset is available to view here alongside our own insights and analysis.
But before we dive in, we just wanted to say how much we appreciate the community for your consistent support. We think the results of the survey will be valuable for both developers and the vendors featured, and we couldn’t have uncovered these insights without your participation—so thank you!
There was a lot of interesting data to parse through in the results, but our takeaway is clear: Investing in web development, and the skills associated, will pay off for years to come.