Native vs Hybrid - Options to develop your mobile applicationLoic Ortola
Developing a mobile application is always a challenge, as it usually implies multi-platform developments (android, iOS, windows phone).
The question of native vs hybrid makes sense.
This presentation lays out the differences, the concepts of existing solutions, and proposes a matrix of decisions, and elements to make up your mind.
The Great Mobile Debate: Native vs. Hybrid App DevelopmentNick Landry
It’s not easy being a mobile developer. iOS and Android dominate the market, Windows Phone is climbing into third place, and we’re not really sure if BlackBerry still matters. Do you focus on one platform or many? What size of the mobile population do you really want to reach? Each mobile platform comes with its own programming languages, SDKs, IDEs and application lifecycle & architecture. Are we really expected to learn all of this? Isn’t HTML5 supposed to be the Silver Bullet so we can finally write apps once and run them everywhere? This session will demystify all these questions, walking you through the modern mobile ecosystem, and explore your options as a developer. We’ll review the native story on each major platform, discuss the pros & cons of both mobile native and web development, cover some of the cross-platform solutions available to developers, and explore best practices and guidelines to insure a successful mobile strategy. Don’t just blindly pick a side or assume that “one size fits all”, this session covers one of the most hotly contested debates in modern IT. Come join us and be a part of the conversation.
How different is the mobile application development experience? What do we need to know about native mobile application development stack? How different it is compared to hybrid mobile application development? What's the big deal about it? Let's get together and see a comparison between native vs. mobile web browser vs. hybrid mobile apps, following with an introductory to the hybrid mobile application development.
Native vs Hybrid - Options to develop your mobile applicationLoic Ortola
Developing a mobile application is always a challenge, as it usually implies multi-platform developments (android, iOS, windows phone).
The question of native vs hybrid makes sense.
This presentation lays out the differences, the concepts of existing solutions, and proposes a matrix of decisions, and elements to make up your mind.
The Great Mobile Debate: Native vs. Hybrid App DevelopmentNick Landry
It’s not easy being a mobile developer. iOS and Android dominate the market, Windows Phone is climbing into third place, and we’re not really sure if BlackBerry still matters. Do you focus on one platform or many? What size of the mobile population do you really want to reach? Each mobile platform comes with its own programming languages, SDKs, IDEs and application lifecycle & architecture. Are we really expected to learn all of this? Isn’t HTML5 supposed to be the Silver Bullet so we can finally write apps once and run them everywhere? This session will demystify all these questions, walking you through the modern mobile ecosystem, and explore your options as a developer. We’ll review the native story on each major platform, discuss the pros & cons of both mobile native and web development, cover some of the cross-platform solutions available to developers, and explore best practices and guidelines to insure a successful mobile strategy. Don’t just blindly pick a side or assume that “one size fits all”, this session covers one of the most hotly contested debates in modern IT. Come join us and be a part of the conversation.
How different is the mobile application development experience? What do we need to know about native mobile application development stack? How different it is compared to hybrid mobile application development? What's the big deal about it? Let's get together and see a comparison between native vs. mobile web browser vs. hybrid mobile apps, following with an introductory to the hybrid mobile application development.
Hybrid vs Native Mobile App. Decide in 5 minutes!July Systems
Wondering whether to build a hybrid mobile app or a native mobile app? Don’t worry, this presentation will help you decide your mobile app strategy in less than 5 minutes!
Building Hybrid Apps with AngularJS and IonicYounes Adounis
Ionic est un SDK HTML5 puissant qui vous aide à construire des applications mobiles Hybrid en utilisant des technologies web comme HTML, CSS et Javascript.
Durant cette session on verra quand faut it choisir Hybrid au lieu de Native, comment utiliser Ionic et tous ses composants et à la fin on fera un exemple réel d'application Android et iOS pour voir les meilleurs pratiques de développement.
Not all apps are created equal. The type of app that you develop will depend on the features you want and your compatible device preferences. There are pros and cons to each app type, but there is usually a best app for your situation.
The Multiplatform App Architecture offers the possibility to create mobile applications for multiple mobile platforms and at the same time offer the flexibility to use all native functionality of the mobile operating systems to realize an optimal user experience. Combined with a powerful development environment and a comprehensive programming language it offers an excellent way to develop and maintain rich mobile applications.
Capgemini helps customers to achieve mobile excellence and realizes mobile applications in an agile way using this architecture.
Top 4 Cross Platform tools for Mobile App Developmenttechugo
Scope of Cross Platform App Development is bright as developers and engineers find it easy and interesting to use a single code base to compile and deploy their app on all major mobile platforms. Top 4 Cross Platform Development tools are discussed here in the presentation, with few of their major pros and cons:
Hybrid vs native mobile development – how to choose a tech stackJacques De Vos
Choosing the wrong mobile tech stack sets you up for a world of pain. But how do you select the right one from a plethora of current options?
As an iOS developer I am convinced that a carefully designed native app provides the best user experience. So why would we choose Ionic2/Angular2 on Cordova (a bleeding edge Hybrid JavaScript framework) for our latest mobile App? In this short talk I will share our thinking and experiences on the current landscape of mobile stack options.
I will introduce the contenders: Native (iOS and Android) vs Semi-Native (Xamarin and React Native) vs Hybrid (Ionic2/Angular2 on Cordova) vs Web. We will then go through some of the prominent tradeoffs between the different options: cost, reuse, single language, speed and user experience, device support, learning curve.
This should give you some (opinionated) guidelines to choosing the right mobile stack for your particular App.
Greane Tree Technology CTO Joseph Payette gave our latest “Lunch & Learn” presentation. With the number of tools and frameworks for cross platform mobile application development increasing every year, it can be a challenge to determine the best fit technology for a mobile project. All of these tools and frameworks have their advantages and disadvantages, as they leverage different mechanisms for abstracting differences across mobile devices in an effort to provide a single platform for rapid application development. To bring order to the various options at hand, Joe reviewed mobile application architectures (native, hybrid, and HTML5), and explored and compared a few hybrid tools and frameworks, namely PhoneGap (www.phonegap.com), Appcelerator (www.appcelerator.com), and MoSync (www.mosync.com). Joe’s mobile application development presentation includes sample code for these three tools and frameworks.
The Lunch and Learn series is a regular event where we discuss topics of interest to our projects and clients. Last month, Chad Calhoun explored Git Interactive Techniques.
Hybrid vs Native Mobile App. Decide in 5 minutes!July Systems
Wondering whether to build a hybrid mobile app or a native mobile app? Don’t worry, this presentation will help you decide your mobile app strategy in less than 5 minutes!
Building Hybrid Apps with AngularJS and IonicYounes Adounis
Ionic est un SDK HTML5 puissant qui vous aide à construire des applications mobiles Hybrid en utilisant des technologies web comme HTML, CSS et Javascript.
Durant cette session on verra quand faut it choisir Hybrid au lieu de Native, comment utiliser Ionic et tous ses composants et à la fin on fera un exemple réel d'application Android et iOS pour voir les meilleurs pratiques de développement.
Not all apps are created equal. The type of app that you develop will depend on the features you want and your compatible device preferences. There are pros and cons to each app type, but there is usually a best app for your situation.
The Multiplatform App Architecture offers the possibility to create mobile applications for multiple mobile platforms and at the same time offer the flexibility to use all native functionality of the mobile operating systems to realize an optimal user experience. Combined with a powerful development environment and a comprehensive programming language it offers an excellent way to develop and maintain rich mobile applications.
Capgemini helps customers to achieve mobile excellence and realizes mobile applications in an agile way using this architecture.
Top 4 Cross Platform tools for Mobile App Developmenttechugo
Scope of Cross Platform App Development is bright as developers and engineers find it easy and interesting to use a single code base to compile and deploy their app on all major mobile platforms. Top 4 Cross Platform Development tools are discussed here in the presentation, with few of their major pros and cons:
Hybrid vs native mobile development – how to choose a tech stackJacques De Vos
Choosing the wrong mobile tech stack sets you up for a world of pain. But how do you select the right one from a plethora of current options?
As an iOS developer I am convinced that a carefully designed native app provides the best user experience. So why would we choose Ionic2/Angular2 on Cordova (a bleeding edge Hybrid JavaScript framework) for our latest mobile App? In this short talk I will share our thinking and experiences on the current landscape of mobile stack options.
I will introduce the contenders: Native (iOS and Android) vs Semi-Native (Xamarin and React Native) vs Hybrid (Ionic2/Angular2 on Cordova) vs Web. We will then go through some of the prominent tradeoffs between the different options: cost, reuse, single language, speed and user experience, device support, learning curve.
This should give you some (opinionated) guidelines to choosing the right mobile stack for your particular App.
Greane Tree Technology CTO Joseph Payette gave our latest “Lunch & Learn” presentation. With the number of tools and frameworks for cross platform mobile application development increasing every year, it can be a challenge to determine the best fit technology for a mobile project. All of these tools and frameworks have their advantages and disadvantages, as they leverage different mechanisms for abstracting differences across mobile devices in an effort to provide a single platform for rapid application development. To bring order to the various options at hand, Joe reviewed mobile application architectures (native, hybrid, and HTML5), and explored and compared a few hybrid tools and frameworks, namely PhoneGap (www.phonegap.com), Appcelerator (www.appcelerator.com), and MoSync (www.mosync.com). Joe’s mobile application development presentation includes sample code for these three tools and frameworks.
The Lunch and Learn series is a regular event where we discuss topics of interest to our projects and clients. Last month, Chad Calhoun explored Git Interactive Techniques.
Designing and delivering elearning in a multi-device worldKineo
Kineo Pacific’s eLearning Solutions Manager Souraya Khoury led a breakout session on Day 1 of AITD 2013 about the new challenges that L&D departments face: What can be achieved with HTML5 and how responsive eLearning design can assist in achieving greater levels of accessibility across multiple devices.
Find out more at www.kineo.com
ChromeInfo Technologies is a renowned Native Mobile App Development Company in India. ... Offering you with best Native Mobile App Development Services, we have talented team of well-skilled professional, delivering best mobile solutions.
Deal with the dilemma of hybrid and nativeswamileo1
There are two kinds of platforms that can be used to build an app, Hybrid or Cross platforms and Native platforms. Hybrid and Native technologies have their own pros and cons although it is still debatable which framework is better.
HTML5 vs. Native Apps: Demystifying the Decision Making ProcessiTexico
It’s now clear that mobile is the path consumer markets are leaning towards to utilizing mobile apps as their preferred way to conduct e-commerce. According to a study by Gartner, 70% of customer interactions will originate from a mobile device by 2015. More and more organizations are realizing that mobile can significantly impact their core business operations and are transitioning to a mobile-based strategy. Therefore, iTexico partnered with Propelics to deliver a webinar: "HTML5 vs Native Apps: Demystifying The Decision Making Process" Here we present the slides from the last webinar.
Mobile App Landscape for the Non-TechnicalJames Quick
As CEO/Founder of any startup, you may not be the lead developer on your product or app, but you do have to be able to have somewhat technical conversations with investors, interviewees, etc. All founders have wear many different hats and perform multiple different roles. This deck focuses on the landscape of Mobile as it is today focusing on three major platforms, Android, IOS, and Windows. We will take a look at building both native applications and cross-platform applications along with relevant tools and skills needed for both.
Similar to Mobile application development strategy and execution (20)
3. • Any Device
– Smartphones, Tablets, Desktops, TVs
– Mobile, Portable, Desktop, Anchored Devices
– Different Form Factors and User Experiences
• Consumers, Customers, Citizens and Employees
• Pay for Download, Subscription, In App Purchases
and Free
• Apple, Google and Microsoft
• Mobile Device Management and BYOD
• Marketplaces and Private Stores
• Mobile Web and Mobile Apps
13. • Pure Native – Written in the devices SDK, so one codebase per
platform and no code reuse between platforms.
• Common Language Frameworks – All code is written in the
same language. There can be 50% or more reusable code
between platforms; but not a single codebase.
• Hybrid – Written in special frameworks that host the Mobile
application on the device but inside a Web Control. There is a high
level of code reuse between platforms usually with only one
codebase.
• Mobile Web – A website that has been optimized for touch
devices and use on smaller screens like mobile devices. Like any
web-application there is usually only one codebase
14. • Pure Native – Written in the devices SDK, so one codebase per
platform and no code reuse between platforms.
• Common Language Frameworks – All code is written in the
same language. There can be 50% or more reusable code
between platforms; but not a single codebase.
Performance Boundary
• Hybrid – Written in special frameworks that host the Mobile
application on the device but inside a Web Control. There is a high
level of code reuse between platforms usually with only one
codebase.
• Mobile Web – A website that has been optimized for touch
devices and use on smaller screens like mobile devices. Like any
web-application there is usually only one codebase
15. • Pure Native – Written in the devices SDK, so one codebase per
platform and no code reuse between platforms.
• Common Language Frameworks – All code is written in the
same language. There can be 50% or more reusable code
between platforms; but not a single codebase.
UX Boundary
• Hybrid – Written in special frameworks that host the Mobile
application on the device but inside a Web Control. There is a high
level of code reuse between platforms usually with only one
codebase.
• Mobile Web – A website that has been optimized for touch
devices and use on smaller screens like mobile devices. Like any
web-application there is usually only one codebase
16. • Pure Native
– Apple iOS – Objective C
– Google Android – Java
– Microsoft Windows 8 - C# or HTML5
• Common Language Frameworks
– C# and others (Mono)
• Hybrid
– PhoneGap, JavaScript, some Pure Native SDK experience
• Mobile Web
– HTML5, CSS3, JavaScript
17. • Pure Native Best
– Apple iOS – Objective C
– Google Android – Java
– Microsoft Windows 8 - C# or HTML5
• Common Language Frameworks
– C# and others (Mono)
• Hybrid
– PhoneGap, JavaScript, some Pure Native SDK experience
• Mobile Web
– HTML5, CSS3, JavaScript Good
18. • Pure Native Best
– Apple iOS – Objective C
– Google Android – Java
– Microsoft Windows 8 - C# or HTML5
• Common Language Frameworks
– C# and others (Mono)
• Hybrid
– PhoneGap, JavaScript, some Pure Native SDK experience
• Mobile Web
– HTML5, CSS3, JavaScript Good
19. • Pure Native Highest
– Apple iOS – Objective C
– Google Android – Java
– Microsoft Windows 8 - C# or HTML5
• Common Language Frameworks
– C# and others (Mono)
• Hybrid
– PhoneGap, JavaScript, some Pure Native SDK experience
• Mobile Web
– HTML5, CSS3, JavaScript Lower
20. • Pure Native Highest
– 1N per platform
• Common Language Frameworks
– 1N for the first platform, .5N additional platforms
• Hybrid
– 1.25N for Apple, Google and Windows Phone
• Mobile Web
– 1N for Apple, Google and Windows Phone
Lower
21. • App for that
– $150,000 for Apple, Google and Windows Phone
22. • Pure Native
– $150,000 for Apple, Google and Windows Phone
23. • Pure Native
– $$50,000 for Apple Google and Windows Phone
24. • Pure Native Justify
– $150,000 for Apple, Google and Windows Phone
• Common Language Frameworks
– $100,000 for Apple, Google and Windows Phone
• Hybrid
– $62,500 for Apple, Google and Windows Phone
• Mobile Web
– $50,000 for Apple, Google and Windows Phone
Start
25. • Pure Native Company Owned
Targeted Device
– Field Workforce and Line of Business Applications
– Game Development
• Common Language Frameworks
– Must go native but still need a broad reach
– Leverage existing development language skill sets
• Hybrid
– Smartphone Applications
– Augmenting an existing web experience
• Web
– Broad reach consumer solutions
– Infrequent or impulse use cases
– non-committed consumers, citizens or employees BYOD
Broad Reach
26. • Pure Native
– Field Workforce and Line of Business Applications
– Game Development
• Common Language Frameworks
– Must go native but still need a broad reach Marketplace Solutions
– Leverage existing development language skill sets
• Hybrid
– Smartphone Applications
– Augmenting an existing web experience
• Web
– Broad reach consumer solutions
– Infrequent or impulse use cases
– non-committed consumers, citizens or employees
27.
28.
29. Mindy Hass Marketing Professional
Mindy is technically savvy and has moderate industry
experience. Her background is IT Solutions
Architecture. Although her work process itself is not
complex, the management of all marketing and social
5
media efforts is.
“I need to the ability to see and prioritize marketing 4
events quickly.”
3
2
1
Age: 25-45 Knowledge Activities
Primary Use Goals Influencers Pain Points & Frustrations
• Find relevant events • Have a unified location for all • Offline access to all information • There is no unified place to find this
regarding technology as it events, regardless of technology • Easily find event locations information
relates to IT Solutions and/or location • Efficiently filter events by • Hard to access information remotely
Architecture • Register for events technology and location • Difficulty in finding solutions for a
• Find ways of creatively • The ability to access information • Seamlessly register for events specific problem
expanding the companies remotely without leaving application
presence in the field
• Research new technologies
• Research ways to improve
company productivity
38. • Communications : JSON RESTful Services
• Framework : ASP.NET Web.API
• Platform : Azure
– Load balanced Web Worker roles
– Azure Storage Queues
– Azure Worker processes OR services running at “Home”
monitoring the queues
– Azure Tables & SQL Azure for cached “mobile only” data
39. • PaaS Web/Worker roles scale easily without the
overhead of new “servers”
• Easy deployments
• VM support when you need to “own” the OS
• Simple queues up to complex Service Bus
architectures to fit your messaging needs
• Easy and cross platform identity management
that can integrate with your on-prem AD and
manage access and control of your applications
• SQL Azure for traditional relational data
42. • KISS your mobile strategy
• Start with Who?
– Requirements
– Platform Support
– Broad Reach or Targeted Devices
– BYOD or Company Owned
– Solution Strategy
– Marketplace Considerations
• Multiple mobile solutions might be the answer
• Keep all four (4) Solution Strategies on the table
• Design, Prototype, Build
• Measure and Iterate
43. Eric Russell
Director of Business Development
Catapult Systems - Mobile Division
512.225.6974 | Direct
512.328.8181 | Main
512.577.7209 | Mobile
512.328.0584 | Fax
eric.russell@catapultsystems.com