Ce diaporama a bien été signalé.
Nous utilisons votre profil LinkedIn et vos données d’activité pour vous proposer des publicités personnalisées et pertinentes. Vous pouvez changer vos préférences de publicités à tout moment.
Cross-Platform Native vs. Hybrid HTML
Making the right choice for the enterprise
We will answer questions during our Q&A
S...
Xamarin: The Complete Mobile Lifecycle Solution
xamarin.com
Today’s presenters
Kevin Ford

Mobile Practice Lead
Kevin Ford is the Mobile Practice
Lead with Magenic leading
developmen...
Agenda
1
Enterprise Mobile
Considerations
2
Mobile Frameworks
Overview
3
Head to Head Comparison:
Cross Platform Native vs...
What are we exploring and comparing?
Enterprise Productivity Fast Time to Market
POC or Version 1.0
Quantified Comparative...
Enterprise mobile considerations
Business Transformation
User Experience

and Productivity
Time to Market and Agility
TCO ...
What are the mobile platform stacks?
Platform Proprietary
Objective-C / Swift
Android Java
Windows .NET
Cross-Platform Nat...
The Demo App: IncidentTrackr
The Demo App: IncidentTrackr
•  Field Service productivity and
workflow app for
maintenance operations
•  Used dozens of t...
The Demo App: IncidentTrackr
The Demo App: IncidentTrackr
Azure App Service
(formerly Azure Mobile Services)
Azure Active Directory
(Identity)
Storage
...
Top-level takeaways
Cross-Platform Native fulfilled
all app requirements.
Hybrid HTML could not deliver
on key piece of functionality
without ...
25%
FASTER
Cross-Platform Native apps
started faster than the Hybrid
HTML versions
62%
FASTER
Cross-Platform Native
loaded large datasets
faster than Hybrid HTML
-50%
LESS
Cross-Platform Native
used less memory than
Hybrid HTML
-76%
LESS
Cross-Platform Native
used less CPU time than
Hybrid HTML
22x
FASTER
Xamarin performs
CPU-intensive tasks
faster than Hybrid
HTML
User Experience
User Experience: Key Considerations
Native UX Total Hardware &
Platform Access
UX Design
Capability
Developer Tools

and Productivity
Developer Productivity: Key Considerations
1
Volatility of

HTML frameworks
2
API Access
Extensibility
3
Stack Complexity
...
Hybrid HTML UI Frameworks
Performance
Performance: Runtime Metrics
4,810
1,940
3,840
1,550
Android	
  
iOS	
  
Hybrid	
  Mobile	
  
Hybrid	
  Mobile	
  
App Sta...
Performance: Runtime Metrics
4,810
1,940
3,840
1,550
Android	
  
iOS	
  
	
  231	
  	
  
	
  6,000	
  	
  
	
  165	
  	
  ...
Performance: Runtime Metrics
4,810
1,940
3,840
1,550
Android	
  
iOS	
  
	
  231	
  	
  
	
  6,000	
  	
  
	
  165	
  	
  ...
Performance: Runtime Metrics
4,810
1,940
3,840
1,550
Android	
  
iOS	
  
	
  231	
  	
  
	
  6,000	
  	
  
	
  165	
  	
  ...
Performance: Coding Metrics
Code Reuse
Hybrid	
  HTML	
  
Xamarin	
  
Hybrid	
  Mobile	
   99%
*96%
(with Xamarin.Forms)
4...
Performance: Coding Metrics
Hybrid	
  Mobile	
  
Hybrid	
  Mobile	
  
Code Reuse Compile Time (sec) – Debug Build
Hybrid	
...
Performance: Coding Metrics
Hybrid	
  Mobile	
  
Hybrid	
  Mobile	
  
Code Reuse Compile Time (sec) – Debug Build
Hybrid	
...
Total Cost of Ownership
TCO: Key Considerations
1
Upfront Cost vs.
Maintenance & Operations
2
End-User Productivity
App Adoption
3
Agility & Oppor...
Conclusion
What To Use When?
Results & eBook available March 2016
Cross-Platform Native
Public facing – a reflection of your brand
Ex...
What To Use When?
Results & eBook available March 2016
Cross-Platform Native
Public facing – a reflection of your brand
Ex...
Orlando, FL April 24th–28th
Thank you!
Prochain SlideShare
Chargement dans…5
×

Xamarin vs. Hybrid HTML: Making the Right Mobile Platform Choice for the Enterprise

6 763 vues

Publié le

Selecting the right mobile platform for your enterprise can be a high-risk gamble that can affect thousands of your employees and millions of your customers. Building the right app will either digitally transform your business or derail your efforts and force you to start over while the industry and customers leave you behind.

The two leading choices for building cross-platform native apps are Xamarin or hybrid mobile solutions that utilize HTML and JavaScript. How do you know which option is the best fit for you? Which solution provides superior user experience (UX), performance, faster development time, full hardware access, and a lower TCO?

Magenic, a leading solution provider, built an enterprise-focused application using the Xamarin Platform and a hybrid HTML framework to quantitatively compare the differences between the two approaches. These slides from the live webinar on 2/18/16 break down the essential advantages, roadblocks, and observations we found to help you make the best choice for your strategic mobile initiatives.

Publié dans : Mobile
  • Hey guys! Who wants to chat with me? More photos with me here 👉 http://www.bit.ly/katekoxx
       Répondre 
    Voulez-vous vraiment ?  Oui  Non
    Votre message apparaîtra ici

Xamarin vs. Hybrid HTML: Making the Right Mobile Platform Choice for the Enterprise

  1. 1. Cross-Platform Native vs. Hybrid HTML Making the right choice for the enterprise We will answer questions during our Q&A Send mail to webinar@xamarin.com
  2. 2. Xamarin: The Complete Mobile Lifecycle Solution xamarin.com
  3. 3. Today’s presenters Kevin Ford
 Mobile Practice Lead Kevin Ford is the Mobile Practice Lead with Magenic leading development with native mobile technologies, Xamarin and Cordova. Steven Yi Head of Product Marketing Prior experience at Microsoft, Red Hat, and global system integrators in strategy, product management and architecture roles.
  4. 4. Agenda 1 Enterprise Mobile Considerations 2 Mobile Frameworks Overview 3 Head to Head Comparison: Cross Platform Native vs. Hybrid HTML User Experience Developer Tools & Productivity Performance Total Cost of Ownership
  5. 5. What are we exploring and comparing? Enterprise Productivity Fast Time to Market POC or Version 1.0 Quantified Comparative Analysis Benchmarks vs. Anecdotal Experience Fully Mobile Capable TCO Long term & Opportunity Costs
  6. 6. Enterprise mobile considerations Business Transformation User Experience
 and Productivity Time to Market and Agility TCO and Maintainability
  7. 7. What are the mobile platform stacks? Platform Proprietary Objective-C / Swift Android Java Windows .NET Cross-Platform Native Hybrid HTML & JavaScript Frameworks React 1st Gen 3rd Gen 2nd Gen Native UX High performance Multi-platform Unified codebase Hardware & platform access Native UX High performance Multi-platform Unified codebase *Hardware & platform access Native UX High performance Multi-platform *Unified codebase Hardware & platform access
  8. 8. The Demo App: IncidentTrackr
  9. 9. The Demo App: IncidentTrackr •  Field Service productivity and workflow app for maintenance operations •  Used dozens of times a day •  Utilizes camera, microphone, and audio •  BYOD •  6 week development time •  Extend enterprise backend
  10. 10. The Demo App: IncidentTrackr
  11. 11. The Demo App: IncidentTrackr Azure App Service (formerly Azure Mobile Services) Azure Active Directory (Identity) Storage Azure SQL Database
  12. 12. Top-level takeaways
  13. 13. Cross-Platform Native fulfilled all app requirements. Hybrid HTML could not deliver on key piece of functionality without requiring custom Objective-C and Java. THE APP WORKED
  14. 14. 25% FASTER Cross-Platform Native apps started faster than the Hybrid HTML versions
  15. 15. 62% FASTER Cross-Platform Native loaded large datasets faster than Hybrid HTML
  16. 16. -50% LESS Cross-Platform Native used less memory than Hybrid HTML
  17. 17. -76% LESS Cross-Platform Native used less CPU time than Hybrid HTML
  18. 18. 22x FASTER Xamarin performs CPU-intensive tasks faster than Hybrid HTML
  19. 19. User Experience
  20. 20. User Experience: Key Considerations Native UX Total Hardware & Platform Access UX Design Capability
  21. 21. Developer Tools
 and Productivity
  22. 22. Developer Productivity: Key Considerations 1 Volatility of
 HTML frameworks 2 API Access Extensibility 3 Stack Complexity 4 Strongly-Typed Development 5 Compilation Time
  23. 23. Hybrid HTML UI Frameworks
  24. 24. Performance
  25. 25. Performance: Runtime Metrics 4,810 1,940 3,840 1,550 Android   iOS   Hybrid  Mobile   Hybrid  Mobile   App Start Time (ms)
  26. 26. Performance: Runtime Metrics 4,810 1,940 3,840 1,550 Android   iOS    231      6,000      165      3,000     Android   iOS   Hybrid  Mobile   Hybrid  Mobile   Hybrid  Mobile   Hybrid  Mobile   App Start Time (ms) Memory Usage (mb)
  27. 27. Performance: Runtime Metrics 4,810 1,940 3,840 1,550 Android   iOS    231      6,000      165      3,000     Android   iOS   110 25 iOS   Hybrid  Mobile   Hybrid  Mobile   Hybrid  Mobile   Hybrid  Mobile   Hybrid  Mobile   App Start Time (ms) Memory Usage (mb) Total CPU Time (seconds)
  28. 28. Performance: Runtime Metrics 4,810 1,940 3,840 1,550 Android   iOS    231      6,000      165      3,000     Android   iOS   110 25 iOS   4,800 4,030 2,070 3,220 Android   iOS   Hybrid  Mobile   Hybrid  Mobile   Hybrid  Mobile   Hybrid  Mobile   Hybrid  Mobile   Hybrid  Mobile   Hybrid  Mobile   App Start Time (ms) Memory Usage (mb) Loading Large Datasets (ms) – 1,000 RecordsTotal CPU Time (seconds)
  29. 29. Performance: Coding Metrics Code Reuse Hybrid  HTML   Xamarin   Hybrid  Mobile   99% *96% (with Xamarin.Forms) 42% using Xamarin.iOS and Xamarin.Android
  30. 30. Performance: Coding Metrics Hybrid  Mobile   Hybrid  Mobile   Code Reuse Compile Time (sec) – Debug Build Hybrid  HTML   Xamarin   25 18 32 34 Android   iOS   Hybrid  Mobile   99% *96% (with Xamarin.Forms) 42% using Xamarin.iOS and Xamarin.Android
  31. 31. Performance: Coding Metrics Hybrid  Mobile   Hybrid  Mobile   Code Reuse Compile Time (sec) – Debug Build Hybrid  HTML   Xamarin   25 18 32 34 Android   iOS   5.29 11.30 11.49 35.50 Android   iOS   Hybrid  Mobile   99% *96% (with Xamarin.Forms) 42% using Xamarin.iOS and Xamarin.Android Hybrid  Mobile   Hybrid  Mobile   App Size (mb)
  32. 32. Total Cost of Ownership
  33. 33. TCO: Key Considerations 1 Upfront Cost vs. Maintenance & Operations 2 End-User Productivity App Adoption 3 Agility & Opportunity Costs
  34. 34. Conclusion
  35. 35. What To Use When? Results & eBook available March 2016 Cross-Platform Native Public facing – a reflection of your brand Experience with C# or Java Utilizing newer and/or full hardware capabilities
  36. 36. What To Use When? Results & eBook available March 2016 Cross-Platform Native Public facing – a reflection of your brand Experience with C# or Java Utilizing newer and/or full hardware capabilities Hybrid HTML Lower UX expectations HTML-only skillset Primarily consumption experience vs. high interactivity
  37. 37. Orlando, FL April 24th–28th
  38. 38. Thank you!

×