native vs. hybrid applications

Native vs. Hybrid Apps@cihadhoruzoglu

Cihad HoruzoğluSoftware Architect at CicekSepeti.com

Quick Overview

Native App Development

iOS Android

Native Apps

Pros

● High performance● Native UI elements● Better user experience● Easier access to built in capabilities

Cons

● Needs more than one language● Seperate code base● Timely & expensive development

Hybrid App Development

React Native

Hybrid Apps

Pros

● Quick development● One code base● Low price

Cons

● Low performance● Design● User experience● Depends on third party plugins

5 Questions to ask before you decide

How important is mobile app performance?

84% of users considering performance to be an important factor.

Source: dynatrace.com

Hybrid apps running on HTML and depends on DOM.

“ You cannot build a 60fps scrolling list view with DOM. ” - Flipboard

Do you have enough budget?

Facebook example

If you have enough money and your revenue depends on this app.. Then go for Native!

If you have limited budgetgo for Hybrid.

Do you want to provide the best user experience?

Customer reaction to poor mobile user experience

Source: dynatrace.com

Users will expect a great experience.

They do not care what approach your team decided to take.

Do you need multiple platform right away?

If you have less time to develop multiple platform and you want MVP*, then choose Hybrid.

*Minimum Viable Product

Instagram took two years to develop an Android version.

“We are currently working on making the iPhone experience as solid as possible. Only then will we consider other platforms, but currently we have nothing to announce.” – Instagram FAQs 2010

Do you want to use native features?

If your app is heavy on native phone capability then Native app development will work best.

Hybrid apps depends on 3’rd party plugins and various Android versions.

How to choose

Native Hybrid

Hybrid issues

● More code = More Problem● Android device diversity● Plugin limitations

Demo Time

Questions?

Thanks!@cihahoruzoglu