A small popup opens. It contains a form, several tabs, an upload field and a second popup explaining the first.
At some point, this stopped being a quick interruption and became a modest apartment.
The useful question is whether the task belongs in an overlay, within the existing page or on a page of its own. That choice affects what people can reference, how they recover from mistakes and how comfortably they can finish.
Vitaly Friedman’s March 2026 discussion of modals and separate pages is a helpful prompt to review the decision.1 I would begin with what the person is trying to do, then choose the amount of interruption the task deserves.
Keep a short, connected decision close to its context
A modal dialog requires attention before the person can return to the underlying page. That can suit a brief, self-contained decision directly related to the current work.
Suppose an administrator is about to delete a saved configuration that cannot easily be restored. A confirmation can identify exactly what will be removed and give them a clear way to cancel.
The interruption has a purpose: it creates a moment to inspect a consequential action.
A small edit may also fit a dialog when the person can complete it without needing information hidden underneath. The surrounding page should retain its useful state when the dialog closes.
The button labels matter. “Delete saved configuration” communicates more than “OK.” The person should not have to remember the question after their eyes move to the answer.
Give a larger task enough room
A separate page often suits work involving several decisions, substantial input or information that needs to be saved and revisited.
Planning a new site? See how we approach custom website creation.
When people need to compare, keep the evidence accessible
Imagine creating a custom equipment package. Staff need to compare specifications, check availability and add several items.
A blocking dialog over the product list may conceal the information required to complete the task. If people repeatedly close it to look something up, the layout is interrupting the work it was meant to support.
A dedicated workspace, an in-page editor or an appropriate side panel may provide a clearer arrangement. The choice depends on how much reference material and editing space the task needs.
Consider the return journey too. A separate page should provide a clear route back, preserving relevant filters, selections or draft work where appropriate.
For frequent small edits, reduce unnecessary ceremonies
If staff update many short records in succession, repeatedly opening and dismissing dialogs can become tiring. Inline editing may keep the action anchored to the relevant row.
That still needs clear save, cancel and error behavior. A subtle interface is useful only if people can tell what has changed.
I would observe a representative session before choosing the pattern. One item in a design review can feel effortless. Fifty items before lunch may reveal a slightly different personality.
If this was useful, try The form found a problem. Now help the person finish.
| Modal dialog | Separate page or panel | |
|---|---|---|
| Suits | A short, connected decision, such as confirming a delete that cannot be undone | Several decisions, substantial input or information people need to compare |
| Keep in mind | It hides the page underneath until it closes | People need a clear route back with their filters and place kept |
| Check | Focus moves in and stays inside, Escape and cancel work, labels name the action | Clear navigation, a visible task title and meaningful error recovery |
Check how the chosen pattern behaves
For a modal, keyboard focus should move inside when it opens and remain within it while active. Closing should return focus to the invoking control, or another logical point if the workflow requires it.
Provide an accessible name, an obvious close or cancel control and appropriate keyboard behavior, including Escape. Those details are part of making the interaction usable, rather than decorative work after the layout is approved.
Also check the dialog on a phone with the keyboard open and with enlarged text. Can people reach the action buttons, understand errors and exit without losing work unexpectedly?
A full page needs its own checks: clear navigation, a visible task title, meaningful error recovery and appropriate handling of unsaved changes. More space does not automatically make the process easier.
For either option, try the task with realistic content. Ask someone to complete it, change their mind and recover from a mistake. Watch where they need information the interface has put elsewhere.
The best choice lets people concentrate on the job with a sensible amount of context and interruption. A popup can be helpful. It simply should not require a floor plan.