• Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

Native Android Application vs. Hybrid Application & the future

 
Gunj Pandya
Greenhorn
Posts: 8
Java
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi,

I have started exploring Android mobile development world. My question is:
With the rise of 'Develop once-Deploy everywhere' mobile app development frameworks like Apache Cordova/PhoneGap, more sophisticated web dev frameworks, and increasing native like performance, what will be the future of Hybrid mobile application development compared to Native development?

What are the main advantages pure Native development have over hybrid approach (not mobile web app dev) besides security and performance?

Looking forward to your reply.
Thanks,
Gunjan
(I've asked the same question out side 'Head First Questions' topic, apologies for the repetition)
 
Ben Allen
Ranch Hand
Posts: 32
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I'm interested in the answer to this. Additionally, how well would the skills gained from this book translate to IOS development? Is it at all similar to Android, or a totally different beast?

Since OP moved the post title, I figure my response should follow as well
 
David Griffiths
Author
Ranch Hand
Posts: 45
5
Android Python Ruby
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hello Gunj/Ben,

This book is specifically Android, some other than some general principles of app design, the truth is a lot of it won't be directly usable for iOS development. An interesting trend (a principle example would be React Native) is to move away from creating apps that are identical on both Android and iOS and to instead use common technologies (in the case of React Native, JavaScript) to create bespoke experiences for Android and iOS users. If that trend continues, it would be useful to become aware to the particular experiences users on the two platforms expect and then create your apps accordingly.

HTH

Dawn and David
 
Piotr Maksymowicz
Greenhorn
Posts: 1
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Well, native approach definitely gives you more opportunities for future development. I think that in the end, native is the way to go, but still, if you don't plan on adding a lot of functionalities to your app etc., hybrid is also a viable option. For some more precise arguments I invite you to read this article - http://howwedostartups.com/articles/Native-vs-Hybrid . Cheers.
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic