Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
1. That is clunkier than just tapping the home button and then double tapping to get the multi tasking bar up. I think my idea would be a much less clunky way of quitting out of an app.

2. That doesn't quit it out of the "multi-task" bar...

I never said it was elegant. It's not intended as an UI feature, rather it's a troubleshooting command to close an app.
Don't take this the wrong way, but "your multi-tasking wrong". :p
By that I mean that your fighting against the way the OS is designed to be used. Your work-flow is counter to what the UI designer expects. Unfortunately for you, this wont be addressed through Apple making it easier to do the 'wrong' thing. Apple has been addressing the issue by making the requirement of killing tasks less necessary in the first place. In the early days of iOS4 I had to frequently kill tasks. These days, I don't.
 
Last edited:
Facebook integration? I highly doubt that. Job's and Zuckerburg fell out over just making Ping work with FB - was that ever resolved? Full on integration will never happen, Apple hate relying on other companies. There is just no way Apple of all companies would do that.

As for the video, I call jailbreak. I think it's probably a White mod too.
 
At 1:26 you can clearly see it says "iP4 64GB" he tries tries to hide it...

And doesn't anybody notice the old Calculator and Voice Memos icon?
 
Last edited:
Apple has been addressing the issue by making the requirement of killing tasks less necessary in the first place. In the early days of iOS4 I had to frequently kill tasks. These days, I don't.

I have to do it more than ever. Infinity Blade's framerate will half without killing all the Apple background apps for example or anything else doing task finishing or keeping the audio playback api open.

Since 4.3 many people have also been finding that the App Store doesn't close it's connection properly and that is a suspected source of battery life dropping like a rock unless it's killed manually immediately after use.

Phazer
 
At 1:26 you can clearly see it says "iP4 64GB" he tries tries to hide it...

And doesn't anybody notice the old Calculator and Voice Memos icon?

I noticed that too, there is no way iOS 5 would have old icons in any alpha/beta version.
 
I have to kill Navigon everytime I use it as well. It will run in the background and continue to navigate and kill my battery if I just drop it to the background. In order to have it stop using my GPS it has to be killed. I would love to see an option to quit an app especially for apps that you don't want to run in the background.
 
I have to do it more than ever. Infinity Blade's framerate will half without killing all the Apple background apps...

I have to kill Navigon everytime I use it as well...

These are issues where the OS and/or apps are not functioning as intended (Arguably Navigon is by design, but it's clearly not 'good' design in this regard).

The discussion is largely philosophical, but I feel that OS development resources are better spent identifying these issues and correcting them. For example iOS5 could implement a 'game mode' that a developer could initiate to set CPU priortiy and free RAM prior to executing (w/o user interaction). Simply implementing a manual task manager is giving up on the issue. It would be nearly impossible to 'untrain' users from depending on a task manager after one is provided.

Would you rather have a great task manger to help you identify your intensive apps and quickly terminate them before launching IB, or would you rather just launch IB and have it run well? The goal should be to eliminate repetitive manual maintenance routines. Even the best task manager implementation would still require a repetitive manual maintenance routine (that's the entire purpose of a task manger).

The work-flow of iOS is not process oriented, it's task oriented. That is to say the user should be thinking of what they want to do next and switch to that task. The user shouldn't need worry about what they were previously doing and what should be terminated before continuing.
 
Last edited:
And, I don't like leaving apps in the background/running because I find despite what Apple claims it does slow my phone down a lot if a lot of apps accumulate and are running (iOS does not do a good job of managing apps on its own imho).

Leaving apps running in the background is multitasking, buddy. So, your entire rant was pointless?
 
Fake or not, I hope they update the notifications system. Almost every app pushes, and it is hard to keep track anymore
 
I never said it was elegant. It's not intended as an UI feature, rather it's a troubleshooting command to close an app.
Don't take this the wrong way, but "your multi-tasking wrong". :p
By that I mean that your fighting against the way the OS is designed to be used. Your work-flow is counter to what the UI designer expects. Unfortunately for you, this wont be addressed through Apple making it easier to do the 'wrong' thing. Apple has been addressing the issue by making the requirement of killing tasks less necessary in the first place. In the early days of iOS4 I had to frequently kill tasks. These days, I don't.

So I am supposed to be able to tell how the UI designer wants me to use my phone? Wait, it's my phone. Shouldn't I be able to use the apps I want?

I tried doing the just let it run and let the OS do its thing. It slows my phone down!!! Am I supposed to be able to read the designer's mind on what apps I should run or when I should run them?!!!

I'm sorry, but it was not implemented well. And even if it was, you do have a point that not everyone is going to use it like they expect. So they shouldn't have some clunky system to manually work around it!
 
...Wait, it's my phone. Shouldn't I be able to use the apps I want?

Of course not! This is Apple.

But this does illustrate the issue that Apple is having. They don't want to require that users manage their processes. To that end they have provided only limited tools to do so.
Many users are accustomed to having to close apps and the idea of relegating this task to OS seems foreign. I would argue that this type of repetitive task is precisely what OS automation should be managing.
I understand that you want to get every last bit of performance out of your device, but as devices get faster CPU's, more RAM and improved API's there will be ever decreasing returns on the investment of manual task mangers.
Outside of a performance sapping bug here and there, most users are satisfied with current iOS performance while multitasking. Apple has little incentive to give up on their goals of a future w/o requiring users to mange tasks.
 
Doesn't look polished enough to be Apple, to be honest. Not even polished enough to be beta from Apple.
 
1. That is clunkier than just tapping the home button and then double tapping to get the multi tasking bar up. I think my idea would be a much less clunky way of quitting out of an app.

2. That doesn't quit it out of the "multi-task" bar. I checked and it still lists it as one of the programs on the multi task bar. I realize that bar is also a list of apps I recently opened. But since I'm never sure which are actually running (except Final Fantasy II which just does not support multi-tasking so if you go to home you lost any progress you've made since your last save. I love you Square but why did you not support that?) and which are just telling me they've been opened before.

that method of quitting isn't for closing an app...it is for force quitting it. It is to be used when the app is frozen and normal closing methods don't fix the issue
 
Until it’s lost in a bar in NYC, I won’t believe it.:)

I’m happy with the way Apple does “multitasking” currently. I’m not sure I’d like it taking over the whole screen like it does in that video.
 
You can get multitasking like this if you jailbreak using a tweak called Multifl0w.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.