I'm on macOS and I'm trying to understand the usability decisions behind the close action on some application windows. I have just started terminal:

enter image description here

Nothing to see here of relevance: terminal has been opened, and it's clear in the bottom right of the taskbar that it's running as it has a dot underneath the terminal icon to show that it's running.

Next, I click the close icon at the top left of the window:

enter image description here

As you can see, it appears that, in spite of me closing the window and closing the application, terminal is still running as evidenced by the taskbar still showing the icon showing that it is running.

Why does close not mean close? I have noticed that this functionality is divergent, some applications actually close and some don't.

If I right click on the application and close it, it actually does close.

Why does using the close window button not actually close some applications? If I wanted it minimized, I would have used the minimize button.


2 Answers 2


Document vs App

This has to do with the distinction between:

  • Document windows
  • App windows

Close means close. The only question is whether you are closing a document in a multi-document application, or a singular app window and thus the application itself.

(For more: Human Interface Guidelines for MacOs).

Document window

With some applications it makes sense to have the ability to open more than one window, aka document. Examples include:

  • Word processor
  • Terminal
  • Browser
  • Graphics application

App window

With some applications it doesn't make sense:

  • Calculator
  • Most games
  • FaceTime

Mac vs Windows - Short history

I haven't used Windows for years, but when I did, you had the app window, within which you had the document windows - and the latter could not extend beyond the boundaries of the former:

A music software on Windows XP

This made the whole app vs document windows way clearer: You close the window inside - you close a document; you close the outer window - you close the app.

One problem though - once you could afford a second screen, you had to drag the app window across both screens and organise your documents per screen. This was a MASSIVE PAIN if the two screens did not have the same size/resolution. More so if you had 3 screens.

Mac back then was targeting the creative industries (media, design, graphics), which often used more than one screen. Thus, MacOS did not adopt the document within an app window, but rather an 'it depends' approach.

The caveat? This whole document/window distinction is far more blurry.

You can see more pros and cons of this approach in this wikipedia page on MDI.

It's all quite genius if you look a step further

I doubt Apple weren't aware of the ambiguity and potential annoyance when they made the decision.

But they, as Apple often do, looked one step ahead (this links to usability concepts such as learning curves, progressive disclosure, and performance load). It goes:

  • I close the terminal window with the mouse.
  • Damn! The bloody app is still open.
  • How do I close it?
  • I move the mouse all the way to the menu.
  • I move the mouse all the way to the Quit option (often, bottom menu item = more mousing to be done).
  • Damn! That's a lot of mousing around.
  • Hey, what' this? I can use CMD-Q to close the app.
  • Ah!!! Better use this next time.

And so, from a novice mouse user you become an expert keyboard user. Then you discover CMD-W.

Although I'm a single sample, I was a bit surprised by your question, because I cannot recall ever noticing this - I have been conditioned very early on to use the keyboard shortcuts as means to articulate my goals.

  • 1
    For what it’s worth, that Windows screenshot shows an interface paradigm called multiple document interface or MDI. I think the main distinction for the app closing behaviour is the persistent menu bar, personally, but I don’t have evidence to back that up.
    – Kit Grose
    Commented Sep 5, 2018 at 22:11
  • Thanks @KitGrose I've added the link to the answer - hugely helpful.
    – Izhaki
    Commented Sep 5, 2018 at 22:42
  • I will push back against the conclusion of this answer... I am a near exclusive keyboard user already, and all this does it make matters worse, i.e. shortcuts are for efficiency, and now I have added one more to the list, where one would have done just fine. Commented Oct 23, 2019 at 2:55
  • I think it's also good to keep in mind that some users even after years and years of usage don't get any more proficient
    – Chris
    Commented Jun 2, 2021 at 20:26

As one of the recent Mac users (used previously Linux all my life) and I have to say that for many of the functionalities that I used on Unix OS I did not get dissapointed.

But I have to say that not actually closing an App when you currently press the Close Button it's quite frustrating.

If the decision was made, based on Izhaki's thinking (which it makes a lot of sense and I agree with this logic), it still a very poor decision to make.

If you place a button to close but you actually want the user to close the app with Command+Q why even have the close button at the first place? This decision is just confused and frustrating at the end of it.

But hey, it's Apple, they know everything the user wants, right? ¯_(ツ)_/¯

  • Hi, and welcome to the site! We love to see good answers to the questions (about UX) posted here. To make a question more important, you would up-vote the question, but not add an answer basically agreeing to the question. Commented Apr 18, 2020 at 10:47

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.