The Empty State Every RAXXO Tool Needs Before I Call It Shipped

Description and use

New users see a blank screen that looks broken. By adding a clear reason, a single action button, and removing empty rectangles, RAXXO improved first impressions.

Problem

New users encounter blank screens that look broken instead of informative, causing confusion and anxiety.

Outcome

All RAXXO tools now display informative empty states that guide users, reducing confusion and improving first impressions.

Workflow

• Identify screens that can be empty (first-run, zero results, etc.).
• Write an empty-state script before UI code: state reason, single action, no blank rectangle.
• Seed new projects with starter content where appropriate.
• Create fresh test accounts and walk through first five minutes on phone.
• Use beta testers to screenshot and flag any empty-state issues.
• Iterate until all empty states meet the rule.
• Ship tool with empty states in place.

Evidence

A blank list screen in Git Dojo's early build looked broken, not empty

Source

Every RAXXO tool now ships with a written empty-state script before the first line of UI code

Source

The rule is three parts: say why it's empty, show one action, never show a bare rectangle

Source

I create a genuinely fresh account and walk through the exact first five minutes a stranger would have

Source