Tulip Logo IconTulip
Google Provider

Sync and Metadata

Treat Google Drive metadata as remote state with provider-specific mapping and cache concerns.

Practical concerns

  • remote names and parent relationships can change outside your app
  • readonly and archive semantics map differently than in local storage
  • folder listings should assume remote latency
  • cached metadata needs explicit invalidation rules

Important Google-specific fields

The provider keeps several native fields available because they matter in real products:

  • webViewLink: best default for opening a file in Google Drive
  • webContentLink: binary download link when Google provides one
  • thumbnailLink: preview thumbnail when available
  • trashed and trashedAt: used to model archive-like behavior
  • canEdit: useful for disabling actions beyond your own app permission layer
  • googleParents: useful when diagnosing tree sync issues

Document these differences in product code so users know when they are interacting with a remote system instead of app-owned storage.

Server

The Google server layer exposes tree reads and node mutations against Google Drive.

Components

Drive exposes small building blocks that can be composed into full file-management screens.

On this page

Practical concernsImportant Google-specific fields