Skip to content

Implement memorization score submission prompt #26

@c0d3sw0t

Description

@c0d3sw0t

Extracted from documentation: T3-InfoSec/t3-memassist#10


What is the Problem or Limitation?

The application lacks a structured mechanism to prompt users for memorization score submission at the appropriate moment. Without this feature, the app risks missing critical moments to record user performance, which could impact tracking progress and generating meaningful insights. A streamlined submission flow ensures the data is captured when it matters, without disrupting user experience.


Describe the Solution You Would Like

The solution aims to introduce an interactive prompt that triggers the score submission once there is a submission in the user’s memorization session.

  1. Trigger Points for the Submission Prompt

    • Automatically display the prompt:
      • When the user submits an answer or finishes a specific number of nodes.
  2. Handling Multiple Submissions

    • Prevent duplicate submissions by checking if a score has already been recorded.
    • If the user skips the submission, prompt them again only after further progress is made or the session ends.
  3. Performance and Security Considerations

    • Ensure submission happens asynchronously to avoid blocking the user interface.
    • Store submitted scores securely in an encrypted database to prevent tampering and data loss.
    • Implement validation checks to verify the integrity of the submitted scores before saving them.
  4. Feedback Loop with User

    • After a successful submission, display personalized feedback, such as:
      • “Great job! You’ve improved by 20% since your last session.”
      • Next step suggestions to guide users (e.g., “Try Level 2 next!”).

Additional Considerations

  • Analytics Integration: Capture metrics like submission rates and skipped submissions to monitor user behavior and improve the prompt.
  • Multi-language Support: If the app supports multiple languages, ensure the prompt is localized for each user’s preference.
  • Error Handling: If submission fails due to a network issue, notify the user and retry in the background when the connection is restored.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions