![]() Because of that, every interactive element has to be large enough for the user to touch it without accidentally touching something else. The problem with mobile devices (excluding notebooks/laptops), is that they come with a touchscreen instead of a keyboard or a mouse. For those that don't, the OS provides a replacement interface. The reason why mobile apps don't have a "close" button, is because there is no need for it.Īll mobile devices are built with a button that fullfills the role of "closing" an app. In this case the answer isn't a close button, it's to design the service better. In the case of services it is possible to gain battery life by closing them, however only very badly designed applications should have services that run with no foreground application and drain the battery life. They are designed to be short lived and shouldn't be open for long before they finish themselves. The application has the option to keep these running when the foreground application closes. Services are separate from the bit of the application that you see (the UI). The exception to this is when applications make use of services. Therefore you will see extremely minimal battery life gain by closing an application. It doesn't use any CPU and the memory it uses will be aggressively cleared whenever the OS needs it. Again, this isn't 100% accurate but you get the idea.Įssentially if you navigate away from an application it is no longer running. If you then relaunch the application which had its memory archived the OS the has the option to unarchive that memory and start the application exactly how the user left it. This then frees up enough memory for other applications to run with no slow down. However, if the operating system needs more memory for when you open a different application it will archive the memory that the older application used (not exactly, but you get the idea). That is because unlike with desktop applications the OS knows that you can't be using it, so why bother keeping it running.Īt this point the memory it was using will still be allocated to it. When you don't have an application on the screen (in the foreground) it no longer takes up any CPU. The operating system manages the memory in a very different way to the way it's done on a desktop computer. It's because of the way Android is designed.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |