Last week I was fortunate enough to speak at the latest PhoneGap Day EU in Amsterdam, one of my favorite conferences due to the intimate feeling, access to Cordova/PhoneGap core contributors, and the wonderful city of Amsterdam.
This time around, I talked about practical performance techniques for building native quality web apps (slides here). Before getting into the discussion around current web APIs related to performance, I talked a bit about the history of web-on-mobile, and how quickly things have changed in the last few years alone.
I was boarding my flight from Boston to Madison the other day when my phone buzzed. At first, I assumed it was just another push notification I’ve been meaning to turn off. But it was actually my Delta Airlines app telling me that my bags had just been loaded onto my flight after a tight connection.
Wow, that’s actually pretty awesome.
From an industry that’s not known for delivering great customer experiences, it actually made a big difference to me.
When we asked the Ionic developer community to Become an Ionic Jedi Hackster on May the Fourth, we expected only two – maybe three – developers would have the free time to invest developing and completing an app using the Ionic 3 CLI for this hackathon. The results exceeded our expectations…
Howdy folks! In our last blog post we discussed how to configure an app to lazy load pages. In this post we’ll discuss how to better organize the rest of our app to operate with lazy loading; specifically the UI Components, Directives and Pipes.
Greetings everyone! I’m happy to announce that version 3 of the Ionic CLI is now available!
Since we announced the CLI v3 Beta and our Easter Egg hunt, we’ve seen a large amount early beta testers using the CLI successfully in their Ionic projects. These testers were able to provide some great feedback, as well as get a chance to win a prize! In fact, many of them found our Easter Egg in just a few short hours. More recently, we were able to get even more feedback while devs became true Ionic Jedi Hacksters in our hackathon last week (Stay tuned for results on our Ionic Jedi Hackathon!!!)
Other than the version change, what makes this CLI release special? Let’s take a look at some of the key improvements to the CLI.
One of our priorities at Ionic is making it easy for developers (from indie to enterprise) to go from zero to a fully functioning app with production-ready backend in as few steps as possible. Our developers often tell us that it’s challenging navigating the landscape of mobile-enabled backend services, and they don’t know where to turn after generating and building out the first few bits of their Ionic apps.
Hi there folks! When we were working on release 3.0.0, our main goal was to add lazy loading to the framework and make it as easy as possible. While we are still labeling lazy loading as a beta/non-default setting, many developers who are adding lazy loading to their apps are asking question regarding best practices and examples. I thought this warranted a post on the subject to dive how to set up an app for lazy loading.
Remember when we said this in our Ionic 2.0.0 final blog:
Ionic 3 of course! (…joking!)
Well, we were joking about a completely new framework, but this version change is not for that reason.