ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
A concise architecture note for implementing a minimal HTML5 Service Worker that caches core assets and serves them offline, covering requirements, design, trust boundaries, checks, failure modes, verification, limits, and rollback.
Goal Determine whether enabling Firestore persistence with enablePersistence() results in a single shared IndexedDB cache across multiple tabs when the application is used in Safari private browsing mode, given that the SDK attempts to share persistence via a shared worker but sharing is not guaranteed across all browsers. Constraints include the variability
Ti.Cloud.currentUser() returns null when offline The goal is to understand why the Cloud Services API returns null for Ti.Cloud.currentUser() after a device loses connectivity, even though a user had previously authenticated. This behavior is observed in SDK versions 7.0.0 and later, but the documentation does not specify whether a cached user should be retu
Goal Determine how Notion’s offline editing strategy affects data freshness when multiple devices edit the same page. The focus is on the trade‑off between immediately pushing changes to the server versus applying updates locally and deferring cache invalidation until a sync cycle completes. Constraints & Uncertainty Notion stores a local cache (IndexedD
html5
titaniumsdk