-
-
Notifications
You must be signed in to change notification settings - Fork 12
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add PWA capabilities for offline access #1580
Comments
Sorry, I think I missed your issue. I build that project to have access to full content in RSS that I then read offline after having synced them on my mobile. But on a daily basis I never go to the website. Because I'm using RSS provided by it only. That's why I think adding PWA might be a bit overkill. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
You mention reading these feeds on the subway, presumably you have your laptop and are running locally.
What would be really cool, of course, would be to have a stand-alone mobile app that fetched stories from the f43.me server in the background.
To this end, I updated my fork to Symfony 6.4 and replaced Webpack with AssetMapper (woohoo, no more node! no more build step!) Creating the offline app won't be hard, though the background sync part is something I'm still learning.
I tried to upgrade to Symfony 7, but there are some issues with graby that I are being worked on.
This really is a cool application, thanks again for releasing it. I look forward to your feedback about a PWA, it's obviously a somewhat big decision because the Symfony bundle that I'd use to create the PWA requires AssetMapper and Symfony 6.4 || 7.0
The text was updated successfully, but these errors were encountered: