Google has started to build its open-source WebRTC software into its Chrome web browser, according to CNET. WebRTC was introduced in May as a new open tech that allows developers to create quick HTML and Javascript APIs for building voice and video chat applications on the web. With WebRTC built into Chrome, users would presumably be able to initiate video chats over Gmail’s Google Talk chat application without the need for installing Google’s plug-in first. “Our goal is to enable Chrome with Real-Time Communications (RTC) capabilities via simple Javascript APIs,” Henrik Andreasson, a Google employee on the WebRTC project said. “We are working hard to provide full RTC support in Chrome all the way from WebKit down to the native audio and video parts.”

Read

In light of a WebKit vulnerability discovered at this year’s Pwn2Own conference in Vancouver, Research In Motion has issued a bulletin for its most security conscious customers. Affecting handsets running BlackBerry Device Software version 6.0 or higher, the exploit could allow an attacker to gain access to data stored on the media card or in the media storage area built into BlackBerry devices. RIM notes that the vulnerability does not grant attackers access to email, calendar, contact, or application store data. Regardless, if you’re reading this with your tinfoil hat on, the company has issued a list of workarounds that can mitigate your risk to the hack. Standalone users can disable JavaScript in their Internet browser — JavaScript is not the root of the problem, but the use of JavaScript is required to execute the vulnerability. BlackBerry Enterprise Server administrators can disable the BlackBerry browser altogether from the BES console — which, as you can imagine, has other implications. RIM has yet to comment on when a more permanent fix might become available, but it has issued a statement saying it is, “investigating the issue to determine the best resolution for protecting BlackBerry smartphone users.”

Read

Add Apple’s iOS and Research In Motion’s BlackBerry OS to the list of victims at this year’s Pwn2Own challenge. Conference veteran Charlie Miller, along with Dion Blazakis, deployed an exploit to iOS 4.2.1 through a vulnerability in Safari. By navigating to a custom-made webpage, the duo were able to execute remote code and gain access to the iOS address book. Vincenzo Iozzo, Willem Pinckaers, and Ralf Philipp Weinmann also utilized a WebKit-based vulnerability to take down a BlackBerry Torch running BlackBerry OS 6.0.0.246. The three researchers noted that the exploit used on the BlackBerry’s mobile OS was difficult to craft due to the lack of documentation, software tools, and resources available. They also noted that most of the operating systems security was achieved via obscurity, and stated that the company was “way behind the iPhone at the moment, from a security perspective.” No conference participants have yet to challenge Google’s Android or Microsoft’s Windows Phone 7 operating systems.

Read

We have been working this one for a while, and we finally got BlackBerry OS 6 for our BlackBerry 9700. Here’s a short walkthrough video we put together. Comparing BlackBerry 6 on the 9700 to BlackBerry 6 on the 9800, we feel that the 9700 runs it better. It is less complicated to use, more functional (at least for us), and above all, faster. It even boots up in around a minute. For some reason, even though this build is not a final build, the phone feels snappy and doesn’t seem to get bogged down like our BlackBerry Torch did. All the great features of BlackBerry 6 are obviously here — WebKit browser, Universal Search, and more — and it’s nice to be able to pamper your beloved aging 9700 sometimes, isn’t it?

A freshly minted post on the official BlackBerry Blog is giving all those interested a more in-depth look at the redesigned BlackBerry 6 browser. As you may or may not have heard, the new BlackBerry browser is based on the WebKit rendering engine and should dramatically improve the browsing experience on BB6 equipped devices. Images and descriptions of the new start page, tabbed browsing, social feed integration, options menu, and browser viewing are all included. Hit the read link to have a look, and let us know what you think.

Read

Salomondrin took BlackBerry’s upcoming webkit browser — expected to debut in OS 6.0 — and ran it through its paces using a BlackBerry 9800 Slider. Salomondrin subjected the browser to several acid tests, the de facto standard for browser performance, and compared the results with the iPhone 4 and the HTC Incredible. Much to the surprise of many a reader, the BlackBerry webkit browser scored 208 on the test and outperformed both the iPhone 4 which scored 185 and the HTC Incredible which scored 151. Salomondrin also put together a nice video review which compares the current non-webkit browser with the upcoming webkit version highlighting the goodness that is to come to the world of BlackBerry. Video is after the jump for your viewing pleasure.

Read

Can’t get enough BlackBerry slider action? Well today’s your lucky day, as a bunch of new images of the handset have leaped out by way of TheBerryFix. Showing off what looks to be a late prototype / early production model, the images give us a pretty good glimpse of not only the handset itself, but some of the new niceties of the BlackBerry 6 OS including a virtual QWERTY keypad, a clone of Cover Flow in the media player, and, of course, the much-hyped WebKit browser. Anyone else excited to see this sucker launch on AT&T during the June/July timeframe? Click on through for a few more pics.

Thanks, Ruffles!

Read

Today, RIM co-CEO, Mike Lazaridis, and Director of Developer Relations, Mike Kirkup, gave us a little taste of what the future of browsing on a BlackBerry will look like…and it’s much better. While the UI is familiar, the rendering accuracy is what really shines through. The browser, which uses the WebKit rendering engine, fully supports HTML 5, still uses RIM’s compression schema for data efficiency, and gets an impressive 100/100 on the Acid 3 browser test. Now, we’re not 100% sure,but…we do see a web ad at about 0:41 in the video that appears to be running in Flash; if you go to live4soccer.com, you’ll see that only Flash advertisements seem to run on that particular spot in the page (middle left). Will the BlackBerry WebKit browser deliver Flash support? We sure hope so. No word from RIM on a release timeline or supported devices, but our connects tell us it is coming relatively soon. We’ve got a video of the browser in action set up for you after the break.

Read

Here’s what we know: we’ve been told the Google Nexus 1 (yes, the Google phone Arrington nailed) will be sold by Google online directly. But that’s also the “first retail channel” and it will be sold by a carrier/s. Apparently the Wall Street Journal is running a story tomorrow saying what we just told you. And heck, we don’t charge subscription fees…

UPDATE: So, we’re hearing Best Buy should sell this as well when it launches.

We hope you Android lovers out there are sitting down, because we’re about to knock your socks off. Android 2.0 hasn’t been released, announced, or even pictured. Until now. And we’re doing it like we’re doing it for TV — major screenshots and major information right here, just for you, our beloved readers.

Android 2.0 looks to be a major improvement in Google’s mobile OS and we couldn’t be more excited about it. From native Exchange support to native Facebook support (it will sync with your contacts), browser improvements, a completely updated Maps application, unified email Inbox — there’s much, much more — and a brand new UI makeover, version 2.0 starts to make Android a really viable (and interesting) platform. Bounce over the jump for all the screenshots and our walkthrough!

Please note: this isn’t the final build of Android 2.0 and the follow reporting is based on the version we have running. Things can and will change prior to release.

Microsoft Exchange compatibility looks to be built-in to the OS now, and the new unified Inbox is perfect for keeping up with your personal and corporate email. You can star (flag for the corporate world) emails, mark multiple as read or unread, delete, forward — whatever you want basically. Emails load effortlessly. Unfortunately (or not so unfortunately) the unified Inbox won’t work with your Gmail account as that uses the specific Google-made Gmail email application in Android.

Maps has been updated to include Layers. We’d imagine this will grow over time but now you can overlay search queries, Wikipedia entries, Latitude buddies, traffic, transit lines, and even load remote My Maps where you can share and receive directions with others. Android 2.0 seems to have some multi-touch gestures built-in like two-finger tapping in Maps, that will zoom in, however, there’s no gesture to zoom out and pinching doesn’t work. © Apple.

The browser has a nice little UI makeover with a redone URL entry bar which includes a Favicon. In terms of performance, no this version we have doesn’t have Flash 10, Google keeps making strides in the browser space. It’s worlds better than anything we’ve used previously on a stock Android OS, and jumps one notch higher than HTC’s customized browser. There is not multi-touch in here as of now, but, you can double tap to zoom in and zoom out which is really all we’ve been asking for since Android 1.0. Oh and did we mention this thing flies? We’re talking ridiculously close to iPhone 3GS web page speeds.

There’s now a YouTube widget you can place directly on your homescreen and that allows for literally two-click YouTube video uploads. You hit record, the video recording app launches, you type in a title and description for your newly-recorded video, and it’s up and away.

While the settings area is roughly the same overall, there’s a lot of interesting additions in 2.0. For starters, there’s haptic feedback built-in and a brand new Accessibility option. There’s also a new option for Text-to-speech and generally with Android 2.0, you’re given more control over the settings of your phone and more opportunities to customize it based on your liking. Something completely bewildering is the fact that if you set a lock code for the phone (seriously give people a choice to use numbers or letters as the passcode), there’s no lock interval option, so each time your phone turns off (about every 30 seconds when not in use), you’re forced to enter the password again on arrival. Lame.

Car Home. What? You don’t know what that is? Ok, it’s a new application that’s meant to be used, uh, in your car. Seriously it’s actually quite nice. It’s a consolidated list of icons that help you perform things (presumably using voice commands if you’re driving). Things like doing a voice search across the internet, getting driving directions, viewing a location on a map, selecting a contact, searching through your phone, etc. It’s very cool that you can say, “map of gas stations” and that will open Google Maps and show you on the map where all the gas stations are closest to you. Not exactly new technology, but hey, we didn’t say it was. We said this was all about pushing Android forward, and it is.

The Amazon MP3 application seems to work over 3G instead of just Wi-Fi now, but whether that is something done because of Android 2.0 or just because of the carrier it’s running on, we’re not positively sure.

Contacts seem to be much more roomy and there’s some great functionality built right in. Instead of hitting the contact and then diving through it to find the contact information you need, just tap the contact’s photo. Up will spring a clean and tidy sub-menu with the pertinent information which can be clicked on. Send someone an email instantly, open up their Facebook profile, or even call them! Very cool and all great things that we love seeing.

Things like the music application and gallery application don’t look to have changed too much, if at all. There also looks to be some more flexibility when defining homescreen shortcuts and things of that nature.

That’s all we have for you today, guys. What do you think of Android 2.0 in its not-final version? We’re loving it. And it could help that it’s running on a pretty bad ass piece of machinery, but hey, that’s for another day.

Wow. That probably sums up everyone at BGR’s initial reaction when we got a heads up that RIM acquired Torch Mobile. Why, might you ask? Well, it goes a lot deeper than this, but all we can see glistening right now are the words “WebKit-based browser”. That would go nicely with some Flash and Silverlight action, eh?

Thanks, Jason!

I want to start this off by saying I have nothing but love for RIM the company. Probably my favorite tech corporation in the world, they’ve created an incredibly unique product that practically replaces the need for drugs for most people. What’s even more fascinating, however, is how RIM (to the pleasant surprise of a lot of us early users) has managed to take a corporate-focused product and service and blow down doors in the consumer world. From the BlackBerry 7100, the first consumer-oriented device, to the eye-catching BlackBerry Tour (it’s business through and through, yet it will be an incredibly popular consumer phone on Verizon and Sprint), it’s clear that RIM has done everything right to this day.

So, what’s the problem you’re asking? They have probably the best back-end infrastructure for mobile communication on the planet, awesome phones that can go head-to-head with high-end smartphones, consumer marketing, a huge consumer fanbase, and practically every businessman (or woman) has one on their hip. One word is where RIM fails so miserably it isn’t even imaginable: software.

You have to look at the big picture here… for what RIM is working with (an incredibly miserable Java OS with so much security and encryption and smoke-blowing APIs) they’ve hit the jackpot. Their OS architecture is fantastic, their use of security is what makes them so trustworthy. But, as each handset release comes closer and closer, people start to see the bigger picture. And that’s the fact that RIM’s OS is more than antiquated, it’s borderline laughable. But it works, you’re thinking, so what’s wrong? I’ve been saying this for years, but it wasn’t designed to do anything the BlackBerry does now. Imagine scotch taping car parts to a 200hp engine and see how far that gets you. Obviously, it’s just a viciously rough metaphor, but we believe a correct one.

There’s so many limitations to RIM’s OS, and even RIM’s data network that it offsets all the wonderful things they’ve managed to accomplish. Remember when people were so excited over leaked shots of OS 4.6 and I said somewhere it was just a theme? Well, was I wrong? Oh, look! OS 5.0! What changed? 99% nothing. Some functionality is added here and there, but the mobile phone landscape has changed so drastically in the last two years, that RIM, admittedly known to planning “three years out” looks to be unable to see the proper direction to head.

You can throw $1,000,000,000 at developers but you won’t get any if your OS, tools, and documentation are so bad, and that’s really in the end a lot of what I’m getting at. I was laying in bed at around 3AM early one morning recently, looking through the iPhone App Store and I came across EA’s Tiger Woods Golf. $6.99, why not? Wait, it’s 150MB? Wow, it must be good. I clicked purchase and literally 4 minutes later, Tiger Woods was installed and up on my screen. Granted I was on a high-speed Wi-Fi connection, but it made me realize more than ever that RIM has the most uphill battle of their lifetimes. When a BlackBerry application over 500k is considered “large”, something’s wrong. When TweetGenius is one of the first BlackBerry applications to do fun, unique things like transparent overlays, consistent shortcuts, and a straight forward UI, something is wrong.

The reason why this is so frustrating to me and I’m guessing many is because RIM literally almost has it all. They’ve got it! They are 90% there but that last 10% has become the most important. If you take Apple for example, and see their shortcomings, and then what they’ve done to fix them, it’s remarkable. It’s a completely different DNA than RIM’s but it’s working. In two years Apple has practically matched Research In Motion in almost every consumer area while having the most advanced mobile operating system with the most advanced mobile SDK on the planet. If Apple can do this in just two years and RIM has stood still, no one thinks that’s a problem?

The reason RIM works is because it’s the entire package, if you will. Hardware, software, infrastructure, corporate integration, security, etc. People want simplicity, ease of use, but more than ever they want more than they need. Stupider people are smarter and expect more, smarter people are stupider and expect more. RIM delivers the same tired package in new hardware and people are starting to catch on. App World? Seriously? From every single developer I’ve spoke to, it’s a non-starter. It basically doesn’t exist to them in terms of a sales channel — it’s practically like 1% if that.

What consumers don’t do is look forward. They look at what’s put in front of them. It’s the exact opposite for the manufacturer and thus why it’s so difficult. Look back two or three years and the Bold and Storm might seem incredibly innovative, consumer-focused, and sure to be hot sellers. And they were and are, but look ahead three years and tell me point blank you have confidence that RIM knows how to steer this ship. I don’t, and that’s being incredibly honest. It’s not me being negative, it’s objectively looking at the landscape and evaluating things. I want RIM to succeed, I want RIM to make kick ass products. I’m just frustrated that RIM is going through hardware like it’s nobody’s business yet fails to deliver on the things that everyone wants. Screw business people, screw consumers, everyone wants a WebKit-based browser. It’s inexcusable RIM doesn’t get it. It’s inexcusable that people put up with a 2003 operating system with so many limitations and restrictions it would make Ahmadinejad jealous. I don’t think RIM is going anywhere, they as a company are incredibly successful, but once they start to lose the consumer market which they worked so hard to get, it’s a downward shift.

Here’s a list of RIM’s models followed by Apple’s in the last 3 years:

RIM: 8110, 8120, 8130, 8800, 8820, 8830, 8300, 8310, 8320, 8330, 8220, 8230, 8900, 9000, 9500, 9530, 9630.

Apple: iPhone, iPhone 3G, iPhone 3GS.

There’s a good and bad part with knowing things in advance. For instance, people might hold off on purchasing a new BlackBerry if they know a newer and better one is being released in a couple months, and this hurts a company’s current product cycle. On the other hand, if someone on Verizon sees a Tour being released two months from now, they might rethink jumping ship or switching to a different device on Verizon. And the cycle continues. Looking at RIM’s upcoming products for the next 6-12 months is simply a rehash of current limitations and shortcoming in smaller and sexier packages. The BlackBerry 9020? It’s a Bold in a smaller, sexier package. Nothing else is different. The BlackBerry Storm 2? It’s the same device with maybe improved screen tech. The BlackBerry Magnum? As hot as a hybrid touch screen/QWERTY device would be, it’s still a BlackBerry that can’t pull up a webpage to save its life or play a real game or have any sort of desktop-class application running.

These things won’t change, the core OS hasn’t changed, and RIM has had no reason to change it. Why mess with success, right? Well, if you happen to be Research In Motion, you might have to start changing things up or newer and better operating systems like the iPhone, webOS, and Android are going to eat their lunch and their applications, too.

I’m fortunate enough to be able to have every phone I want on every carrier and that gives a person an incredible amount of clarity when picking the superior products. I use an iPhone 3GS and a BlackBerry Bold everyday, both on AT&T. But to tell you the truth, in the past when people ask me what device would I choose if I had to only pick one, it would hurt my brain. There was just no way to choose. But unfortunately or fortunately, that decision has become clearer and clearer. I don’t think I’ll ever give up my BlackBerry, I’m pretty sure you’ll always find one on my hip in an OEM RIM leather holster, (yes, holsters are cool as shit) but when me of all people starts truly questioning how a company as successful and brilliant as RIM is going to keep up with the next 2-3 years, you’ve got a big, big issue.

I’ll close by saying that the market is still wide open and this doesn’t mean RIM is or ever will go anywhere. It’s just something to keep an eye on and see how the best to ever do it will react to competitors’ advances, innovations, and of course, their software.

Steve Ballmer has been all over the globe lately. First, he was in South Korea teaming up with LG for a future with Windows Mobile in LG smartphones. This week, he made his way to Australia with those loud, powerful and rather obnoxious words, “Developers, developers, developers!” But the excitement died down quickly when a student at Power to Developers event asked, “Why is IE still relevant and why is it worth spending money on rendering engines when there are open source ones available that can respond to changes in Web standards faster?” Ballmer’s response was that the question was “cheeky, but a good question, but cheeky”. Right, that’s when you know you’ve struck a nerve. After treating the crowd to his usual rant about looking to and anticipating the future, all Ballmer could really say about open-source browsers was that they are “interesting.” Very similar to his feelings about Google’s Android platform.

Open source is interesting. Apple has embraced Webkit and we may look at that, but we will continue to build extensions for IE 8.

So it looks like Microsoft is probably going there, but not all the way there. Catch the drift? Even then, if Microsoft were to show an iota of interest in open source engines like WebKit, it could be huge news for third-party developers and in turn, to end users. We’ll have to wait and see where Microsoft is going with this, but don’t go thinking they’re ready to open up and embrace open source quite yet.

Read

Ok, maybe that’s not the best analogy since SquirrelFish isn’t illegal. With performance figures like this however, competing mobile browsers may wish it was. WebKit, the driving force behind “real web in your pocket” browsers such as the S60 Browser and Apple’s mobile Safari, has just received a new juiced-up JavaScript interpreter that bumps efficiency up considerably. Codenamed SquirrelFish, WebKit’s new interpreter is a whopping 60% faster than its predecessor as displayed by the graph above showing the results of SunSpider JavaScript benchmark tests. From the announcement:

SquirrelFish is a register-based, direct-threaded, high-level bytecode engine, with a sliding register window calling convention. It lazily generates bytecodes from a syntax tree, using a simple one-pass compiler with built-in copy propagation.

Right then. All you really need to know is that once future builds of WebKit are incorporated into your mobile browser of choice, JavaScript performance is going to be a heck of a lot faster. SquirrelFish is also just the first step in a series of enhancements. Juice it up fellas!

Read