[GH-ISSUE #1145] Implement Progressive Web App (PWA) Functionality #331

Open
opened 2026-02-26 18:46:33 +03:00 by kerem · 2 comments
Owner

Originally created by @Gautam-Hegde on GitHub (May 4, 2024).
Original GitHub issue: https://github.com/documenso/documenso/issues/1145

Feature Description

  • To integrate PWA functionality(since documenso is now fully responsive).
  • users can have the feel and functionality of an actual native app

Use Case

  • quick access(caching feat) since they are all installable on the home screen

Proposed Solution

using @ducanh2912/next-pwa(maintained) its a fork of next-pwa

Alternatives (optional)

next-pwa package(not maintained)

Additional Context

No response

Please check the boxes that apply to this feature request.

  • I have searched the existing feature requests to make sure this is not a duplicate.
  • I have provided a detailed description of the requested feature.
  • I have explained the use case or scenario for this feature.
  • I have included any relevant technical details or design suggestions.
  • I understand that this is a suggestion and that there is no guarantee of implementation.
  • I want to work on creating a PR for this issue if approved
Originally created by @Gautam-Hegde on GitHub (May 4, 2024). Original GitHub issue: https://github.com/documenso/documenso/issues/1145 ### Feature Description - To integrate PWA functionality(since documenso is now fully responsive). - users can have the feel and functionality of an actual native app ### Use Case - quick access(caching feat) since they are all installable on the home screen ### Proposed Solution using `@ducanh2912/next-pwa`(maintained) its a fork of `next-pwa` ### Alternatives (optional) `next-pwa` package(not maintained) ### Additional Context _No response_ ### Please check the boxes that apply to this feature request. - [X] I have searched the existing feature requests to make sure this is not a duplicate. - [X] I have provided a detailed description of the requested feature. - [X] I have explained the use case or scenario for this feature. - [X] I have included any relevant technical details or design suggestions. - [X] I understand that this is a suggestion and that there is no guarantee of implementation. - [X] I want to work on creating a PR for this issue if approved
Author
Owner

@ElTimuro commented on GitHub (May 8, 2024):

  • @Gautam-Hegde, we thought about this as well
  • Question is, is the value of this really that big and worth the effort to maintain it? I'm not sure TBH
<!-- gh-comment-id:2100494696 --> @ElTimuro commented on GitHub (May 8, 2024): - @Gautam-Hegde, we thought about this as well - Question is, is the value of this really that big and worth the effort to maintain it? I'm not sure TBH
Author
Owner

@Gautam-Hegde commented on GitHub (May 10, 2024):

understandable 😅, should I close the issue for now until we reach a decision?

<!-- gh-comment-id:2103937095 --> @Gautam-Hegde commented on GitHub (May 10, 2024): understandable 😅, should I close the issue for now until we reach a decision?
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/documenso#331
No description provided.