Workflow UX Polish

Use app-native dialogs, prompts, toasts, and disabled-state clarity for launch-critical workflows

Workflow UX Polish

Workflow UX Polish makes ReformCode interactions feel like one intentional product instead of a collection of browser prompts. Critical CODE and REFORM actions now use app-native dialogs, clear destructive-action details, pending states, and global toast feedback.

What Changed

  • Confirmations: destructive or state-replacing actions open branded confirmation dialogs.
  • Prompts: text-entry flows, such as creating a file, use in-app prompt dialogs.
  • Feedback: optimize/analyze failures and successes use toasts instead of blocking alerts.
  • Consistency: CODE, REFORM, history, saved items, snippets, and workspace file flows share the same interaction primitives.

Covered Actions

  • destructive AI proposal apply in CODE/Workspace and Builder
  • current-file optimization in CODE and Workbench
  • workspace file creation and deletion
  • analysis and workspace-session deletion
  • saved developer removal
  • code snippet deletion

Product Standard

Every visible launch workflow should do one of three things:

  • perform the action immediately when safe;
  • navigate to the correct destination;
  • explain clearly why the action is unavailable or requires confirmation.

Native browser alert(), confirm(), and prompt() calls are intentionally blocked by regression coverage for app, component, and E2E source.