What a web app is made of and why it opens fast

A web app is a site built to behave like an app. Here is what it is made of and why it opens fast. I give no loading time and no file size in figures: it depends on the phone and the network.

Théo BeltrameLead Developer Front-end (PWA), 3 min

Photo: Thomas Lefebvre imthebear, CC0. Photo credits

A link and a browser

Everything starts from an address. Your audience taps the link, the browser loads the page and the app appears. No search, no file to download first.

Then one gesture is enough to add it to the home screen. The icon sits with the others and the app opens with a tap.

Four pieces

A web app holds four pieces. The content: your texts, your images, your sessions or your recipes. The interface: the screens, the buttons, the colors. The code: what makes the screens react when they are touched. The hosting: a server that sends all of this on demand.

The content is yours. The hosting is our job.

Think of a cookbook. The recipes belong to the author, the layout is done by the publisher and the printer delivers the book. Everyone has a role.

Why it opens fast

There is little to carry. A native app asks for a download and an installation. A web app sends what the screen needs at the moment it is asked for.

Not everything loads in one block. The app shows what is visible first and the rest arrives after. The home screen does not need next week’s pages.

Finally, the browser keeps in memory what it has already received. On later openings, it has less to fetch.

From link to screen

  1. A linkTapped by your audience
  2. The browserLoads the page
  3. The home screenThe icon is added in one gesture
  4. The next openingIn principle the up-to-date version
No time in figures: speed depends on the phone and the network.

Light images

Images weigh the most in an app. A photo taken with a phone and sent as it is slows everything down.

Before an image goes online, we lighten it: a size suited to the screen, a compact format. To the naked eye you do not see the difference. When the app opens, you feel it.

Keep your originals aside. The app uses the lightened version, the original stays yours.

Code displayed on a computer screen. Photo : Artem Sapegin sapegin, CC0.

Updates

When we fix or improve the app, it happens on the hosting side. The person has no update to accept. In principle, they see the up-to-date version at the next opening.

That is one of the strengths of a web app. A store app follows its own update path, with the store’s review. We can do one or the other depending on your project.

What I do not promise

I give no second and no kilobyte, and the offer contains none. Speed depends on the phone, its age, the network, the place where you are and the time of day.

I can only give the principle: little to load and a browser that remembers. Opening is fast in most cases, though not in all.

If someone tells you the app is slow, send them to us: support for your subscribers is on our side. We look first at their browser and their network, with a screenshot to go on.

You can check for yourself

Open one of our demos on your phone. Close it, reopen it. Do the same with an app you use often and compare by eye, no stopwatch.

Look at what you see on opening: an empty screen, a loading state or the content straight away. Your subscribers will see roughly the same thing, depending on their phone and network.