Ideas

/ Thoughts about new products and digital in general

Native vs Hybrid (continued)

A few weeks ago, I posted on the trade-offs between native, hybrid and responsive approaches to mobile development.    A recent article by Roi Kraus in Techcrunch delves deeper into the subject.  His conclusions are:

  • Choose hybrid which is faster and cheaper to execute if you don’t need native functionality,
  • Go native if you need to use extensive communication, access lots of data or use many of the phone’s onboard components (like graphics, GPS, etc.).
  • If you go native focus on one platform first to avoid managing multiple developments simultaneously,
  • Focus on user expectations rather than business needs in choosing which way to go.

See the whole article here:  From Native To Hybrid App Development And Back

Related Posts
How to make a good first impression on your users ( 19 Jan,2016 )
Native vs Hybrid (continued) ( 20 Nov,2015 )
Are feature requests really UX issues? ( 17 Sep,2015 )
Death by customisation ( 16 Sep,2015 )
Think of the recruitment cycle when retargeting to grow users ( 26 Oct,2015 )
Written by

Leave Your Comment