-
-
Notifications
You must be signed in to change notification settings - Fork 26
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 progressive web app support #588
Comments
Hi. Thanks for the issue. The PWA app should be doable. What do you mean with a new documentation page? |
That's great to hear!
While not strictly necessary, I think a feature like this would elevate the tool a lot and be a selling point over competitors. As such, I'd be willing to document how to do it and why it's so nice. |
I added support for PWA to PodFetch. |
Awesome! Thanks for all of the continued work, love Podfetch 😄 |
It works great so far! Two things of note:
As for the documentation, would you like me to take a crack at this? I tried to open a PR but wasn't sure how to do so. |
Sure feel free to open a pull request. I'll try to fix the audio issues with the pwa. |
Clear and concise description of the problem
Using Podfetch on mobile is an incredibly common (if not the dominant) use case. But Podfetch doesn't have a standalone app, nor is that likely.
A great alternative would be a progressive web app, which allows opening websites as their own standalone "apps" on mobile. A combination of this (plus a new documentation page I would be happy to contribute to!) could give Podfetch an "app" feel, improving usability
Suggested solution
Implementing the standalone app from this guide would likely accomplish it, alongside custom icons, etc.
Alternative
No response
Additional context
No response
Validations
The text was updated successfully, but these errors were encountered: