Welcome to the Qwik Academy!

Are you looking to become proficient with the Qwik Framework? You've come to the right place.

The Qwik Academy is an independently owned online software development academy where you can learn at your own pace about everything Qwik-related.

This includes the core Qwik framework, the Qwik City meta-framework, as well as anything else related to the Qwik ecosystem.

Table of contents

Who created the Qwik Academy?

My name is Vasco, and I'm the owner of the Qwik Academy.

I have been teaching web development technologies through online courses and blogging since 2016, with a focus on technologies like Angular, Firebase, Typescript, and Node.

In addition to teaching online, I am the owner of a SaaS company in the online course space, OnlineCourseHost.com.

Qwik (started by the creator of Angular and AngularJs Miško Hevery) looks to me like a natural step forward when compared to React, Angular, and Vue.

This is, of course, only my opinion as an early adopter and enthusiast, but let me tell you why. 😉

The goal here is of course not to tell anything negative about other frameworks that I myself also use and love, but just to explain why I think Qwik is truly so different due to its innovative design.

At first sight, Qwik looks and feels a lot like React in terms of developer experience (it uses JSX for example), but internally it works completely differently.

Qwik couldn't have been named better: it's blazing fast!

The most particular aspect of Qwik is that it allows for an almost instant page load time.

Why is Qwik so fast?

One of the reasons for this is that Qwik is server-side rendered (or pre-rendered) by default, out of the box, without you having to install any special libraries or do any special configuration for that to happen.

But that is only a very small part of the whole story.

More important than that, Qwik helps you to minimize the amount of Javascript loaded into the browser, as everything in your code can potentially be lazy-loaded by default.

For example, the granular lazy-loading mechanism of Qwik can go as far as loading the code of a click handler only when that button is clicked for the first time!

And this all happens without you the developer having to do anything special to achieve this fine-grained level of automatic lazy loading.

The framework knows how to split up the code, and takes care of everything for you.

This doesn't mean of course that in production literally everything will be lazy-loaded all the time.

After all, it's still a good idea to bring a certain amount of code upfront that you know for sure you will need every single time.

This just means that it's possible to lazy-load every aspect of your application if you need to, without you having to do anything special to enable that.

It's just part of the framework, it's just how Qwik works.

This means that the Javascript payload of your application does not have to grow as you add more features to it.

The amount of Javascript that you need to load on your initial page load is minimal, and can be served inline in the HTML by the rendering server.

When you load a Qwik application, the application gets first rendered on the server (if you are not using pre-rendering).

The payload will then be sent over the wire to the browser. But no components need to be sent to the browser at this stage.

All you really need is a minimal amount of Qwik startup code, that is automatically included for you by the framework (the Qwik Loader).

The application will then resume itself where it left off on the server, and take over the page.

The Qwik Loader will then take care of downloading the minimal amount of code that it needs from the server to handle your interactions with the page, keeping the Javascript downloaded to the browser to a minimum.

Why I think you will love Qwik too

Besides the speed and the completely new design that enables this type of performance, Qwik has also great developer ergonomics.

From a developer experience point of view, Qwik looks a lot like React, due to its use of JSX and also due to the deliberate choice of using similar naming patterns for some of its APIs, to make it as familiar as possible to the widest number of developers.

This makes Qwik super familiar to React developers, but it's also very easy to understand to any other developer coming from other frameworks.

Qwik has a very minimal API, there are a lot fewer things to learn in terms of API surface.

The Qwik development environment is also super easy to use and blazing fast, making it a joy to develop with Qwik.


So, will Qwik become popular in the web development world?

Time will tell, but I sure hope so. 😉

There is no doubt that the technology itself is indeed a leap forward when compared to the previous generation of frameworks, which is normal as it's a more recent technology.

The developer ergonomics and the API of Qwik are awesome too.  If you are a React developer, you already (almost) know Qwik.

And if you are used to other frameworks, or are looking to learn Qwik from scratch, Qwik will be easy to learn for you too.

So if you are interested in learning more about Qwik, do make sure to subscribe to my Qwik newsletter:

Let me know in the comments below if there is anything that you would like to know about Qwik, and I might just write a post about it. 😉

I'm looking forward to hearing from you.

Vasco Cavalheiro

Web Development Instructor (Qwik Academy and Angular University)

Founder of OnlineCourseHost.com

LinkedIn AngularUniv Facebook  AngularUniv Twitter