Improve data consistency and sync reliability across dashboard modules

[sdeepika-2606]

While using LifeTrack, I noticed that progress data across tasks, workouts, diet, and coding modules can occasionally feel slightly out of sync on the dashboard. Improving consistency in state updates and Supabase sync handling would make progress tracking more reliable, especially after rapid updates or app restarts.

[saksham91108]

Hi @tanishsarkar28 👋

I'd love to work on this issue! After reviewing the codebase and the problem described above, I'm confident I can address all the points:

• ✅ Fix data consistency across tasks, workouts, diet & coding modules
• ✅ Resolve state sync issues on the dashboard
• ✅ Add proper error-handling and rollback logic in data_providers.dart
• ✅ Ensure reliable async sync with the Supabase API

Could you please assign this issue to me? I'll have a PR ready soon! 🚀

[undamatla-vijayeswari]

Hi @tanishsarkar28 ,

I am a GSSoC 2026 contributor and would like to work on this issue. I have reviewed the requirements and am confident I can complete it successfully.

Kindly assign this issue to me.

Thank you!

[vinodsingh-dev-gsoc]

Hi @sdeepika-2606 and @tanishsarkar28

I have been analyzing the LifeTrack dashboard sync issues. The problem with rapid updates feeling "out of sync" usually stems from race conditions between local state and backend writes.

Here is my concrete architecture plan to fix this:

Optimistic State Updates: I will refactor the local state controllers to update the UI immediately upon user action, before awaiting the Supabase response. This makes the app feel instantly responsive.

Write Debouncing & Queuing: For rapid updates (like ticking off multiple tasks or reps quickly), I will implement a debounce mechanism to batch the Supabase API calls, preventing write conflicts.

Supabase Realtime Subscriptions: I will ensure the dashboard listens to Supabase.instance.client.from('your_table').stream(...) so that if a background sync completes or fails, the dashboard state recovers and matches the source of truth perfectly.

Error Rollbacks: If the Supabase write fails, the local state will gracefully roll back to the previous snapshot, accompanied by a clean SnackBar alert.

My environment is fully set up. Could you assign this to me? I can start implementing this robust sync logic immediately!