3 ms·
Your contention was 2 hours and 40% was outside Apple's standards. I merely demonstrated that it was, in fact, within Apple's standards, as demonstrated by the
by jasonlotito 17y ago
Your contention was 2 hours and 40% was outside Apple's standards. I merely demonstrated that it was, in fact, within Apple's standards, as demonstrated by their own stats.
More importantly, this demonstrates that Flash doesn't kill battery life as propose by Jobs. 5 hours of heavy web usage of heavy flash sites doesn't sound unreasonable.
- stcredzero 17y agoNope. To do that, you'd have to talk about performance strictly under 3G, or you'd have to talk about use under conditions like onboard a plane. There should be different expectations for mobile use. 3G use is already a drain, and you're asking to add another drain on top of that. The question to ask, is how would Flash over 3G do? If we're down to just a few hours of battery life, it doesn't sound attractive anymore.
- jasonlotito 17y agoI disagree. I've already shown that 5 hours of use is acceptable in Apple's world. On top of this, 3G isn't the only available connection. The iPod is completely non-3G, and the iPad has a non-3G variant working just on wireless. Apple's contention was that Flash would destroy mobile batteries. This is clearly not the case. Look at it this way: With Flash, the battery life is 5 hours. With 3G, the battery life is 5 hours. Yes, on 3G, the battery life might be worse, considering you are using both 3G and Flash. But then, where do you draw the line? If 5 hours is acceptable battery life for 3G, if I don't have 3G, could I have Flash and get the same battery life? Finally, that's 5 hours of 3G browsing the internet. Is that 5 hours of streaming video content? I don't know, the website doesn't say. However, the Wired article makes remarks this is party what he was doing, streaming flash videos over a wireless connection. Hopefully that explains it better. Flash clearly doesn't kill battery life. At least no more than 3G does. I think Apple's point of view is partly that 3G offers something you couldn't get otherwise, whereas Flash replicates things already available on the iPhone/iPad platform. Therefore, 3G battery life issues are acceptable, where as, for Apple, Flash is not. And, you can't offer Flash on non-3G variants, because then you know people would want it on the 3G variants.
- glhaynes 17y agoYou're saying that Flash "clearly doesn't kill battery life" but then go on to say it's no worse than 3G... well, yeah, but lots of people have complained about 3G's effect on battery life, and much of the time both features will be used at the same time so the effect on battery life is "stacked". And keep in mind how much Flash you'll be running "unintentionally" doing just normal browsing (on 3G or not) in the form of ads and the like. Flash doesn't only come into play when you're playing Farmville. So this is something that affects a lot of browsing. On that note: how does backgrounding work in Flash Player 10.1? Can I play Flash-streamed audio in the background while I browse other pages (via "tabs") or use other apps? If not, that's one more plus for native apps over in-browser Flash. But if so, what happens if I have 5 different pages open, each with a couple of Flash ads -- do they keep executing in the background?
- jasonlotito 17y agoThose are good questions, and honest concerns. First, yes, 3G does "Kill battery life," but with regard to Jobs and Apple, they made it seem like Flash was something so much worse. While they never compared it to 3G, the sense was that it was a lot worse than it seems to be. Maybe a better approach is to say Flash doesn't kill battery life anymore than other Apple implementations of other technologies. As for the rest of your comment, that's more of an implementation thing. Done intelligently, most of what you are talking about is a non-issue. I'll try to explain. First, Flash doesn't have to run normally. Flash support can be activated. This avoids the torrent of flash ads that can run rampant on websites. However, if I go to a website, and I want to run the application there, I can choose to enable it. Something like this is already done with the YouTube app on the iPhone. You go to a video page, and you click on the Play button, a simple image. In Flash's case, it would explicitly enable the flash player to activate. People do this already in browser. They block flash for the most part, and enable flash in certain, particular cases. As for backgrounding v.s. native apps, that's a non-issue. Native apps will always be better, on any platform. The problem is, not every web app can have a native iPhone app. In your example, the flash web page could be treated like every other web page. In this case, does an HTML5 video continue playing if you open a new tab? Does it keep executing in the background? The idea isn't to recreate the native functionality, but give Flash support so existing media that exists now can be consumed. Media that HTML5 has no support for, and cannot deal with.