Need for Speed: How XO Group Optimized their Image Loading Time on The Knot Mobile App
summary
Measures this path from 8.6 seconds cold start to 480 milliseconds by removing unused images, moving bitmaps to a media API with resized URLs and SDWebImage placeholders, and converting icons to draw-code via PaintCode/QuartzCode. Finds over 300 assets and shows 70% of launch time comes from the asset catalog, uses DYLD_PRINT_STATISTICS to measure, runs lsunusedresources to delete dead files, and accepts a few compile-time draw-code costs to hit 480 milliseconds while keeping rich UI with SDWebImage placeholders.
AI-written summary · about
chapters (13)
- 0:00Introduction
- 1:10About The Knot app
- 2:37Why launch speed matters
- 4:28Diagnosing launch time
- 6:13Surprising cause of slowness
- 7:58Optimizing image loading
- 10:03Vector vs bitmap images
- 11:30PaintCode and QuartzCode
- 12:53Streamlining vector images
- 13:58Vector image trade-offs
- 15:00Optimizing bitmap images
- 16:44Image implementation strategy
- 17:06Results and launch time
related talks
33mOptimization - Making your app faster
41mBuild apps for Billions
58mNeed for speed 8, performance tuning of your web application
46mThink Fast!
30mFast and Beautiful: Modern Image Delivery Techniques
37mIt's just too Slow: Testing Mobile application performance
41mMaking The Mobile Website Faster
48mFast and Beautiful: Modern Image Delivery Techniques