Draft PPS (Problem, Proposed Solution) Design Doc for Biweekly Leaderboard "Lost and Found" Feature

[NwinNwin]

Description

• Please draft a PPS (Problem, Proposed Solution) design document for implementing the Biweekly Leaderboard Lost & Found feature to gamify the app.

---

The design doc should include the following:

1. Goal:

   • Explain the purpose of this feature:
     • Encourage continuous user engagement through a "Lost and Found" leaderboard reset every two weeks.
     • Create a mini-challenge every two weeks for users to participate in the leaderboard.

2. Feature Flow:

   • Detailed user journey from the start of a biweekly cycle to the reset event and user re-engagement.
   • Explain what happens when the leaderboard resets. (Technical + UI/UX)
   • How do we notify users that win the event?
   • Way to view past competition winners? All time score?
   • NOTE: If you have time, include a simple diagram or flow chart would be very helpful!

3. Technical Details:

   • CRON Job:
     • Set up a scheduled CRON to reset leaderboard data every two weeks at a specific time (UTC).
     • Describe how the CRON triggers the leaderboard archive and reset.
   • SQL Implementation:
     • How to track the current biweekly leaderboard entries.
     • Two seperate tables?
   • API Requests:
     • New or updated endpoints for:
       • Fetching current leaderboard.
       • Fetching previous cycle leaderboard.
       • Notifications or reminders for users about resets?

4. Edge cases

   • If you can think of any techincal or UI/UX edge cases, please document it as well 🙏

[rebecca-123]

Link to PPS

Version 2