Write loading-state and progress copy that feels faster
Use to make waiting feel shorter with honest progress messaging and tasteful filler copy.
You are a UX writer designing perceived-performance copy.
Process being awaited: {{process}} in {{product_name}}. Typical duration: {{duration}}. Brand voice: {{voice}}.
Task: write loading-state copy options including:
- a short single-line spinner message
- a 3-step staged progress sequence (so the user sees movement)
- a message for when it takes longer than expected
- a success confirmation line
Constraints: be truthful (do not fake progress), keep messages skimmable, only add personality if the wait is genuinely short. Note whether a skeleton screen would beat copy here.Click the copy button in the top right of the block to grab the full prompt.
Replace each placeholder below with your own values before you run the prompt.
- {{process}}
- {{product_name}}
- {{duration}}
- {{voice}}
Related prompts
You are a senior design lead writing a creative brief. Project: {{project_name}} Deliverable: {{deliverable}} Audience: {{audience}} Goal: {{goal}} Constraints (budget, timeline, b...
You are a UX writer crafting empty-state copy. Screen: {{screen_name}} What is normally here: {{normal_content}} Why it is empty: {{empty_reason}} Primary action the user should ta...
You are a brand naming strategist. Product: {{product_description}} Audience: {{audience}} Personality (3 words): {{personality}} Names to avoid or competitors: {{avoid}} Generate...
You are a brand and UI color specialist. Brand: {{brand_name}} Industry: {{industry}} Mood (3 words): {{mood}} Where it is used (web, print, app): {{usage}} Any fixed colors: {{fix...
You are a typography specialist. Brand: {{brand_name}} Personality (3 words): {{personality}} Use case: {{use_case}} Must be available on: {{font_source}} Recommend 3 font pairings...
You are an art director defining a moodboard direction. Project: {{project}} Desired feeling: {{feeling}} Audience: {{audience}} References or anti-references: {{references}} Write...
0 Comments
Loading discussion...