The key viral feature was using the addressbook to populate the contact list, and you'd lose that, but still be able to implement a bunch of the other stuff. I can't tell from that browserdev page how much of the "widget API" is stuff that you'd need to get bundled up and signed, and how much is just available in the browser.
Either way, this is a pretty developer-hostile move on RIM's part. That's okay, though; all indications are that RIM is capable of developing a large selection of beautiful, compelling, worthwhile first-party apps for the Playbook. A third-party developer ecosystem would really just weigh the platform down.
Comments
I wonder what the feasibility would be of developing a web client for BlackBerry, with long-polling or websockets for the notifications.
http://us.blackberry.com/developers/browserdev/
The key viral feature was using the addressbook to populate the contact list, and you'd lose that, but still be able to implement a bunch of the other stuff. I can't tell from that browserdev page how much of the "widget API" is stuff that you'd need to get bundled up and signed, and how much is just available in the browser.
Either way, this is a pretty developer-hostile move on RIM's part. That's okay, though; all indications are that RIM is capable of developing a large selection of beautiful, compelling, worthwhile first-party apps for the Playbook. A third-party developer ecosystem would really just weigh the platform down.