One size fits no one - why mobile development is like buying a shirt
Kathleenholm 2700009BHX Visits (5010)
Ever try on a one-size fits all shirt? It doesn't fit, right? That's because any shirt that tries to fit all bodies will fit none of them perfectly. Well, that's true of our mobile application development needs as well. So when I hear a developer going off like it's a religious argument about what type of mobile development approach is best, I do that little T-shaped hand gesture that says time out!
Native device mobile development has it proponents, as do web-based, hybrid and cross-platform native, but which one is best? The answer should be, it depends. It depends on your target audience, the resources you can dedicate to the application, when your application needs to be released, and what kind of functions you're trying to build in. Does your application target CEOs who only use iPhones? What happens when Android or Windows phone is used? Then make it native. Does your application need to get to market fast to beat the competition and get first mover advantage? Then do it web-based. We believe in the rule of 3's for Hybrid applications. If you plan to run on 3 or more platforms and connect to 3 or more back-end systems, hybrid has a very large appeal. But enough with the true-believer arguments.
Paths are many, truth is one, they say. This little chart seeks to illustrate the considerations for choosing an approach. Notice that there is no perfect approach, each has different pros and cons. Use it to help guide your choice rather than letting the “true-believers” dictate your path.
Our recent acquisition of Worklight is a non-denominational (platform agnostic) mobile application development tool. It’s equally suited to developing native, hybrid and HTML 5 apps. It’s open, light, and powerful. So you can choose the mobile development approach that best fits your needs. And stay out of religious arguments.downloaded with our free developer tools on WASDev.net
Check back weekly for new content.