feat: Installable PWA + offline entry capture
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 38/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Quiet
- Tech stack
- nextjs, typescript
Research direction
Start by reviewing next.config.ts and the bare public/ directory, then define the offline write and sync model before implementing the manifest, icons, and service worker. Done means the planner is installable, retains an offline read cache, queues entry logs while offline, and syncs them after reconnecting.
Written by the indexing model from the issue text.
Description
Size: L.
No web manifest and no service worker exist (next.config.ts, public/ are bare). The app is a phone-first daily logger but can't be installed or used offline.
Scope
Add a manifest + icons + service worker with an offline read cache and an outbox queue for logging entries offline (sync on reconnect). Big lever for real mobile daily use. Needs a design pass on the offline write/sync model.
- Dominant language
- TypeScript
- Stars
- 2
- Forks
- 4
- PR merge metrics
- No merged PRs in 30d
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 TemaDeveloper/personal_planner
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
TemaDeveloper/personal_planner#48 · 1 comment ·
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
-
good first issue polish
Difficulty 2/5 Half a day Newbie friendliness 72/100
All issues in TemaDeveloper/personal_planner
Similar issues
-
chore v2
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
modelcontextprotocol/servers#5115 ·
Maintainers usually reply within 1 day
-
beginner bug good first issue
Difficulty 1/5 Under an hour Newbie friendliness 85/100
philaconvalley/website#168 ·
Maintainers usually reply within 1 day
-
bug frontend good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
oss-slu/lrda_mobile#294 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
hatchet-dev/hatchet#5179 ·
Maintainers usually reply within 1 day