balazsorban44 / ecatch-it2901 Goto Github PK

Description

As of now, @lighthousebot has no real thresholds set. We should figure out some good values/goals we should aim for, and set those in .travis.yml

Idea 💡: Check out some well-built, known PWAs' scores, and post them here in comments in the form of.:

Website: http://example.com

Category	Score
Performance	x
Progressive Web App	x
Accessibility	x
Best Practices	x
SEO	x

(score template here)

@toretefre @haavarol @elfingar @Virkz @tordsta @Mortefal

The fisher should be able to choose between norwegian and english language + other languages

Expected Behavior

There is some kind of a menu with options to select from, where the user can select a language that propagates through the entire user interface, resulting in a different language displayed.

Things to consider:

• Try to get the user's preferred language as default ( navigator.language object in the browser), and use Norwegian 🇳🇴 as a fallback.
• The application should remember the choice, even if it is different than the default system language, or the application has been closed.
• Add initial tests
• Define a workflow to write tests effectively

Areas affected

• frontend
• backend

Priority

The task got a low priority, but since its type (requires modifications to the core architecture) it has been moved up in the priority queue.

Size

At least 2 team members should work on this

PWA means that we need a notification to users that the website can be installed to the home screen.

Things to consider: https://developers.google.com/web/fundamentals/app-install-banners/

• images
• service worker with fetch()
• https

Expected Behavior

When the website is visited on chrome for more than 30 seconds the user shall get a "notification" in site that tells the user that the website is possible to add to home screen. If the users choose so, the website will be added to home screen and if the users open the site from home screen the website will look like a native app,

Areas affected

• frontend?
• backend?

Priority

When we have time

Size

1

Description

When we finally have a real domain name, use that instead of the one provided by Firebase 🔥

Places to check:

• Lighthouse
• meta tags
• env variables (.env, etc.)
• cors

Also set up the domain in Firebase itself:

• Point A records to Firebase in DNS settings of domain provider

To make the team's life easier, there is a need for a place, where local data can live and can be propagated to any components in the tree, no matter how deep those components are. This seems to be the perfect use case of React Context.

Things to consider:

• implement connection between Store context, and Service Worker

Expected Behavior

There should exist a Context Provider, (called Store) that holds all data used throughout the app in its state.
Furthermore, there should exist a Consumer (via withStore HOC and/or use of static ContextType)

Areas affected

• frontend
• backend

Priority

As fast as possible

Size

Probably everybody will make use of this, but the setup process is relatively easy and can be done by one person.