burnett2k / work-timer-react Goto Github PK

mention:

• How to get app running
• Architecture of the app
• Where it is running

Add features of a progressive web app to allow a better user experience. This means

1. The app should work fine offline
2. The app should load over HTTPS
3. The app should have a web app manifest file

More info here

It would be a really nice feature to add which would help you focus and determine if you met your goal

This project is getting hella old and I need to bite the bullet and modernize it, or re-write it again.

It's a bit weird that you cannot see the user you are logged in as

Need to move setInterval to a separate thread so it won't be throttled by browser optimization. This will require pulling timer funcionality into a separate file, and creating a worker out of it. Must communicate with it using messages rather than react props like I'm currently using.

More info here: https://www.fullstackreact.com/articles/introduction-to-web-workers-with-react/

It was fun getting all this working on a digital ocean droplet, but It's kind of fragile and seems to break all the time.

I want to look at how to simplify this stack and potentially reduce cost.

Ideas:

• host the frontend on a CDN instead of serving from a web server. There's no reason to be using a web server if it's just passing back a bundle of JS and html.
• Move dns Hosting over to route53?
• Consider breaking up the repo into frontend and backend repos for simplicity
• Consider whether you even want to keep this around

implement offline caching so that the app will continue to run just fine and return a 200 response even though there is no internet connection

In some situations this is not ideal. 1 case where this shouldn't happen is:

• started a timer
• realized you aren't logged in
• login

The login causes a page refresh so your timer stops. Maybe I should store some kind of state that checks what the last known status was and continues the timer if it was "Running"?... This should be pretty easy to fix.