Shared publicly  - 
As a response to +Suzanne Alexandra's post about multi-platform frameworks
I posted my thoughts into my blog. My take on the frameworks is from the user's point of view and I think that these frameworks do little good.

Mark Murphy from posted a good and well thought out rebuttal to my arguments to his blog

Let's keep the discussion going!
But then there are the hybrid app frameworks. The idea of a hybrid app is to bring the strong points of each approach into one app. Probably the best known hybrid app frameworks are the PhoneGap and t...
Ramón Medrano Llamas (m3drano)'s profile photoThomas Eichberger's profile photoScott Alexander-Bown (scottyab)'s profile photoJoshwin Greene's profile photo
IMHO Mark Murphy is right, in saying this is not a perfect world and everything's a matter of compromises. But, this stands when you are creating a specialized app, with no competition. A one-off app, an internal app, can be made using one of those cross-platform toolkits. Hey, you didn't even consider Adobe Air, that afaik is much better at platform consistency than those HTML5+JS frameworks.
Still, if you release for general public and have at least one native app as your competition, you can't afford to have such a crappy UX as that offered by those frameworks.
The user wants apps that work, and that can be achieved with web (hybrid) apps. But the user wants to "feel at home" (read: have a consistent UX) and wants his app to feel snappy as well. And that is simply not possible on today's web apps frameworks. Or, tbh, it might be, but I still haven't found one single app developed using web technologies to feel like a native app-
100% agree with this article, web based apps are for the lazy.
In the last two days I have made exactly this point twice. I am also saying that no cross-platform apps are possible right now. With one caveat: At least none that does not invent a completely new paradigm.
Games show it's okay if you choose a completely different paradigm. But then again even games follow more or less established patterns - albeit this time game specific patterns.
One of my comments was to a post by +Davy De Waele - also about Phonegap and Sencha:
+David Kaneda of Sencha Touch replies in this thread - and I think his answer is worthwhile.

Regarding Mark Murphy's answer: Well if all know exactly what they do and decide that given all constraints of a project platform-specific UX-conventions are not that important, than that is fine with me. But my experience is, that management is easily fooled (not seldom by their own assumptions) and tends to believe way too much - and even if they understand, they hope that it might not be as bad as it really is. In these cases developers and users both have to suffer. We cannot blame PhoneGap or Sencha or any other HTML5-toolset for this. But because of this strong warnings like those made by +Juhani Lehtimäki are so important.
The company I'm currently working for is evaluating different frameworks / products. They already made it clear that they don't want to do native development and support multiple code-bases. The required budget for that and the type of app they want to deliver just doesn't justify that cost.

We also feel that Adobe Air seems to be a more mature platform when it comes to cross platform development, and I think we can manage/accept a lower platform UX fidelity as long as the solution performs great and looks great on both platforms. Even native apps (both on iOS and on Android) don't always look / behave in a consistent way.

Another approach might be to start with an html5 bases mobile site (hybrid model) with a limited feature set.

Too many choices, too little time/budget....
I have vested interest in saying that native is better because I'm a native developer and there aren't very many of us.
However, internal corporate software has a long history of being crappy and I don't expect that to change.
There is some data to suggest that enterprise software is getting better with more and more software as a service companies but it's a slow change.

And just because an app in native doesn't mean that it will magically be awesome. There are some horrible native apps and some decent HTML5 apps.

The bottom line is if you are developing a consumer app in a competitive space it better be great and the only way to make a great app right now is with native development.

+Davy De Waele Thanks for tagging me.
Does Mark Murphy not have a G+ account? What's up with that?
+David Shellabarger yeah... it's been noticed in a couple of other posts as well... on the other hand, take a look at his score/activity on stackoverflow. It's amazing he still finds the time to produce all that great Android content.
I really agree with Mark's post. The original post I wrote on the MOTODEV for Enterprise blog was aimed at enterprise customers. One of their key goals is reducing development cost and time in a multiplatform environment where employees bring many types of devices to work. The cost of developing and maintaining multiple native mobile apps is prohibitive. +Vic Gundotra says that even Google can't afford to do that (search on App stores are not the future). If we want Android in the enterprise, we need to help enterprises find solutions. I am very aware of design, as Juhani is. Trust me, it's one of my favorite subjects. :-) But I think that a web app that runs on Android that's almost as good as a native app is better than no Android app at all.
It seems to be very difficult to find real-world examples of such multi-platform apps that follow good design, are feature-rich and are truly multi-platform. Out of the 7 featured apps on PhoneGap, only 2 run on both Android and iOS. The rest is targeting a single platform. The ones that are truly multi platform don't run all that great. The ones that do work are usually very simple apps that should have been mobile sites instead. You see that on the AppStore/Market as well, people notice these things and give bad ratings to those apps. I'm evaluating these things for a big telco that wants to do part internal, part customer facing mobile apps. So far none of those frameworks have convinced me, and I would not want to release these kind of apps to the public. I'm also not convinced of the cost-overhead of doing things in a native way. It all depends on the quality you want to deliver (also as a company in an enterprise context).
Add a comment...