Slashdot Mirror
iPhone 4 News Roundup
We have a slew of iPhone 4-related stories this morning, so I'm lumping them together for easier consumption/ignoring, depending on your personal feelings on the subject.
Here is a blog entry proclaiming that iOS 4 multitasking sucks and why. Here is a sketchy summary of privacy violations by Apple and AT&T — apparently they are reporting back jailbroken phones. Skunkpost has a story about the lines and sales of the new phone. But the big news of the morning is the reception problems that apparently only affect people who hold the phone in their left hands.
Goatse.
But seriously folks...the new iPhone hardware and many of the additions they are making to the OS are really great...but I'm sorry, I still can't get past the walled garden. Again, I know the app store would have everything I would likely need, but I just can't accept being told that an application would be inappropriate for me to use. And yes, I know I could just jailbreak it...but that's not the point. I don't care that I can get around it, I care that the walled garden exists in the first place. As a consumer, the best I can do is vote with my wallet.
This is only my opinion, I don't speak for others, YMMV, etc applies.
Living With a Nerd
Perhaps Apple (and others) need to shift emphasis back towards the actual calling features of their phones. Who wants a phone that drops calls if you hold it wrong ? It's great that it has new software, etcetc, but any phone I would consider buying needs to include basic features like better than average reception, a decent sounding speaker/mic, and most importantly, does not drop calls if you touch it in it's no-no spot.
The multitasking complaint seems kind of off to me - he complains about the tray being "cluttered" after you go through a few apps because they are automatically added to the tray. But the tray is just four apps wide - how can you have clutter in only four items? And he complains he needs to press and hold to quit an app - but also complains most apps are just suspended. So then why quit an app? It's not doing anything and will be removed if you are low on memory.
"There is more worth loving than we have strength to love." - Brian Jay Stanley
This is a completely nonsensical argument. Apple already have complete control over applications that are available through the app store and, as such, there's no need for technical limitations to prevent people from running such services in the background. I've seen many people claim that Apple's multitasking "sucks," but I've yet to see any convincing argument as to why it would be implemented in such a way for anything other than the reasons they profess!
Apparently the author who wrote about multitasking hasn't actually tried it out yet, because he's off-base. While the app tray does quickly get cluttered, as he mentions, the lack of true multitasking is exactly why this doesn't matter - you can have as many apps down there as you want but they're not actively consuming resources. Where he's really off is in his implication that it now becomes difficult to find your apps to switch back to them. Look, if I'm playing Peggle and then use 4, or worst case 8, apps after switching out of Peggle - mentally I just won't even think to look in the task tray for it anymore. I just can't keep track of every app I've used in my brain. The tray will quickly let me switch back to my most recently used apps, which is really handy - but when I want to switch back to the middle of my Peggle game a week and 20 other app uses later I... and this will sound crazy... click the Peggle icon wherever it's located on my main screens. The author seems to think that the only way to resume an app is from the task tray, and that's simply not true.
Granted, I had some uncertainty about how this would work, too. But I grabbed a new iPhone and tried it out to see exactly how it works, rather than hopping on the interwebs and writing up an article with uninformed assumptions which then ended up on the front page of /.
Additionally, he goes on to say that developers have to explicitly add multitasking. While that's true for using the background services, my understanding (and correct me if I'm wrong folks, as I have this on good authority but haven't actually tried it) is that for the base level of background freezing, which for a majority of apps is all that's really needed, all you have to do is recompile the app against iOS 4. It's not automagic, but it's really not so bad as the author implies. The worst bit about it is submitting to the app store, but it should be pretty painless to get to that point.
Granted, it's not true multitasking. Everyone knows that by now. But frankly, I'd rather the phone always be responsive and maintain its battery life than have true multitasking for the vast majority of the things that I do and have no desire to have to actively manage my apps (which contrary to the author's claims, I don't have to do). Maybe some day I'll change my mind on that. Maybe right now this level of multitasking isn't good enough for many people out there. And that's cool, we have options now - get one of the many excellent Android phones. But please don't write a blog post of inaccuracies.
Well, hello there, selective memory. There are tons of Linux and other articles every single day. The iPhone is a major technology release that has changed phones, so it's going to get stories written about it.
How about you move your cursor to the right side of your window and click the left mouse button on the scroll bar to do what we refer to as "scrolling." By "scrolling," you will move the awful Apple story off of your screen! It's like your very own AdBlock.
From other platforms, we know that is not a major battery drain
The people who make those platforms would beg to differ, Larry Page himself said that poor battery life in android is usually down to multitasking.
This is a completely nonsensical argument. Apple already have complete control over applications that are available through the app store
That's an obvious but wrong response. Apple also wouldn't have to declare any explicit prohibitions on scripting languages, they could just turn down applications, but the resulting uncertainty would be bad for developers. Therefore, when Apple doesn't want unrestricted multitasking, they need to communicate and implement that somehow in a way that doesn't create hazards for their developers.
By defining a specific set of APIs and laying down the rule "no multitasking except through these APIs", Apple gets the restrictions they want, developers get clear rules to follow, and users still get the amount of multitasking Apple is willing to give them. In different words, the existence of these extra APIs codifies business strategy.
If you have another explanation, let's hear it, but Apple's explanation is nonsense. Whatever technical goals Apple says they want to achieve, they could simply achieve through small modifications to their scheduler, if need be, on a per-application basis, with much less work for themselves and their developers.
The lost prototype was camouflaged in an iPhone 3G[s] shell. This non-conductive plastic shell would have prevented the flawed antenna design from being revealed.
"With the iPhone, Apple succeeded in selling a smartphone to consumers by hiding all the complexities of a smartphone like the filesystem and a file manager."
Sure, because managing files is something that millions of PC users have never done before.
Personally, I think that Apple's compromise is a good one. If your app doesn't have a compelling reason to keep executing (like streaming audio, getting GPS updates for navigation, etc.), then the most your app really needs is just to have its state saved for quick re-launch.
The problem with Apple's compromise is that the definition of "compelling" is defined by Apple, while in reality it should be defined by the user. In that sense, the Android compromise is more reasonable - the normal programming model for applications revolves around "activities", which also have lifetime not dissimilar to iOS model - an app switched into background is typically frozen. But an app can explicitly launch a background processing thread - a "service" - if it needs to; and the service can do anything at all (well, apart from displaying UI), not just something that Google has deemed "background worthy".
What I'd like to see on Android, though, is a permission that controls whether an app is allowed to spawn background services, which would be listed alongside others in the confirmation screen when app is installed.
Worthless to 98+% of smartPhone users. Tech folks have a very skewed and unrealistic view of what smartphones are and how they will be used. We techies want our smartphones to do a lot of what our laptops do for us.
Regular users don't want their smartPhone to be a computer. They want it to be a phone that let's them do a few other things. They don't want to have to remember to stop apps so their battery doesn't die in a hour or 2. They don't want complex navigation. They don't want apps that make them constantly reboot their phone. They do want a simple, consistent interface and they want to know that the few apps that they buy/download/acquire will work on their phones. I would be surprised if more than a small percentage of multitasking smartphone users use any multitasking features besides music, messaging and GPS.
Suppose you were an idiot. And suppose you were a member of congress. But then I repeat myself. -- Mark Twain
Sure, because managing files is something that millions of PC users have never done before.
I think you were trying for sarcasm, but instead you really hit the nail on the head there...
Try again. iPhone apps can't call the equivalent even of Windows 3.1 yield(); - they either run in the foreground, or they're suspended - like the DOS 5.0 task swapper.
The few exceptions need to take advantage of a special api call for music, of all things.
If you want a real multi-tasking OS on your phone, you won't get it from Apple. Not this year, and not next year. They're already starting to fall behind in the features race.
Breaking story: If you're visiting YouTube, you've already decided that your time isn't valuable.
Your argument is that because you don't consider something to be valuable to you, it can't possibly be valuable to another person.
I read another article where a guy was mad because he couldn't go switch to something else in the 5-6 seconds while a page loads in Safari (probably while he's driving, too).
Now you're just building strawmen.
To be honest, it seems like you don't get why people would want something, so you don't want them to have it.
Don't get me wrong. I agree that being able to keep Pandora going while I do other stuff is a nicety, but I don't think that something like that is such a "must have" thing that it warrants all of the articles and posts we've seen demanding that Apple make significant changes to the OS and its API in order to make it possible.
Forget Pandora. I want my VOIP app to be able to answer calls even when I'm not actively using it. Of course, I haven't really figured out why they couldn't handle that with push notifications, but the powers that be seem to think it requires multitasking so I'll give them the benefit of the doubt.
Dewey, what part of this looks like authorities should be involved?
"The day Apple makes iPhone available on Verizon, the market for Android devices will take an enormous hit."
Apple should have released it on Verizon 6 months ago. Apple is letting Google's platform become firmly entrenched, and now that hardware manufacturers don't have to write their own OS, they can provide all kinds of interesting handset features. This will rapidly become a PC versus Mac type battle.
The point is, if Apple waits another year to release to Verizon, the impact will be interesting, but it will be too late to have the kind of impact you think.
You were mistaken. Which is odd, since memory shouldn't be a problem for you
Your face is wrong :p
But seriously though.
If you think of the iPhone as an appliance and not a computer, then it makes perfect sense.
I often hear this argument, and my response is always the same: it doesn't matter how you spin it, it doesn't matter what you call it, it doesn't matter what you "think of it as"...the fact is, Apple offers a restricted product while others offer an unrestricted product. I have a choice as a consumer, and I've made one.
Living With a Nerd
In other words, what you want is a smartphone that will confuse the heck out of the average user. Most users are not capable of making an intelligent and informed decision on what apps should be running in the background, particularly since the apps can come from anywhere and aren't necessarily vetted first. The average user will either forbid or allow most background privileges, and therefore will either get no benefit from background processing or wind up with a sluggish phone draining the battery.
I'm not saying that what you are asking is unreasonable, but that it's simply not going to work for most people. Since Apple makes its money selling easy-to-use tech, Apple's not going to make the phone you want.
There is a great deal of value in making things accessible to non-techies, and in order to do that you have to remove a lot of choices. That's simply the way it is. The average user doesn't know enough to make a good decision on many things, and will simply become frustrated when asked an unintelligible question. That's been one of the complaints about Microsoft: UAC, for example, relies on the user to make an accurate technical decision on the spur of the moment with insufficient information.
On a larger system, it's easier to have more choices but to hide them normally. On a handheld, this is a lot less practical.
There are trade-offs here. There is no one right answer. Apple's answer is perfectly valid, and useful for a wide range of people.
"When you have eliminated the unacceptable, whatever is left, however improbable, must be the truthiness" - Holmes
You realize that your entire argument goes down the drain with that one exception?
How about if you wanted to take down notes with your phone WHILE watching said instructive YouTube video?
Point is, people have perfectly legitimate, non-time-wasting reasons to "bellyache" (as you so put it) for multitasking. Don't treat those reasons as unimportant (implicit from your accusation that "they have already decided that their time isn't valuable") just because *you* don't have those reasons.
I hope you don't mind me omitting the trollish end of your sentence. I *do* switch between the web browser and the maps app on my Android phone when navigating on foot to somewhere, with the web browser bringing up the website of my destination (to get address details that the map won't show, e.g. when the destination is inside a mall).
Even though it's one USER task, those are still two PHONE tasks running at the same time. I expect my phone to keep up with me. 5 to 6 seconds is an awfully long time when you're running late.
Needless to say I'm quite glad I've been able to do what I do on my Android long before *anyone* can do it on an iPhone, thanks to multitasking.
Heck my older Nokia 6680 has been doing it way before these new-fangled phones, and I've always found it useful.
I wonder what the obsession is with your kind about BASHING the existence of multitasking on phones.
Pet peeve: Profane people propagating perfunctory pedantry.
Microsoft? Can you install anything you like on a Zune? No. Can you install what you want on an XBox 360? No. Will you be able to install freely on a Kin or other Windows Phone 7 series device? No. Comparing Windows to iPhones is comparing apples and clay bricks.
Apple are NOT falling behind, because only a TINY fraction of users are tech-geeks who "need" full control over their device. The ONLY thing propping Android up is the Google support, there have been other open platforms and they failed. Why? Because the openness is not in demand by the majority of the market. It would not surprise me if the three million iPads sold in three months exceed the total number of Windows-based tablets manufactured since the release of Windows 3 Pen Edition back in the day...
Most people want something that just works. Which is what Apple sells.
You've clearly never had to manage files on a WM phone. A 3.5" screen, even with 480 resolution, is not conducive to intensive file management.
Is it just my observation, or are there way too many stupid people in the world?
"see... if I touch here, it does this.ll but if I let go... look! This thing is messed up!"
I hope I'm not the first to call bullshit on all the reported reception problems. All these iphone owners have a single phone, and widely reported anacdotal evidence of fewer bars when you pick it up isn't fucking science and means absolutely nothing at all. Gizmodo's Jason Chen broke this non-story, and failed to do even the tiniest amount of research which would have yielded that since the inception of cell phone technology, a cell phone that is sitting perfectly still will get better reception that one you are waving around. Also, I'd like to point out that each iPhone release was plagued by false reports of reception problems. It's all bullshit. Yes, I don't doubt what you are rabidly saying, that you lose bars when you pick it up, what I'm telling you guys is that it is known and expected behavior. It's a cell phone. That's one of the things they've always done.
The Admin and the Engineer