

783: How We Built a Netflix Style “Save for Offline” Feature Into Syntax
7 snips Jun 17, 2024
Discover the ins and outs of browser caching as the hosts dive into the File System API and Cache API. Learn the unique characteristics of local storage, IndexedDB, and the challenges they present, especially in Safari. Explore technical hurdles while implementing offline listening and the intricacies of managing MP3 data. Unpack the nuances of persistent storage and how user interactions affect it. Plus, get a peek into the complexities of video autoplay permissions that drive developers up the wall!
AI Snips
Chapters
Transcript
Episode notes
Why Not File System API?
- Avoid using the file system API for storing large amounts of user data due to browser inconsistencies and user experience issues.
- The file system API can cause errors, requires permissions, and might scare users, making the Cache API a smoother alternative.
Cache API Explained
- The Cache API, typically associated with service workers, can function independently for general browser caching.
- It offers a way to manage request/response caching directly within the browser, separate from HTTP caching or service worker contexts.
Browser Storage Limits
- Browser storage limits for the Cache API vary significantly, with Chrome offering the most generous allocation.
- Chrome allows caching based on a percentage of free disk space, while Firefox and Safari impose fixed limits, impacting applications like Riverside.fm.