Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Research using Service Workers as a caching mechanism #189

Closed
2 of 8 tasks
Tracked by #78
, #77
...
Aveline-art opened this issue Mar 30, 2022 · 1 comment
Closed
2 of 8 tasks
Tracked by #78
, #77
...

Research using Service Workers as a caching mechanism #189

Aveline-art opened this issue Mar 30, 2022 · 1 comment
Labels
feature: Architecture Pertains to project architecture and settings PBV: dev all issues for engineering roles (devops, backend, frontend, db) role: frontend Pertains to frontend tasks size: 5pt Can be done in 19-30 hours
Milestone
04 - Project Setup

Comments

@Aveline-art
Copy link
Member

Aveline-art commented Mar 30, 2022 •
edited
Loading

Dependency

Overview

As a developer we need to investigate technology that can solve problems for our application. For this issue we will research and forward a proposal for how Service Workers can help us achieve our MVP.

Action Items

  • Read the instructions below to understand our MVP problem
  • View the resources below to perform the necessary research
  • Draft a proposal (in a comment on this issue) on the viability of using Service Workers to solve our MVP problem
  • In a meeting, get tech lead sign off on proposal

Resources/Instructions

MVP Problem:

As of now, permanent caching of user data is not possible. If a user enters data in the qualifier page, for example, this data disappears upon browser exit. Although browser caching represents a solution, it is not a reliable one as we do not control browser data. Therefore, this issue is to investigate how we can reliable, permanently save user data!

Resources
Using Service Workers
Progressive Web Apps
Progressive Web Application
Workbox
@Aveline-art Aveline-art added dependency This item depends on something role: frontend Pertains to frontend tasks feature: Architecture Pertains to project architecture and settings size: 5pt Can be done in 19-30 hours labels Mar 30, 2022
This was referenced Mar 31, 2022
Closed
Closed
@jenchuu jenchuu changed the title Reasearch using Service Workers as a caching mechanism Research using Service Workers as a caching mechanism Apr 5, 2022
@sdimran sdimran added this to the 04 - Project Setup milestone Apr 10, 2022
@Aveline-art Aveline-art removed the dependency This item depends on something label Jun 3, 2023
@Aveline-art Aveline-art moved this from 🆕 New to 📋 Backlog in P: CTJ: Project Board Jun 3, 2023
@ExperimentsInHonesty ExperimentsInHonesty added the PBV: dev all issues for engineering roles (devops, backend, frontend, db) label Jun 12, 2024
@nooriaali9
Copy link
Member

Closing this issue - since it is outdated/ not a priority anymore - based off of #552

@github-project-automation github-project-automation bot moved this from 📋 Prioritized Backlog to ✅ Done in P: CTJ: Project Board Aug 22, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
feature: Architecture Pertains to project architecture and settings PBV: dev all issues for engineering roles (devops, backend, frontend, db) role: frontend Pertains to frontend tasks size: 5pt Can be done in 19-30 hours
Projects
P: CTJ: Project Board
Archived in project
Milestone
04 - Project Setup
Development

No branches or pull requests
4 participants
@sdimran @nooriaali9 @ExperimentsInHonesty @Aveline-art