Adé Ijidakinro
← Selected work

Roblox / Product research

Did they get
to play?

When players leave early, creators need to know whether they were still waiting to load.

Independent proposal, not affiliated with Roblox.
Not built or tested.

01 / The problem

Leaving before the fun starts

A player who leaves before the tutorial might be bored. Or they might still be loading. I wanted to help creators tell the difference.

“an over a minute loading screen”
A tester describing the wait in MINE.
DevForum · April 4, 2026 ↗
“without awfull asset-stutters”
MINE’s creator explaining why they load assets upfront.
DevForum · April 4, 2026 ↗
“the loadtimes are so long”
Project Zero Stop’s creator describing a similar wait.
DevForum · August 14, 2026 ↗

The supplied proposal singled out these three posts from two discussions within a 100-post review. They suggest a question to investigate; they don’t show that loading caused players to leave.

02 / The research

Why players leave early

I analyzed 90+ posts across 20+ Roblox developer discussions to investigate why players leave before reaching gameplay.

The proposal builds on Roblox’s existing performance charts and custom events.

Roblox’s documentation screenshot of the Performance dashboard, with device counts and server CPU and memory charts.
Roblox’s Performance dashboard. Example shown in its documentation.Source: Roblox Creator Hub ↗

03 / My proposal

Mark when play begins

Add a reusable “ready to play” event and a short report. Creators define what ready means for their game, then compare exits before and after that point. If the event is missing, the report says “unknown.”

Roblox’s Plant reference-game example: a custom event chart comparing harvested plant types across several days.
Custom events already support comparisons. Roblox’s Plant example shows harvests by plant type.Source: Roblox Creator Hub ↗

The tradeoff

Loading more upfront can make play smoother, but it also makes people wait. A useful report must keep that wait separate from problems later in the game.

What I’d test next

Watch 4–6 creators investigate early exits. Compare this report with their current tools and clearer setup guidance. Does it help them choose what to check next, without adding too much work?

Sources & practical limits

Custom events are sent from the server in published games, and charts can take 24 hours to update. A readiness event would need reliable reporting from the player’s device.

The Performance charts require at least 100 daily active users. Roblox’s load-time example excludes server connection and avatar loading, so it is only part of the wait.

The forum sample is small and was selected for relevance. The proposal’s totals were not independently recounted. A later loading-screen change had no measured retention result; freezing while driving was excluded as a later gameplay issue.

Screenshots © Roblox Corporation, reproduced unchanged from its Creator Documentation repository: Performance and Custom Event Graph. See the repository’s CC BY 4.0 license. Sources reviewed October 27, 2026.

← More selected work