Over a million developers have joined DZone.
{{announcement.body}}
{{announcement.title}}

Why I am Starting a Hybrid Development Accelerator

DZone's Guide to

Why I am Starting a Hybrid Development Accelerator

· Web Dev Zone
Free Resource

Learn how to build modern digital experience apps with Crafter CMS. Download this eBook now. Brought to you in partnership with Crafter Software

I often get the question, “why the focus on hybrid development for your accelerator?” This question has come up more and more as Mark Zuckerberg said that Facebook’s focus on HTML5/hybrid development was a mistake.

As I argued over a year ago on this blog, it is mistake to bet exclusively on native or hybrid since some Apps will call for a native approach and some will call for a hybrid approach. Projects that need maximum performance and hardware interaction will require a native approach (medical scanning/rendering apps and some games come to mind) and projects that require larger reach and very fast time to market require a hybrid approach. Each approach has its limitations and trade offs.

If I advocate both approaches in a developer’s toolkit, why would I be starting the world’s only Hybrid Accelerator? The reason is that a startup should never, ever, go native. The very nature of a startup is that you have no money and require a super fast time to market. Just last week at a startup networking event in Hong Kong two super cool startups showed me their native apps on their iPhones. They then asked me what I thought of the app. I said: “your app sucks since over 75% of the smartphone market can’t use it, myself included as an Android user.” They countered: “we have no money, so we choose one platform to build the prototype on.”

My advice for them and most startups: For your prototype and V1 release you should go hybrid. You will have a much broader reach and won’t have to maintain two or more codebases (and double the programmer staff.) You’ll save time and money. Once your company matures and you have lots of users and the money to spend on the development, then you should consider going native if you are bumping into the limitations of hybrid development (chances are only a small percentage of apps ever will).

What about a company with 1 billion users, over $1b in profits post-IPO, and a super slow API in the first place? Yes, Mark Zuckerberg proves my point, hybrid development helped Facebook get to market fast with its hybrid mobile app. It was not a mistake for Facebook to go to market fast and cheap with a hybrid app. The mistake Zuckerberg made was not deploy some of those profits to build a better hybrid or go native years ago.

 

 

Crafter is a modern CMS platform for building modern websites and content-rich digital experiences. Download this eBook now. Brought to you in partnership with Crafter Software.

Topics:

Published at DZone with permission of Stephen Forte, DZone MVB. See the original article here.

Opinions expressed by DZone contributors are their own.

THE DZONE NEWSLETTER

Dev Resources & Solutions Straight to Your Inbox

Thanks for subscribing!

Awesome! Check your inbox to verify your email so you can start receiving the latest in tech news and resources.

X

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}