Linked by Thom Holwerda on Thu 28th Dec 2017 23:36 UTC

Android applications, running on either Android itself or on Chrome OS, pause whenever they're not in focus. While this makes sense on a phone, this doesn't make a whole lot of sense on desktop machines such as Chromebooks. As such, Google is addressing this shortcoming with Parallel Tasks.

With that in mind, the expected behavior of an open app is that it would remain active and running even when the user clicks to another window. Coming from Windows, Linux, or Mac OS, this is what users expect and it is a bit confusing unless you understand what is happening.

Parallel tasks on Android allow the OS to keep everything running and open until you pause the activity or close the app down. Again, with Chrome OS, this is much easier to manage. Just click the "X" on the app and it is closed. Simple.

Nothing groundbreaking in and of itself, obviously, but a hugely important 'feature' to have on a laptop or desktop.

Permalink for comment 652417
To read all comments associated with this story, please click here.
Member since:

Android feels like somebody's gotten up on the wrong foot. Can you remember when the API didn't even have a number-picker even though Google used them all over?

I'm not sure what widget you mean by number-picker, but last time I did android development, it still didn't have an actual number input field. What it had was a text input that you could set to accept only numbers and a decimal separator. Then you write the code to convert between inputted strings and number types (with proper localization of course).

Haven't done any IOS development, but in Android development, everything feels like an ugly workaround.

Reply Parent Score: 3