Cloud storage synchronization has traditionally relied on dedicated folder silos (e.g., a local “Google Drive” folder). However, recent shifts toward operating system (OS)-level integration—such as Google Drive’s “File Stream” functionality within Windows Explorer—promise reduced local storage usage and native navigation. This paper investigates the user experience, performance overhead, and cognitive load associated with accessing Google Drive directly inside Windows Explorer compared to traditional folder-based sync or web interfaces. Using a mixed-methods approach (task completion timing, error logging, and semi-structured interviews with 30 knowledge workers), we find that while OS integration reduces context switching and storage anxiety, it introduces new friction points: inconsistent file status indicators, latency in thumbnail generation, and conflicts with offline mode expectations. We propose a design framework for “ambient cloud storage” that respects Windows Explorer conventions while clarifying cloud-native behaviors.
NASA-TLX scores for “effort” and “frustration” were significantly higher for the virtual drive than for a traditional sync folder (p < 0.05), despite users rating the idea of integration as “more modern.” google drive in windows explorer
When network drops, the virtual drive remains visible in Explorer but double-clicking a non-cached file shows a “File not found” error after 12 seconds. Users mistook this for file corruption. 5. Discussion 5.1 The Explorer Metaphor Breaks Windows Explorer assumes files are either present or absent, with deterministic open times. Google Drive’s “stream on open” violates the locality of reference expectation. Users expect a drive letter to behave like a USB drive or local disk. It does not. Users mistook this for file corruption
Study funded by no external entity; all participants were volunteers. Study funded by no external entity