experience is close to perfect, while apps are vitally important on phones because the web experience is dismal. “ Nilay Patel http://www.theverge.com/2015/7/20/9002721/the-mobile-web-sucks
page resulted in the ‘Get App’ button being pressed. (Note that some percentage of these users already have the app installed or may never follow through with the app store download.) • 69% of the visits abandoned our page. These users neither went to the app store nor continued to our mobile website. “
two options that Atwood mentioned) flat out disqualify them for mobile use. “ Henrik Joreteg https://joreteg.com/blog/viability- of-js-frameworks-on-mobile
server • Users see content before JavaScript loads • Mitigates all but largest payload sizes • Reduce framework size by removing deprecated features • Ship Ember as ES6 modules (tree shaking) • Eliminate unused modules • Split up app code into separate bundles • Users only load code for the part of the app they're using
• Preemptively fetch resources • Never download JavaScript assets after first boot • Update atomically • Available everywhere today • Ship JavaScript modules as strings • Only pay evaluation cost for modules that are actually used Service Worker App Cache String Loading
Teaches us how to make core Ember better • Compiles templates to FRP program, runs it on a custom VM • Unlocks adaptive, runtime optimizations • Paves the path to eagerly awaited features 2