01 / OVERVIEW
Your files should be there before you need the internet.
DeskTop explores a familiar tension: people want the convenience of syncing across devices, but they also want to keep working when a connection drops and understand what happens to their files.
I designed a desktop surface for recent files, folders, shared work, activity, and sync status. The next product direction connects that experience to a private encrypted vault and an assistant that helps people work inside their documents.
The design question: how do you make local work feel seamless without making sync invisible?
02 / THE CHALLENGE
Working files move through too many places.
A person may open a spreadsheet or presentation on their computer, make a change, and then wonder whether the right version is available elsewhere. The manual download–edit–reupload pattern is especially easy to lose track of. The larger concern behind the concept is control over sensitive files when cloud storage is involved.
This is a design opportunity, not a claim that current tools never sync automatically. DeskTop asks what a simpler, privacy-conscious workflow could feel like from the desktop.
Keep work within reach
Local files remain available when the connection is unstable or absent.
Show what is happening
People can see whether changes are up to date, in progress, or paused.
Make privacy legible
The product should explain where files go and when the assistant can read them.
03 / DESIGN APPROACH
A small surface with a clear job.
The app is designed as a compact companion to the desktop. Rather than becoming a separate full-screen destination, it keeps recent work close to the files and apps people already use.
Files before features
Recent files take the lead. Folders, the assistant, workspaces, and activity are available in a narrow rail without competing with the file list.
Sync has a visible pulse
The status line distinguishes “Your files are up to date” from “Syncing 34 files,” giving a lightweight signal about the current state.
04 / THE EXPERIENCE
Make the invisible parts of file work visible.
The interface explorations cover the everyday moments around file access: browsing recent work, moving into a shared workspace, checking activity, searching, and pausing sync.
Pause without guessing.
The menu provides 30 minutes, one hour, until tomorrow, and indefinite pause options. A future iteration should make the paused state and the next sync time equally clear in the main panel.
Search by the way people think about files.
The filter exploration groups results by type, including images, documents, spreadsheets, presentations, audio, and more. This broad file scope belongs to this desktop file concept.
05 / THE ASSISTANT
From finding files to working with them.
The assistant is designed as a conversational surface within the file workspace. The supplied screen shows an email request, a response that asks for approval before sending, and visible task progress.
My intended scope for the assistant also includes creating documents, editing their contents, managing spreadsheet files, and making presentations. Those tasks would need specific file selection and review steps in a later design iteration.
Document editing, spreadsheet management, and presentation creation are the intended product scope described by the designer; these flows are not shown in the supplied screen.
06 / PRODUCT DIRECTION
Give sync a destination people can understand.
To support the privacy goal, I would propose a local-first model with an encrypted cloud vault. People edit a local copy; changed files are encrypted on their device and synced when connected. Other trusted devices receive the updated file after they unlock it.
The assistant introduces a separate choice: it should only act on selected files and show changes before applying them. If a task requires an external AI service, the interface must clearly request consent before file contents leave the device.
Edit offline
The working copy remains accessible on the device.
Save a change
The app notices the updated file and shows a pending state.
Encrypt & sync
On reconnection, encrypted changes move to the private vault.
Up to date
A clear status tells the person the latest change is available.
Next design step: show where a file is stored, whether it is available offline, and what the assistant can access. The current PDF shows sync states; it does not show these privacy details yet.
07 / REFLECTION
Trust is an experience people can see.
The designed interface establishes the foundation: recent files, workspaces, activity, search, and sync controls in a compact desktop surface. The more interesting next step is to make the system's promises tangible. People need to know which copy is current, when a change will sync, and whether the assistant is about to modify or share a file.
I would test this direction with three tasks: edit a file while disconnected, return online and confirm its sync state, then use the assistant to propose a spreadsheet change. Those tasks would reveal whether the status language and approval points provide enough confidence.
This is a design concept. The encrypted vault, assistant approval flow, and task testing are proposed directions; no shipped implementation, user research result, or performance outcome is claimed.