-
-
Notifications
You must be signed in to change notification settings - Fork 187
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
[Feature]: Add "Progressive Web App (PWA)" support #370
Comments
@plantindesk, all icons are generated from the main PWAs are something I did not explore before so I'm unable to assist with the issue you mentioned it #353 (comment) in the video. It looks OK to me. What's the problem? Btw we can use privacy.sexy as app name, matching the package.json. Thank you for leading this through your contributions ❤️. |
@undergroundwires I need to give you access to my Project IDX and for that i need your Email Address. Also I accidentally put the slogan in name , Sorry. |
You can find my e-mail here here is the discord link. You can also consider creating a PR to work on the code. It would simplify the work. |
I am extremely sorry. I should have seen that |
Ok I tried to give access to my Project IDX but was unsuccessfull cause it needs gmail account. I have successfully made a pull request that contains idx directory, query parameters and manifest.json |
Problem statement
Support Progressive Web Apps (PWA) to improve accessibility and user experience on Android devices. This feature would help improve the app's usability on various Android platforms, paving the way for Android support (#324).
Proposed solution
Implement PWA support to make the app installable on Android devices. This should include offline capabilities, and an icon on the home screen, leveraging service workers for background syncing and caching strategies.
Alternatives considered
Have you considered any alternative solutions or features?
Additional information
This feature request is linked to ongoing discussions about Android support (see issue #324) and some information from #353 which mentions also performance concerns highlighted by Lighthouse testing, such as the need to minify JavaScript, which could be addressed during the PWA implementation process.
The text was updated successfully, but these errors were encountered: