sillsdev / sillsdev/appbuilder-pwa
Improve update behavior
Open
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 14
- Forks
- 39
- Avg merge
- 4h 50m
- Merged PRs (30d)
- 5
Description
Steps to reproduce:
- Using Chrome on Android, when I used a PWA (posted to a server -- I can help with this), it offered to add the PWA to my homescreen.
- I closed the app on my Android phone
- I added a book to the PWA and republished it
- When I opened the app on my Android phone, it didn't show the added book. If I refreshed the page (pulled to refresh), then it did.
I did some research on improving the experience:
https://chatgpt.com/share/6a330332-8478-83ea-8160-806eea7dc541
Contributor guide
No contributing guide indexed for this repository
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.
Research direction
Start by reproducing the Chrome-on-Android PWA flow described in the issue, comparing reopening the app with manually refreshing it after publishing a new book. Trace the PWA update behavior to identify why reopened content is stale; done means newly published books appear without a manual pull-to-refresh.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- frontend, web-dev
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100