The typical definition of multitasking refers to the ability of a microprocessor to apparently process several tasks simultaneously.
As multi-core CPUs entered the market, the "shared computing" of a single processor was then set free to allow for multiple programs to be operating and running applications at the same time. By definition multi-tasking makes computing better, especially if you're a power user. If you are just a regular user, like most people, multitasking should just blend into your work stream in a meaningful way.
It's interesting to note that the human brain cannot fully focus when multitasking, people take longer to complete tasks and are predisposed to error.
Although being able to run multiple programs on any device is a huge productivity win. I love the ability to check my calendar, quickly switch to a browser, go to an email, then go back to the same browser window or calendar without waiting for it to re-load. This to me is the most natural transition from human multitasking to computed multitasking.
So why are so many people fixated on "the true definition" of multitasking on a phone? These are the same people who are constantly closing apps that are running to save battery life. Why should you have to do this anyways? Doesn't it seem insane that you are manually flipping apps on and off to save battery?
Shouldn't that just be automatic without actually shutting down the app thus giving you more battery life? Shouldn't apps that need a running feature (such as an instant messenger) have APIs that allow it to run certain functions in the background seamless to the user?
Someone just messaged me saying they would like the load/sign in/process of one app running in the background while he or she is doing something else on their phone. Another way of looking at this is, why not make the load/sign in/process faster instead?
I've come up with two perspectives to think about multitasking, one from the user experience, the other from an engineer;
A Engineers definition of Multitasking; The ability to run multiple tasks simultaneously or in the background while focussing on something completely different.
An Experience definition of Multitasking: The ability to switch between tasks instantly so I can bridge what I'm working on across multiple app streams or simply focus on something different.
...and while developers may not like the added baggage of complex APIs, maybe they should focus on the user rather than their own time constraints. Think of your customer man, charge more for your software if you feel you're adding a value that is beyond your call of duty!
When you're creating a new device, experience, anything - think about what problem you're trying to solve.
As multi-core CPUs entered the market, the "shared computing" of a single processor was then set free to allow for multiple programs to be operating and running applications at the same time. By definition multi-tasking makes computing better, especially if you're a power user. If you are just a regular user, like most people, multitasking should just blend into your work stream in a meaningful way.
It's interesting to note that the human brain cannot fully focus when multitasking, people take longer to complete tasks and are predisposed to error.
Although being able to run multiple programs on any device is a huge productivity win. I love the ability to check my calendar, quickly switch to a browser, go to an email, then go back to the same browser window or calendar without waiting for it to re-load. This to me is the most natural transition from human multitasking to computed multitasking.
So why are so many people fixated on "the true definition" of multitasking on a phone? These are the same people who are constantly closing apps that are running to save battery life. Why should you have to do this anyways? Doesn't it seem insane that you are manually flipping apps on and off to save battery?
Shouldn't that just be automatic without actually shutting down the app thus giving you more battery life? Shouldn't apps that need a running feature (such as an instant messenger) have APIs that allow it to run certain functions in the background seamless to the user?
Someone just messaged me saying they would like the load/sign in/process of one app running in the background while he or she is doing something else on their phone. Another way of looking at this is, why not make the load/sign in/process faster instead?
I've come up with two perspectives to think about multitasking, one from the user experience, the other from an engineer;
A Engineers definition of Multitasking; The ability to run multiple tasks simultaneously or in the background while focussing on something completely different.
An Experience definition of Multitasking: The ability to switch between tasks instantly so I can bridge what I'm working on across multiple app streams or simply focus on something different.
...and while developers may not like the added baggage of complex APIs, maybe they should focus on the user rather than their own time constraints. Think of your customer man, charge more for your software if you feel you're adding a value that is beyond your call of duty!
When you're creating a new device, experience, anything - think about what problem you're trying to solve.
Comments