Adapter roadmap

The honest position#

No cloud adapter ships with this package. What ships is ICloudTransport — a four-method seam over opaque bytes — plus everything above it: keys, metadata, precondition discipline, conflict policies, the offline queue and the retry policy. A game that wants a specific service writes one class against that seam.

The entries below are planned, and they are listed as principles rather than promises. No dates are given because none have been committed to.

Firebase adapter#

Roadmap Not shipped. Nothing in this package imports a Firebase SDK, and no account or credential is bundled.

A Firestore or Cloud Storage backed transport would map PutAsync/GetAsync/ListAsync/DeleteAsync onto the service's own calls, declare supportsConditionalWrites honestly (Firestore's preconditions map well), and return CloudErrors.PreconditionRefused(...) rather than retrying over a lost race. Until it exists, the work is the same as for any transport — see Providers and adapters.

PlayFab adapter#

Roadmap Not shipped. PlayFab's entity and title data APIs are a reasonable fit for a transport; the framework would not need to change. The same rules apply: declare capabilities truthfully, never throw for an expected failure, and report LooksOnline as a hint.

Generic REST adapter#

Roadmap Not shipped. A REST transport is the most likely first adapter, because it requires no vendor SDK: a PUT/GET/DELETE with an ETag or a revision header covers the four methods, and HTTP status codes map onto the framework's error codes. The failure-injection doubles the cloud tests use today are already HTTP-shaped.

Future integrations#

Roadmap Also planned, also not shipped:

• Steam Cloud, if and when a game needs it — the same seam applies.
• Visual Scripting and PlayMaker nodes over the existing facade.
• Additional platform verification (mobile and consoles, which today are Not verified).
• Additional Unity type support, driven by what games actually ask for.
• Further Editor tooling on top of the validation and diagnostics that already exist.

What exists today#

Available ICloudTransport, ICloudSaveProvider, TransportCloudSaveProvider, CloudSaveSyncService, CloudSyncJournal, CloudConflictPolicy, ICloudConflictResolver, ICloudAuthenticationProvider, CloudRetryPolicy, CloudProviderCapabilities and FakeCloudTransport — the whole framework side of a cloud integration, verified with doubles. Adapter required The provider is yours.

Next#

• Cloud architecture — the boundary in one picture.
• Roadmap — the studio-level view, with the same honesty.
• Samples — 02_CloudSync runs a full sync against the in-memory transport.