Folder moves: choose a destination with confidence

Distinguish the current folder from the chosen destination

ScanGuru marks Folder 1 in a hierarchical destination list and provides Move below it. Documents shows My Files selected while its Move action appears unavailable. Both expose selection, but a checkmark alone can mean either the current location or a newly chosen target. The surrounding labels need to resolve that ambiguity.

Name the current location separately when it helps. If moving to the same folder is not meaningful, explain why the action is unavailable rather than leaving a gray button unexplained. A pending destination summary can stay visible as the person browses. Do not clear a valid selection merely because they open another folder to inspect it.

Use one consistent row behavior. A chevron can indicate navigation while a separate radio selects a folder, or entering a folder can make Move here the confirmation. Avoid combining both models unpredictably. A person should not have to test a row and risk moving the file just to learn whether it opens a subfolder.

Keep parent, workspace and empty-location choices distinct

AlgoApp exposes Folder 1 with a nested New Subfolder option and a naming dialog. Craft offers To Another Space, New Folder and existing folder locations in one move sheet. These interfaces show that a destination is not always just a flat list of folders. It may also involve a different workspace or a location without a folder.

Show enough hierarchy to distinguish repeated names. Two folders called Research are not interchangeable if they live in different projects. A breadcrumb, parent label or current-path summary can provide that context without forcing the entire tree into one small sheet. Keep the path readable as names wrap, and make returning to the parent predictable.

Treat a workspace change as a potentially different operation. It may affect access, ownership or available features. Explain relevant consequences before moving, and do not assume that permission to open a workspace means permission to add content there. A None or Unsorted location also needs a clear meaning: it can remove folder membership without deleting the item.

Create a folder without abandoning the move

Forms for Google Docs places New Folder beside Move while displaying a browsable folder. StudyFetch shows Folder creation successful while its move sheet remains open. That is a useful separation: creating the destination is progress inside the task, not necessarily proof that the original item has moved.

After creation, reveal the new folder and make its pending selection clear. Keep the original item and move request intact. If creation succeeds but relocation fails, report those as separate outcomes. Otherwise a person may create several duplicate folders while repeatedly trying to complete what they believe is one unsuccessful operation.

Validate a name near the field and retain it after a recoverable failure. Define duplicate-name behavior according to the storage system. Do not silently overwrite an existing folder or create an indistinguishable sibling. If creating a subfolder, show the intended parent before commitment so a successful new folder does not appear in the wrong branch.

Retain the item being moved, not only the folder list

iScan shows folder names and file counts with a selected row and Done. Scanner App shows a preview of the document being moved above the destination choices. A source preview can be especially helpful when the task spans several sheets or the person has similarly named items.

Keep source identity visible in the title or a compact summary. For one item, a name and thumbnail may be sufficient. For several, show the count and allow a review of included items without losing the destination. Do not rely on a selection made several screens earlier when the final action can move important content.

Use Done carefully. In a picker, Done can sound like closing a selection screen, while Move describes the mutation. If Done executes relocation, make the heading and pending destination explicit. The same close gesture should not execute a move merely because a folder is selected. Let cancellation leave the item where it was.

Make the final action describe its scope

SCAN ACE names the task Move 1 File and marks the selected memo folder. Scanner Doc uses Move file to... with a selected All Documents location and separate Create folder and Move actions. Their wording exposes an operation and a destination rather than presenting selection as the completed result.

A confirmation can include the item count and destination name when that reduces uncertainty. Keep the action reachable while browsing long folders or entering a new name. If the destination is invalid, unavailable or read-only, explain that state locally before submission where possible. Do not accept a tap that can only fail because the folder is not writable.

After success, identify the confirmed location and provide Open folder or Undo when appropriate. Do not announce success solely because the picker closed. A move across storage providers may require transfer work, while an internal folder move may only update a relationship. The interface should reflect the actual pending and completed states rather than hiding them behind one optimistic toast.

Model relocation against stable item and folder identities

Use stable item and destination identifiers, not the visible folder label or row index. Validate that a folder is not being moved into itself or one of its descendants. Recheck destination access when committing because permissions can change while the picker is open. Keep source and destination state available to explain a rejection without losing the selection.

Define atomicity for a multi-item request. If some items move and others fail, report the actual result and keep failed items available for retry. Repeating a request after a timeout should not create duplicates. A move, copy and transfer should have different operation types even if their destination pickers share the same component.

Keep shortcuts, favorites and shared references consistent with the item’s stable identity where the product supports that. If moving changes link access or ownership, disclose it as part of the operation. Do not claim that a folder relocation is merely cosmetic when the backend actually copies and deletes content across accounts. The UI contract needs engineering confirmation.

Verify that the person can find the item afterward

Move a document into a nested folder, create another destination during the task and cancel a third attempt. Ask the tester to locate each item afterward. A successful task includes a known destination and intact content, not simply a completed button animation. Include repeated folder names and a long path that wraps on a small screen.

Test a deleted destination, revoked access, a source changed on another device and an interrupted transfer. Check whether the last confirmed location remains accurate. If the operation partially succeeds, show which items moved and which remain. A generic error should not force someone to search both locations before deciding whether it is safe to retry.

Review focus when entering and leaving folders, after creation and after the source disappears from the original list. Announce the chosen destination and any unavailable action. Provide accessible alternatives to precision dragging. Count location-selection failures and post-move searches separately from network failures so the product can distinguish confusing hierarchy from unreliable execution.

Review the destination and the result together

Use these checks on a working build, not only on the polished reference state.

• ✓The source item or count remains identifiable throughout the picker.
• ✓Current location, browsed folder and selected destination have clear meanings.
• ✓Repeated folder names include enough parent context.
• ✓Creating a folder preserves the pending move and identifies its parent.
• ✓Cancel never executes a move merely because a folder is selected.
• ✓Invalid destinations and permission changes have actionable feedback.
• ✓Success, partial success and retry expose the confirmed item locations.

Connect relocation to collections and recovery

The saved-items design examples cover how people return to organized content. A destination picker should preserve that retrieval path after moving an item.

Use the mobile error-state examples when designing failed and partial relocation results, rather than sending people back to an unexplained folder list.