Keeping time-based progress consistent
The Flare’s progress was not only a record of completed lessons. Lives recovered over time, daily challenges had their own timing, and streaks depended on when someone last completed an activity. The interface needed to know when its stored state might be out of date.
I added a last-sync timestamp to the profile flow so routine refreshes could reuse recent data. When lives or streak information could have expired, the application could request an immediate refresh instead. The server response updated the profile and daily-quiz state together.
I also removed a duplicate daily-quiz initialization request and adjusted the startup and redirect logic around completed quizzes. These changes kept synchronization and navigation tied to the learner’s current state rather than treating every screen visit as a fresh start.
