Solving Problems for African Soil
summary
Argues that African constraints are concrete: rolling outages of 4–12 hours, ~51% smartphone ownership in South Africa, and data at ~$10/GB make heavy JS and network chatter unusable. Recommends Ember strategies: ember-cli fastboot (static SSR) to drop first contentful paint, code splitting and tree‑shaking to cut JS bytes (examples: bundle analyzer, BundlePhobia, Lighthouse), and service workers plus Pouch-style local stores so pages load offline and queued writes sync automatically when connectivity returns. Gives concrete budgets (e.g., ~170 KB JS, <7s on Android Go).
AI-written summary · about
chapters (9)
- 0:00Start
- 2:33Load Shedding
- 4:06Basic Digital Literacy
- 12:31Code Splitting
- 15:29Mbcli Bundle Analyzer
- 16:17Bundle Phobia
- 23:20Other Performance Tips
- 26:49Milestone Timings
- 30:33Conclusion
related talks
31mWeb Performance: The African Case
24mWeb Performance: The African Case
01h 23mWhy Slow?
30mEmpathy Driven Development: Boosting performance by implementing for unfavorable conditions
32mResponsible Javascript
27mThe Secret Web Performance Metric No One Is Talking About
34mNew Adventures in Front-End, 2021 Edition
30m10KB or Bust: The Delicate Power of Webpack and Babel