AI UX PlaygroundNewsletterJoin 2K+ AI designers and PMs on Substack. New teardowns, patterns, and prompts as they drop.

UX design

Length Expansion Stress Test

Stress-test key screens for text expansion and identify where UI breaks with longer translations.

Prompt

Run a length-expansion stress test for this UI.

Context:
- Product/feature: [name]
- Key screens/components: [list]
- Target expansion factor: [30% / 50% / 70%]
- Target locales: [list]

Inputs:
[Paste UI copy, screenshots/links, and component constraints]

Provide:

1. High-Risk Strings
   - Strings most likely to expand significantly
   - Strings with variables/placeholders that can expand unpredictably

2. Breakpoints & Failure Modes
   For each screen/component, identify:
   - Where truncation will occur
   - Where wrapping will create layout shifts
   - Where buttons/inputs/nav items will overflow
   - Where table columns/cards will break

3. Recommended Fixes
   - Copy alternatives (shorter phrasing, remove redundancy)
   - Layout fixes (wrap rules, flexible widths, max-widths, responsive stacking)
   - Component fixes (icon-only variants, adaptive labels, overflow menus)
   - When truncation is acceptable vs not (and tooltip/expand patterns)

4. Test Cases
   - A checklist of ?strings to test? + ?screens to verify?
   - Suggested pseudo-localized examples (optional)

Format as a screen-by-screen punch list with recommended fixes.

How to use

  1. 01

    Replace [name], [list], [30% / 50% / 70%], and [list] with your specific details

  2. 02

    Gather your UI materials: Collect UI copy, screenshots, and component constraints for key screens

  3. 03

    Replace [Paste UI copy, screenshots/links, and component constraints] with your materials. If you have screenshots, upload them

  4. 04

    Add context before the prompt: Describe your product and expansion factor. Example: "Product: Dashboard. Key screens: Header, Sidebar, Main content. Expansion factor: 50%. Target locales: German, Spanish."

  5. 05

    Paste the modified prompt into your preferred AI tool, like ChatGPT or Claude (preferably with vision if using screenshots)

  6. 06

    Review the stress test results: Check high-risk strings, breakpoints, and failure modes

  7. 07

    Apply recommended fixes: Use the suggested copy alternatives, layout fixes, and component fixes

  8. 08

    Create test checklist: Use the test cases checklist to verify fixes in actual translations

  9. 09

    Export to tracking tool: Copy the screen-by-screen punch list to your project management tool

Tips

  • Specify expansion factor: Mention "50% expansion" (typical for German) or "30% expansion" (conservative) based on your target languages
  • Include key screens: Focus on most important screens (checkout, onboarding, main flows) for targeted stress testing
  • Request pseudo-localization: Ask "Suggest pseudo-localized examples" to test with mock translations
  • For long strings: Pay special attention to strings with variables/placeholders as they can expand unpredictably
  • Combine with i18n audit: Use this stress test alongside the i18n readiness audit for comprehensive localization coverage