Quick answer: Onboarding flows that crash or hang trap new players. A built-in 'skip and report' button lets them proceed while you collect the bug data.
First impressions matter. If onboarding breaks, the player who can still report the bug is salvageable.
Skip button always available
During onboarding, an always-visible 'skip' button. Files a bug; advances player.
Auto-attach context
Skip auto-includes the onboarding step that failed. Engineering knows where; no manual debugging.
Survey on skip
Optional one-line survey: 'what went wrong?' Player's own words; valuable data.
Monitor skip rate
If >5% of new players skip a step, that step has a bug. The rate is the metric.
“Onboarding bugs lose players permanently. Skip + report is the safety valve.”
If your onboarding is more than 5 minutes, the skip+report pattern is non-optional. Plan it.