Shareable progress image or summary, built from the review log
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
Research direction
Start by reading the linked issues #113 and #323 to understand which review-log stats will be available and what the achievements screen already covers. Then review the stats or achievements screen and the interface-prose rules in AGENTS.md; the issue names no specific files or tests. Done means learners can share an image or text summary generated on-device, with the chosen stats settled and no data sent by the app.
Written by the indexing model from the issue text.
Description
Priority: low. Unblocked: #113 closed with PR #432 (FSRS-6 and the skill model).
What
Let a learner share their progress outside the app as an image or a text summary. It is generated on-device from the review log, with no account or server.
This is the offline-first answer to the lack of a social layer: a way to show a streak or a milestone without adding accounts, a backend, or anything that works against offline and privacy.
Where the numbers come from
The numbers to share (retention, words known, streaks) come from the FSRS-6 data and the per-skill fits that PR #432 landed (#113). Related: #323 (Achievements: summary, Progress grid and badges) already covers the on-screen summary, and this should reuse its stats rather than duplicate them.
Sketch
- Share action on the stats or achievements screen, using the platform share sheet.
- Image (rendered card) and plain-text variants.
- Content candidates: current streak, cards reviewed this week, words known per language, deck milestones.
- Computed from the review log only, with nothing sent anywhere by the app itself.
Open questions
- Which stats are worth sharing, once #323 settles?
- Does the image need localised text, per the interface-prose rules in AGENTS.md?
Generated by Claude Code
- Dominant language
- Dart
- Stars
- 1
- Forks
- 0
- Avg merge
- 3h 34m
- Merged PRs (30d)
- 246
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from aaronified/fluenough
-
Difficulty 1/5 1-3 hours Newbie friendliness 76/100
aaronified/fluenough#665 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
aaronified/fluenough#622 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
aaronified/fluenough#503 · 1 comment ·
Maintainers usually reply within 1 day
-
bug direct-code
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
aaronified/fluenough#492 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
aaronified/fluenough#300 ·
Maintainers usually reply within 1 day
All issues in aaronified/fluenough
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
sass/dart-sass#2888 · 2 comments · 1 reaction ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
CircuitVerse/mobile-app#679 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
PhoebeSoftware/xrooster#41 ·