According to our sources, the 3.0 beta still has some stability and speed issues, so that makes these results that much more impressive. While the overall average gives the iPhone 3.0 beta a 300 percent speed advantage, some of the individual tests show 6x, 8x, or even 11x improvements—the bitwise “AND” function even runs 16x faster than in the current version of Mobile Safari.
Should make the release version of the new, Nitro-powered Mobile Safari 3.0 fairly impressive, come summer! Bring on them multi-app Facebook pages, the iPhone will be ready! (Joking… a bit.)
Of course, we mentioned that on Sprint, lacking simultaneous voice and data, even a million times zero is still zero. Less flippantly, however, when Safari 4 Beta shipped for the desktop with its new ultra-fast Nitro (formerly SquirrelFish) rendering engine, we figured it would only be a matter of time before that scaled down to the iPhone’s version of Safari (based on the same WebKit foundations as desktop Safari, as is the Palm Pre browser and Android Chrome Lite).
Wayne Pan has braved the NDA waters and published JavaScript benchmarks for iPhone OS 3.0, and they are impressive — with results ranging between 3× and 10× faster than iPhone OS 2.2. And I’ll confirm that MobileSafari on iPhone OS 3.0 passes my simple “could be Nitro” recursion depth test.
From what we’ve seen of 3.0, it seems that way to us as well. Along with HTML5, CSS, 2D and 3D animation, anti-phishing, AutoFill, etc., it will be interesting to see what Apple and the WebKit team can pull of by the time iPhone 3.0 launches this summer…
Apple has gotten some much-deserved heat in the past for not adapting anti-phishing measures into their Safari browser. Phishing is when “bad guys” make look-alike websites and try to trick users into entering personal data like passwords or credit cards numbers, so they can be used to break into user accounts or make fraudulent purchases. We’ve had some warnings about MobileMe phishing attacks in the past for example.
Safari 4 Beta on the desktop finally took steps to address this, and it looks like Apple is rolling the anti-phishing alerts out to Mobile Safari as well! As more and more people start using mobile browsers for banking, email, and other security-sensitive tasks, Apple can’t be too careful.
Also of note in the screen shot above is auto-fill. We’re guessing this works like the desktop, automatically entering common data in text fields like name, email address, etc. (Of course, the convenience comes at the expense of the very security mentioned above — balance your usage accordingly!)
Ars Technica has a great article up on the future of web design, involving 2D and 3D graphics and transformations, and what’s most interesting is that it’s the iPhone’s Mobile Safari browser that right now seems to be leading the way in surfacing this next-gen (Flash killing?) goodness for general users:
The WebKit team added CSS Transforms to nightly builds of WebKit back in October 2007, transforms that included scaling, rotation, skewing, and translation in 2D space. As the specification matured, 3D and animation capabilities were added. Eventually, the 3D transforms were broken out into a specification of their own. Though WebKit has had these 3D transform capabilities for some time, only Mobile Safari on the iPhone and iPod touch has them enabled.
Check out some of the other demos, and get the full scoop, over on Ars.
Apple has just released the first public beta of their new Safari 4 web browser for both the Mac and Windows (the Windows version now looking like an actual XP or Vista app). New features include an iTunes/Finder-like CoverFlow visualization for exploring browser history, and Apple TV commercial-esque visual wall of Top Sites (which should cause the same potential pr0nbarassment for some as Chrome and Opera’s “favorite” visualizers in the past), the ability to search, spotlight-like through past sites, Chrome-style top-mounted tabs, robust developer tools… and most important for the iPhone and iPod touch’s future — the new Nitro Engine for screaming fast JavaScript rendering.
Yes, JavaScript engines are the new speeds and feeds. Bottom line, the more script, the slower and heavier the site. Hey, BlackBerry still turns JavaScript off by default on the Bold and Storm to get anything approaching decent rendering speeds. But with Google’s V8 and Firefox’s TraceMonkey helping push the technology — not to mention every Web 2.0 site ladling on the AJAX — we’re going to need all the power we can get, especially on the iPhone.
As for the rest: CoverFlow already works well on the iPhone, though I’m not sure we need it in Mobile Safari, and the smaller screen might make Top Sites a little too tiny to be useful. And the search? Heh. We still need Spotlight on the entire iPhone, so how about we get that rolled up together?
Anything else you want to see in Mobile Safari 3.0?
According to Admob (via TUAW), Apple’s share of the mobile Web is big and might just be getting bigger:
Worldwide requests from Apple devices grew 28% month over month to 1.2 billion in January. Building on its strong December, iPod Touch growth outpaced iPhone growth in top markets. The iPod Touch now represents 40% of Apple requests, up from 20% in September.
People like great mobile browsers that can handle HTML, CSS, and AJAX, who’d have thunk it?
Of course, competing devices from Nokia, Palm, and Google, are beginning to use Apple’s WebKit in browsers of their own, Firefox keeps threatening to push their mobile Fennec client to release status, and RIM is inching the Bold towards usability, so can Apple and the iPhone/Safari team maintain their leading edge?
WebKit is Apple’s open source evolution of the old Linux Konquerer KHTML browser, and it forms the foundation of Safari on both the desktop and the iPhone (and Google Android, Palm Pre, Nokia tablets, etc.). Their Surfin’ Safari blog has just announced CSS animation support, but the better news (via MacRumors), is that iPhone (and iPod touch) Safari already supports both CSS animation and 3D.
Overly provocative headline not withstanding, and while this doesn’t address the ubiquity of Flash video, it should go a long way towards enabling more scalable and open interactivity on the web. (Flash sites don’t always scale well to small screens, after all).
Okay, I’m a web geek, I admit it, but is anyone else excited? Or do we just fear that it will all-too-quickly be perverted into iPhone optimized punch-the-monkey banner ads?
It looks like Apple has begin to approve some 3rd party web browsers for the iPhone. Like the (Jobs save us) “fart” apps that were pulled or pending for a long while only to flood the market on some magic-8-ball decided day, some of these web browsers were biding their time in the App Store approval queue for a good long while according to MacRumors:
Edge Browser (Free) – No loss of screen real estate to the address or navigation bars. Incognito ($1.99) – Now you can browse without leaving a history of any kind. WebMate:Tabbed Browser ($0.99) – Web Mate simplifies browsing by queuing up all the links you click on, then allowing you to view them one by one when you’re ready. And Shaking Web ($1.99) – adds a sophisticated algorithm to compensate small hand shaking to allow for easier reading.
BUT (you did see the big old BUT in the headline, right), those thinking, hoping, praying, or reporting that these are actually alternative rendering engines need to back on up a second. To the best of our knowledge, these are merely different UI implementations of the built-in iPhone WebKit rendering engine, much like those already used in Twitterrific, 1Password, and other long-ago approved Apps. The only difference — that TiPb can tell — is that these are stand-alone iPhone WebKit implementations (like MobileSafari, though more limited due to SDK restrictions and non-default status).
So, no Firefox, Chrome, Opera, or (Jobs save us again!) IE 6 for the iPhone just yet, okay?
Still, for those who want different user experiences and features, well, now you can go get them! Anyone try one yet?
The previous attempt to make an end run around the iPhone’s lack of cut/copy and paste involved shared code called OpenClip and relied on a loophole Apple closed in iPhone OS 2.1
This latest tilt at the text editing windmill targets only 2 apps instead:
Pastebud—as the service is called—works using two bookmarks in Safari. One prepares and loads the page you are viewing, ready to select text at the touch of a finger. From there, you can copy any text you want and create a new mail message with that text in it. In addition to that, you will be able to copy and paste in the text field of a different web page.
Check out the full story and video over at Gizmodo. And then let us know if you think this is enough — for now — to satisfy your cut/copy and paste cravings?
Wired’s blog picked up a story from iPhone Atlas today about a minor MobileSafari browser UI change that sees the (defaults to Google) search box surfaced right on top beside the URL address box (currently it only pops up when the top box is activated to save on vertical real estate). To compensate, the Refresh button gets demoted and tucked inside the refresh box. Not sure about the usability on this change yet…?
The more interesting speculation is about cut and paste, which Wired claims NO specific info on, but offers this as part of the ongoing search for some reason why Apple hasn’t yet implemented this seemingly core functionality:
It’s possible that Apple is taking so long to implement copy and paste not because it is difficult, but because Apple is reinventing it. Imagine a system-wide menu added to all applications which, instead of shuffling items off to a clipboard, lists all the places you can send that file (or text string). This would be like the existing “Open with” option available in the Mac’s right-click menu — each application effectively reports to the OS exactly what kind of files it can handle and the OS remembers this. Thus a picture could be sent to not only the Photo app, but to any other photo program. Text could be sent directly to any open dialog box in, say, Safari.
