6 Comments

Summary:

Here’s a quick — and sad — update to that Torch Mobile story from yesterday. Research In Motion bought the company yesterday, presumably to build its own WebKit browser for BlackBerry devices. While that’s a two-thumbs-up story for BlackBerry owners, Windows Mobile devices are apparently getting […]

irisbrowserHere’s a quick — and sad — update to that Torch Mobile story from yesterday. Research In Motion bought the company yesterday, presumably to build its own WebKit browser for BlackBerry devices. While that’s a two-thumbs-up story for BlackBerry owners, Windows Mobile devices are apparently getting a different finger.

Torch Mobile’s Iris browser, which brought WebKit to WinMo, is no longer under development. James noticed yesterday that all links to the Iris browser were gone. Now I see that WMExperts heard direct from a Torch Mobile spokesperson who states that the company will no longer develop for Windows Mobile or CE. That sounds pretty official — WebKit for Windows Mobile is no more — at least not until someone else takes up the torch.

You’re subscribed! If you like, you can update your settings

  1. BooHoo…IMO they can have it…I tried torch once or twice and really disliked it. I always wound up uninstalling for Skyfire. Real web including Flash. Killed all the other mobile browsers out there.

    1. I’d consider using Skyfire if not for the fact that it fails to take advantage of VGA screens.

      Opera Mobile renders in VGA. So did Iris. Skyfire has no excuse.

  2. The same way I assume RIM killed the rumored Dash Nav iPhone app.

  3. Well, that’s a shame. Iris was a nice browser, and they even integrated mouse pointer support for those pesky navigation menus that only pop up when there’s a cursor above them.

    Oh well, we at least still have Opera Mobile. Take that, RIM!

  4. We all don’t have to worry about WinMo platform in couple of years.

  5. Guess what? Windows Mobile just got another WebKit browser.

    http://www.dorothybrowser.com/

    There’s no stopping the pervasiveness of WebKit…

Comments have been disabled for this post