CakeMail Logo

Cakemail Blog

Email marketing for small businesses

Mobile Application vs. Mobile web and Where Mobile is Headed

Posted on December 6, 2010
Cedric Dugas

Written by



9 responses to “Mobile Application vs. Mobile web and Where Mobile is Headed”

  1. Great overview of the frameworks. It’s worth pointing out that all of these mobile web frameworks will run quite nicely in PhoneGap:)

  2. Great points in this article, particularly on making your existing HTML sites mobile. I’m actually about to release a very similar one of my own regarding native mobile development vs adobe air mobile development in terms of apps.

  3. Geoff says:

    Great roundup! Although you mentioned JQueryMobile is in Beta – its actually only in Alpha.

  4. Cedric Dugas cedric says:

    Oups! your right Geoff!

  5. Never heard of zepto.js – thanks for highlighting that.

    Couple of points to clarify though:

    ‘Webkit’ isn’t a browser but rather an open source engine for creating browsers. It is used in Chrome, Safari and the Android browser, but isn’t a browser in itself.

    Titanium doesn’t compile HTML and JavaScript into native applications but instead acts as a JS API that links to pre-compiled native objects. What’s the difference? Well a Titanium app will not have the performance of a fully native app nor does it give you full access to the all native API elements. The cross platform thing is a big draw though.

  6. lazukars says:

    There is still a fundamental problem that needs solved when it comes to mobile web development. That is, should developers make one site for both the desktop and mobile space. Or should they create two different sites. One for the mobile experience and one for desktop users. Both have there downfalls

    I personally lean towards the one site approach. However, media queries alone seem to be a bad solution, and UA sniffing is just outright evil.

    I think we are going to see more tools like, server side modernizr, being developed to fill this gap. It all seems to come down to being able to send the viewport size server side, and THEN rendering the page.

  7. Sencha Touch has a free commercial license now ( this happened in November )

  8. […] Blog » Mobile Application vs. Mobile web and Where Mobile is Headed | CakeMail If you don’t live in a cave you’ve probably noticed that there is presently a really a big mobile boom. So it should also be no surprise that a lot of frameworks are popping up to fill this field and make mobile coding less painful. […]

  9. S Woodside says:

    Cedric, we recently asked ourselves the same question — web or native? … our thoughts at

    Basically it seems like for a polished native developer, there are now actual advantages to do some or all of certain apps using web tools instead. There’s not much discussion about this going on in the native community yet but it seems like a useful discussion to have.