Page Lifecycle API - Philip Walton

Philip Walton hat einen tiefen Einblick in eine neue API, an der das Chrome-Team gearbeitet hat, um Ihnen (dem Entwickler) die Kontrolle darüber zu geben, wie Sie reagieren müssen, wenn der Browser Ihre Tabs auslädt.

Application lifecycle is a key way that modern operating systems manage resources. On Android, iOS, and recent Windows versions, apps can be started and stopped at any time by the OS. This allows these platforms to streamline and reallocate resources where they best benefit the user.

On the web, there has historically been no such lifecycle, and apps can be kept alive indefinitely. With large numbers of web pages running, critical system resources such as memory, CPU, battery, and network can be oversubscribed, leading to a bad end-user experience.

While the web platform has long had events that related to lifecycle states — like load, unload, and visibilitychange — these events only allow developers to respond to user-initiated lifecycle state changes. For the web to work reliably on low-powered devices (and be more resource conscious in general on all platforms) browsers need a way to proactively reclaim and re-allocate system resources.

In fact, browsers today already do take active measures to conserve resources for pages in background tabs, and many browsers (especially Chrome) would like to do a lot more of this — to lessen their overall resource footprint.

The problem is developers currently have no way to prepare for these types of system-initiated interventions or even know that they're happening. This means browsers need to be conservative or risk breaking web pages.

The Page Lifecycle API attempts to solve this problem by:

  • Introducing and standardizing the concept of lifecycle states on the web.
  • Defining new, system-initiated states that allow browsers to limit the resources that can be consumed by hidden or inactive tabs.
  • Creating new APIs and events that allow web developers to respond to transitions to and from these new system-initiated states.
  • This solution provides the predictability web developers need to build applications resilient to system interventions, and it allows browsers to more aggressively optimize system resources, ultimately benefiting all web users.

The rest of this post will introduce the new Page Lifecycle features shipping in Chrome 68 and explore how they relate to all the existing web platform states and events. It will also give recommendations and best-practices for the types of work developers should (and should not) be doing in each state.

Vollständigen Beitrag lesen.

Mein erster Kommentar ist, dass Sie Philips Post lesen sollten. Es ist unglaublich.

Auf Mobilgeräten kann Chrome beim Hintergrund (Einfrieren oder Verwerfen) der Seite ziemlich aggressiv sein, um Ressourcen zu schonen, wenn der Benutzer sie nicht verwendet (z. B. wenn Sie Tabs austauschen oder aus der Chrome-App auf Android wechseln), wenn der Browser Hintergrund hat Seite als Entwickler Sie haben traditionell keine Kenntnis davon, wenn dies passiert, so dass Sie nicht einfach Zustand beibehalten oder sogar offene Ressourcen schließen können und genauso wichtig, wenn Sie App sind, wieder den Zustand sauber zu hydratisieren. Wenn Entwickler die Kontrolle haben, können sie fundiertere Entscheidungen treffen, was auch bedeutet, dass der Browser aggressiver Ressourcen schonen kann, ohne die Benutzer- oder Entwicklererfahrung ernsthaft zu beeinträchtigen.

Schließlich erklärt das folgende Diagramm alles sehr gut.


About Me: Paul Kinlan

I lead the Chrome Developer Relations team at Google.

We want people to have the best experience possible on the web without having to install a native app or produce content in a walled garden.

Our team tries to make it easier for developers to build on the web by supporting every Chrome release, creating great content to support developers on, contributing to MDN, helping to improve browser compatibility, and some of the best developer tools like Lighthouse, Workbox, Squoosh to name just a few.