Do I need a "close" button in Android applications?

Question

Android

I continue to develop an application that was written by another developer back in 2011, i.e. under Android 2.*, and apparently since then the application has had an application close button.
To date, the application has support for API 15+ systems . Today I removed the program close button, arguing that 99% of modern similar applications do not have this button, I tried to explain that this is how it should be and there should not be a close button. In response, I received a flurry of criticism, they say I'm wrong, it's not convenient, etc.
A quick Google search did not turn up any results, so I turn to knowledgeable people - is this button needed?
I found a similar question for iOS - Do I need a "close" button in iOS applications?

Answer 1

Need not. All phones have a home button - it is the "exit / close". Another thing is that your users may have gotten used to it since 2011. Still from time to time I meet a hybrid output: the presence of this button in the on / off settings.
And somehow you searched badly, this problem began to be discussed back in the same 2011:
https://www.quora.com/Why-dont-Android-apps-have-a...
stackoverflow.com/questions/2033914/ quitting-an-ap...
Actually what one of the Android developers says:

Romain Guy: The user doesn't, the system handles this automatically. That's what the activity lifecycle (especially onPause/onStop/onDestroy) is for. No matter what you do, do not put a "quit" or "exit" application button. It is useless with Android's application model. This is also contrary to how core applications work.

Answer 2

Needed if the application implies some kind of activity in the background. For example, messenger. For such programs, there is a need to cut them out altogether, and not hide them.

Answer 3

Depends on the application. Usually - not needed.
But if it is necessary to unload the application from memory forcibly, then such a button is made.

Answer 4

If you have a ForegroundService, then there should be a button to disable it, if there is no other logic.