Today, it’s typical when searching for mobile development solutions to stumble upon head-to-head comparison articles like Native vs. Cross-platform or Full-Code vs. No-Code, etc., which more often than not showcase common information like performance reviews and feature checklists.
While the above information is certainly helpful, as most enterprise decision-makers know, finding the key information needed to make a strategic decision about which mobile development approach to choose can be a challenge.
That’s why, we thought it would be helpful to put together an article guide that highlights 5 questions you might not think to ask, but should, when it comes to choosing the right development approach for your organization.
The questions we’ve chosen to answer are based on our experiences and conversations with hundreds of IT executives, senior developers, and architects, plus some industry research we thought could be useful in the decision-making process.
Do you use VS Code for Ionic and Angular development? Chances are good that you do. It’s a little app from the unlikeliest of companies that is becoming a big deal.
At its core, VS Code (Code from here on), is a code editor that is free, open source, runs on multiple platforms, and has wide support for most major programming languages and environments.
It goes beyond a simple editor, though, and starts to blur the line between a lightweight editor and a full-blown integrated development environment (IDE). Code is super fast, takes seconds to install, and provides key development features most commonly found in large, commercial IDEs.
One of my favorite features of Code is its vast extension ecosystem. There are thousands of extensions out there built by the community that enhances functionality.
In this post, I’m going to share some of my favorite extensions that can help increase productivity when building Ionic and Angular apps.
Have you ever been on your laptop, late in the evening and just thought, “My eyes sure are tired”? Speaking for myself, this happens quite a bit and I find that the bright white background of most sites tends to be the main cause.
This isn’t just a musing or my own idea, there are studies that show bright whites/bright screens lead to faster eye fatigue. So, it’s no wonder when an app offers a dark theme or a night mode that I tend to enable this feature right away.
As a web developer myself, building and enabling features like this have often meant writing multiple styles and sending down multiple CSS files for both light and dark mode. However, all of this has changed with the introduction of System Wide Dark Mode and even more recently with the introduction of the
prefers-color-scheme media query.
In case you missed it, last week we offered a live walkthrough of Ionic Enterprise Edition, the premier and supported version of everything you need to build native-powered apps with Ionic.
During that discussion, Ionic’s IEE Product Manager, Matt Kremer, and I dug into the top challenges that enterprise development teams face when building mission-critical applications. We walked through each one and discussed how Ionic Enterprise Edition addresses them. If you’d like to learn more, check out the on-demand recording.
The purpose of this post is to go back and address some of the many great questions that we weren’t able to get to in the Q&A session. Some of them are specific to Ionic Enterprise Edition, and some are about Ionic application development in general.
We are excited to announce that our first feature release after Ionic 4.0 is out now! In keeping true to using code names from the periodic table of elements, Ionic 4.1 is named Hydrogen (after the initial release of Neutronium).
We have some exciting new features to share in this release, so let’s dive right in!
Nothing strikes fear into the hearts of developers quite like being told their app is slow. Because of this, great pains are taken to optimize the loading and startup performance in our apps. The techniques we use have changed over the years, but the good news is that a lot of the heavy lifting is now done for us by our frameworks and build systems.
In this post, we will take a look at how lazy loading can be used to help speed up the load times of your Ionic Angular apps. Also, it doesn’t matter if your app is packaged and downloaded from the store, or a progressive web app (PWA) running off a server, lazy loading can help increase your startup times in both situations.
We’re thrilled to have recently announced the release of Ionic’s fourth major version, and its ability to work across all frameworks (or with no framework at all).
We’ve been overwhelmed with the positive feedback, and so far 4.0 has exceeded our expectations of what’s been possible with a rewrite. So, with the official Ionic Framework 4.0.0 release behind us, I figured now would be a great time to lay out our roadmap and immediate plans for next steps—a vision, if you will, for where we hope to take Ionic Framework in the near future…
Today, we’re excited to announce that Ionic React is now available in beta! Take a read below to understand more about this release and how to get started building with Ionic and React.
A Quick History
If you are familiar with Ionic Framework, you more than likely associate it with Angular. Historically, your assumption would be correct, as Ionic and Angular have been exclusively paired for a long time. However, with the recent release of Ionic Framework 4.0 this has changed: Now, Ionic’s core is able to adapt and expand to support many different frameworks. In previous posts, we mentioned that Vue and React were in the works…
Finally, however, we’re thrilled to share that the
@ionic/react beta is here! 🎉
This post is contributed by Kevin Ports, designer and front-end developer at Ionic. He’s passionate about pixels, code, and the space in between.
If you’re building a handful of apps in a startup or small business, delivering a consistent user experience across teams and projects is relatively easy. But if you represent a global corporation with hundreds of developers and designers distributed throughout the world, enforcing a set of design standards can get messy. Having a Design System can help.
A Design System is a centralized library of components that can be shared across teams and projects to simplify design and development while ensuring consistent brand experiences, at scale. In some cases, a Design System is nothing more than a collection of visual design specs. But for the purposes of this post, we’re going to talk about Design Systems as a collection of real-code components that front-end developers drop in their projects like Lego blocks, to quickly build new user experiences without having to worry about the core design of each component.
The HubSpot team, a pioneer in Design Systems, explains why this is valuable:
“That’s the beauty of building a design system. By deciding on a detail once, you free up your entire product development team to focus on solving actual customer problems.”
Of course, for HubSpot, it took 34+ designers and over two years of work to perfect their Design System. For most businesses, that kind of commitment just isn’t feasible.
Enter: Web Components. In this post, I’ll explain the five reasons why Web Components are the perfect way to quickly bootstrap a new Design System, with a future-proof design that will benefit you for years to come.