What is your choice of cross mobile platform? Phonegap, Titanium or Rhomobile? What else do you use?
I am not concerned about the learning curve but powerful one which offers the most features and gives better user experience. iPhone and Android supported well. Potentially allows me to add / fix any known issues myself.
Experienced Trainer, Non-Profit Projects' Manager, IT Professional
Best Answers in: Software Development (7)... see more, Computers and Software (5), Web Development (2), Employment and Labor Law (1), Business Development (1), Public Relations (1), Writing and Editing (1), Career Management (1), Enterprise Software (1), Databases (1), Wireless (1) see less
The best Multiple phone web based application framework which offers the most features is QuickConnectFamily framework
I suggest that instead of evaluating your mobile platform based on supported feature count, you look at what you want to accomplish with your application and make a decision with that set of criteria in mind. You've mentioned, for instance, iPhone and Android support. Do you also need to publish to Blackberry, Windows Mobile, Symbian, and WebOS, or are you fine without them? Is your application resource intensive enough that you need to compile to native code, or can you sacrifice that in order to make productivity gains during development? Are standard user interface elements (text fields, checkboxes, etc.) a must, or is a great, but not-quite-native experience okay? Are you willing to purchase a commercial license for your platform, or is an open license a requirement?
Your answers will be indicators about what platform is best for you. If your app is straightforward and doesn't require many hooks into device-level functionality (calendaring, for instance) Phonegap is a good choice. If you're only devices of interest are iPhone and Android, Titanium's tools are very good and relatively easy to learn. For broad device support and "enterprise grade" hooks, I suggest Rhomobile or Ramp.
For my project, we decided on Rhomobile. We wanted to leverage our existing Ruby skills (and I do recommend you consider the cost of skill acquisition as a factor in your decision), needed to push to a broad base of devices, and had some requirements that would have been difficult to meet with the other frameworks.