playroll

PLAYROLL LAB · R&D

Four experiments, live

Working prototypes with real Plays. Each one shows the options side by side, with a recommended pick. Nothing here is linked from the site.

Faster first Play

The same Play loads three ways at once. Watch what each phone shows first, then compare the timings. Run it on your phone on mobile data for the honest picture.

A. TodaySpinner until it loads
Ready
First picture
·
Playable
·
B. Poster firstCover now, game fades in
Ready
First picture
·
Playable
·
C. Tap to loadCover and a play button
Ready
First picture
·
Playable
·

C loads after A and B have already warmed the cache, so its time is a best case.

A. Today

A spinner until the game has loaded. On a slow phone the first few seconds are an empty screen.

MY PICKB. Poster first

The cover shows instantly, the game loads behind it and fades in. No blank screen, ever. A small change to the feed and player.

C. Tap to load

Nothing loads until the tap. Lightest on data and battery, but adds a tap. Good for the library wall, not the feed.

D. Video preview

Not in the race: a 3 second silent loop per Play in the feed, the real game on tap. Feels the most alive, needs a capture job and storage.

Found in the code today
  1. The background loader starts on every page, Terms included, and loads up to 8 Plays (2 at a time on phones). On the homepage those compete with the first Play.
  2. The first Play in the feed has no cover behind it, so phones see a spinner first.
  3. 3D Plays like Seven Stones pull large files. A poster hides that wait completely.

Recommendation: B for the feed and the player, and run the background loader only on pages that have a feed.