RFC Offline support

[Brah-Timo]

Description

[RFC] Offline-First Support: Cache + Queue + Sync Engine

Suggested solution

Suggested solution:

Wrap SupabaseClient with an offline layer:

1. Cache: cacheFirstThenNetwork strategy for instant data
2. Queue: Store mutations in Hive when offline, auto-sync on reconnect
3. Sync: Resolve conflicts with "last write wins"
4. Realtime: Buffer events offline, replay when online

API stays same: UltraClient(client).from('todos').select()

PoC: https://pub.dev/packages/supabase_flutter_ultra/versions/0.1.0

Open to PRs. What's the preferred approach for conflict resolution?

Alternative

No response

Additional context

No response

Validations

• Follow our Code of Conduct
• Read the docs.
• Check that there isn't already an issue that requests the same feature to avoid creating a duplicate.

[spydon]

Hey @Brah-Timo,
Since we're trying to stay aligned between the different SDKs we'd not put this directly in the SDK for now, but we're very soon starting to build v3 of the SDKs and I'll make sure that we take up offline-first support when we do.

[Brah-Timo]

Hey @Brah-Timo,
Since we're trying to stay aligned between the different SDKs we'd not put this directly in the SDK for now, but we're very soon starting to build v3 of the SDKs and I'll make sure that we take up offline-first support when we do.

Thanks for the update!

Totally makes sense to keep the SDKs aligned. I'll continue maintaining supabase_flutter_ultra as a community package and gather feedback/use cases in the meantime.

Looking forward to the v3 discussions. Happy to contribute any learnings from the PoC, especially around conflict resolution strategies we've tested.

Let me know when v3 planning kicks off 👍