Upgrade to Pro — share decks privately, control downloads, hide ads and more …

WebApp vs Native: Performance analysis

WebApp vs Native: Performance analysis

Adrien Couque

December 11, 2012
Tweet

More Decks by Adrien Couque

Other Decks in Technology

Transcript

  1. Focus On: WebApp vs Native, Performance 2012 • Mobile development

    is about UX Which technology should we use?
  2. Focus On: WebApp vs Native, Performance 2012 • Web App

    HTML + Javascript Run inside a browser or a web view inside an application (hybrid approach) Few OS-specific UI elements Native Compiled language Run as a standalone program Direct access to the hardware
  3. 2012 • Compression Focus On: WebApp vs Native, Performance API

    zlib java.util.zip zlib.js 3 Mo pure text ≈ 3.000.000 characters 10 iterations (compression + decompression)
  4. 2012 • SHA-1 Focus On: WebApp vs Native, Performance API

    CommonCrypto MessageDigest crypto.js (Google)
  5. 2012 • Pi Pure arithmetics (additions, multiplications...) Spigot algorithm (Gibbons)

    100.000.000 iterations Yields ≈20.000.000 decimals Focus On: WebApp vs Native, Performance
  6. Focus On: WebApp vs Native, Performance 2012 • Vector Graphics

    API Core Graphics Canvas <canvas> Test: Draw a 7-degree Koch snowflake
  7. Focus On: WebApp vs Native, Performance 2012 • UI Layout

    API UICollectionView GridView CSS (float left) Test: display a grid of thumbnails images
  8. Focus On: WebApp vs Native, Performance 2012 • SQL queries

    API sqlite 3 Web SQL Database (deprecated) Test: Count the occurrences of a word in a book using INSERT and SELECT statements
  9. Focus On: WebApp vs Native, Performance 2012 • Google Maps

    Native Frame Rate: Web Frame Rate: 59 fps 37 fps
  10. Focus On: WebApp vs Native, Performance 2012 • Cut the

    Rope Native Frame Rate: Web Frame Rate: 10 fps 58 fps
  11. Paris, December 11, 2012 Applidium 17 rue du Faubourg du

    Temple 75010 Paris http://applidium.com Thank you