Five reasons why native is the right mobile development strategy

Native vs. HTML5: Liferay's Nate Cavanaugh gives you five questions to ask when trying to choose a mobile development strategy.

One of the biggest challenges an organization looking at adopting a mobile development strategy encounters is the choice between native mobile development and HTML5. If it opts for native mobile development, it will need to deliver and maintain software for the four or five dominant mobile platforms on the market today. But embracing HTML5, and employing a browser-based approach to mobile application development, means a less user-friendly system and greater difficulty in providing consistency across platforms.

Both strategies have their strengths and weaknesses. So given the contrasting nature of the two approaches, how does an organization decide which approach to take? In this interview, Nate Cavanaugh, Liferay's director of UI engineering and one of the creators of the powerful JavaScript library AlloyUI, gives five questions that we should be asking when trying to choose between the two competing strategies. And once empowered with answers to these five key questions, organizations will be better suited to make the right decision about the future of their mobile development strategy.

This was first published in November 2012

Dig Deeper on Mobile development and deployment

0 comments

Oldest 

Forgot Password?

No problem! Submit your e-mail address below. We'll send you an email containing your password.

Your password has been sent to:

-ADS BY GOOGLE

SearchCloudApplications

SearchSOA

SearchSoftwareQuality

SearchFinancialApplications

SearchSAP

SearchManufacturingERP

Close