🧩 The Goal
Currently, InnerHue relies heavily on the browser's localStorage to persist user data (mood entries, streaks, and customization settings). This limits the user experience as data cannot be synced across multiple devices, and clearing the browser cache wipes out long-term analytics. The goal is to move from client-side storage to a robust cloud database to ensure seamless, cross-device emotional tracking.
✨ Proposed Change
I propose integrating a modern database to handle user authentication and data persistence. The key changes would include:
- Setting up database schemas to securely store
users, mood_entries, and preferences.
- Refactoring the client-side state management to sync with the database.
- Ensuring that visual configurations—like the specific parameters rendered by the
OrbVisualizer for past moods—are accurately restored from the cloud when a user views their historical data.
- Providing an automatic migration path to upload a user's existing
localStorage data to the cloud upon their first sign-up.
✅ Impact
- Data Safety: Users will no longer lose their emotional tracking history and streaks if their local cache is cleared.
- Cross-Device Support: A user can log a mood on their phone and review their analytics dashboard and 3D visualizers on their desktop.
- Roadmap Alignment: Directly fulfills the "Cloud Sync" and "User Authentication" goals outlined in the Q1 2026 project roadmap.
💬 Additional Context
I would love to be assigned to this issue under SSoC26 to implement this feature.
Tags required: ssoc26 , hard , database
🧩 The Goal
Currently, InnerHue relies heavily on the browser's
localStorageto persist user data (mood entries, streaks, and customization settings). This limits the user experience as data cannot be synced across multiple devices, and clearing the browser cache wipes out long-term analytics. The goal is to move from client-side storage to a robust cloud database to ensure seamless, cross-device emotional tracking.✨ Proposed Change
I propose integrating a modern database to handle user authentication and data persistence. The key changes would include:
users,mood_entries, and preferences.OrbVisualizerfor past moods—are accurately restored from the cloud when a user views their historical data.localStoragedata to the cloud upon their first sign-up.✅ Impact
💬 Additional Context
I would love to be assigned to this issue under SSoC26 to implement this feature.
Tags required:
ssoc26,hard,database