An unfamiliar screen becomes easier to discuss when you can name the things it shows. Start with a few concepts that travel between different computer environments.
What is being searched, and what would count as a match?
A concept plate, drawn without tying the ideas to a particular operating system or application.
The name points to information.
A file is a named unit of stored data. Its contents might be text, an image, a sound, or information an application uses. The name helps you identify the item; it is not the same thing as the contents.
A file can be shown in more than one place in an interface. A list of recent items, for example, is a way of finding something rather than a complete account of where it is kept.
Keeping those possibilities separate makes later actions easier to describe. “Open the file” is a more specific instruction than “click the thing I saw earlier.”
A location belongs to a larger path.
Folders help arrange files and other folders. A familiar folder name may occur in several places, so the surrounding path can matter when you are trying to identify a particular location.
A useful note describes the relationship: this item is inside a project folder, which sits within another part of the arrangement. The words make sense before a particular button or icon is introduced.
Applications can also present collections, shortcuts, or other views. Read the actual context rather than assuming every visible group has the same role as a folder.
The view and the item are different ideas.
A window is an area where an application or part of its work is presented. It may show a file, a set of items, a task, or another view.
Opening a view
Makes something available to look at or work with in the current environment.
Saving information
Concerns writing the work to storage. The details of when and how this happens depend on the application.
Closing a window
Concerns the current view. It is a different action from deliberately deleting a file.
When an action is unclear, name both the item and the view. That can prevent an instruction about a window from being mistaken for an instruction about the stored material.
Ask what the search is allowed to see.
A search has a scope and a matching rule. It may look through a location, a collection, file names, contents, or information available to a particular application.
A result list is a view of the matches produced under those conditions. An item missing from that list does not, by itself, explain whether the item exists somewhere outside the search.
Those questions are useful across different interfaces. The specific controls can then be read as ways to express the scope and the request.