The whole team at Nitobi is honored to have been picked as one of 5 companies out of 80 to present at the Launch Pad event at Web 2.0 Expo in San Francisco. I get 5 minutes to convince a panel of judges and the crowd (voting in real-time with sms) that PhoneGap is the hottest technology product launching at the event. It’s described as “American Idol” for business…no pressure;-)
“For 2009, we continue the tradition of showcasing innovative and promising new companies at Web 2.0 Expo. While the definition of a launch has gotten cloudy in this age of public betas, we’re looking for new companies or products that make us take notice. And while venture capital has been the focus in past years, the reality of the market is that companies must gain the attention of customers. So our judging panel and criteria this year focus more on what is essential and transformational in today’s market than on ability to get funded. Along the way, we’re sure the VCs in the crowd will find several startups they’d like to talk to!”
Good luck to the other presenter and I hope we all manage to provide some value or at least entertainment to the crowd.
The event is at 1:15-2:15pm Thursday April 2nd in the Keynote Room (Ballroom - 3rd Level).
I have 2 free passes is anyone is interested. Just leave a comment or email me.
PhoneGap makes building iPhone and Android applications a snap with regular HTML, CSS and JavaScript. XUI is a nifty javascript microframework designed for building mobile web applications. Avoid the heresy of Objective-C or Java and return to the sanity of the open web. In this talk Brian will guide you through the creation of a mobile web app that is app store ready and talk a little about the future platforms for PhoneGap and XUI.
On Friday Darryl Taft of eWeek wrote a very nice post on PhoneGap.
“Nitobi Inc.’s PhoneGap is catching on with smartphone application developers who want to avoid the pitfalls of writing to different phone platforms. PhoneGap is a development framework that lets HTML and JavaScript developers build native mobile phone apps that take advantage of native capabilities of the iPhone, Android and BlackBerry.”
My favorite quote is from a member of the PhoneGap community and developer:
“PhoneGap has cut my iPhone development time in half, which has been good news for my clients.” Nathan Freitas
There was a very nice post by one of InfoWorld’s open source bloggers, Savio Rodriguez, this morning about PhoneGap. It was the last paragraph calling our RIM that really caught my attention though…
“If I worked at RIM, I’d take a trip out to Vancouver to talk to the Nitobi dudes. This framework is exactly what RIM needs to counter the trend of developers targeting the iPhone/iPod as the premier environment for mobile device applications. RIM has the brand and market share to persuade developers that writing once and targeting three key mobile platforms is the best use of a mobile developer’s effort. RIM would need to adopt WebKit as the rendering engine for their browser, but that is going to happen anyway. ;-)”
No doubt Rodriguez! My thoughts exactly. Coincidentally we just got a email from someone at RIM:) We think because easy iPhone/iPod Touch development is the carrot and closs platform is the true long term value in PhoneGap every other mobile platform (Window Mobile, Nokia/Symbian, BlackBerry, Android and Palm Pre) should be bending over backwards to help us get PhoneGap running with their OS and APIs. Maybe they all appear to be laggards today for a reason? ;-) *gloves off*
This morning I watched this discussion of the future of mobile apps with Chris Messian and Ryan Carson. They’ve both done their research on the subject, but as you can tell no one really knows where it’s all going to end up.
Interview with Chris Messina from Carsonified on Vimeo.
I agree with Chris that mobile browsers are going to get more powerful, and we hope we’ll get all the device level features we want from JS down the road. In the meantime PhoneGap will can play that role. Eventually we hope PhoneGap won’t have to exist at least in a compiled sense and just and standard API which may eventually become obsolete. Ah wouldn’t it be nice…
We’re really hoping something like BONDI, or BONDI itself, is the way to go. We’re just not sure if we can be the first ones to adopt it. Is anyone else implementing this?