Deliverables open faster and hold their pages on refresh

Deliverables now open with less waiting, and the pages you are reading stay put. Opening a deck, a report, or a social graphic used to show blank white pages for a moment before the content arrived, and every refresh or new version blanked them again. Now the pages arrive sooner, each one fades in once its images have loaded instead of drawing piece by piece, and when new numbers land the page you are reading stays on screen until the updated one is ready to take its place. This holds on the deliverable's own page and in the side panel a chat opens it in, and the faster opening applies in the mobile app too.

How it works

• Asked for together. The viewer asks for the deliverable and for its pages at the same time, rather than one after the other.
• Read once, drawn many times. The server keeps what it last read of a deliverable and its latest data, so opening it again, or drawing a twelve-page deck, doesn't fetch the same files once per page.
• One fetch per page. The page thumbnails and the pages themselves share each page, and a deliverable you reopen in the same session draws from what your browser already has.
• New data never blanks the page. After a refresh or a new version, the updated page loads behind the one on screen and replaces it in one step.

Also shipped

• Updating, on the page. While a refresh fetches new numbers, or a new render replaces a video that is already playing, the pages are veiled with "Updating…" until the new ones have drawn, so a change you just asked for is never mistaken for one that didn't land.