zlacker

Traditionally Windows allowed applications to be either minimized or closed. (AFAIK it still does.) These options might be displayed as buttons in the upper right corner of the window in which the application is running, for example, [-] and [x], respectively. When an application is minimized, it may continue to run in the background. When an application is closed, it does not run in the background.

An exception would be Windows applications that can be "run as a service". This is generally not default behaviour for user-installed Windows applications. It generally requires administrative privileges and manual configuration for each application

https://en.wikipedia.org/wiki/Windows_service

https://stackoverflow.com/questions/3582108/create-windows-s...

https://www.windowscentral.com/how-start-and-stop-services-w...

Unlike Windows, Android does not present an option to close an application while the application is in view. Android applications can be "swiped off" the screen, but they are not closed. By default, _all_ Android applications continue to run in the background. Closing an application in Android requires using a separate app. For example, opening the "Settings" app, then finding the app to be closed in a list of apps, then "stopping" the app by selecting "Force stop" as describeed in the articles above. If the Android user wants to close a number of applications running in the background simultaneously, she is out of luck. They can only be closed serially, one after the other. She must find each of them via the Settings app and Force stop each one, individually. This is extremely tedious and slow and, as one would expect, results in almost all Android users allowing applications to run in the background. The tedium mandated by this design could be purely coincidental.