• write settings component
• create link in nav bar

dependent on #16

Currently, app is working off seeded data and state changes do not persist.

• persist state changes through reload.
• evaluate level db vs local storage.
• evaluate adding/hosting/dealing with postgres

redux is lot of bloat for this little project. The goal is to replace that functionality with hooks/more localized state

once a user adds a new DisplayTimer, the nav drawer should automatically close.

do the reserach and find something better than looping-timer

fill out all the sections

• include data outline?

depends on #13

want to separate out the primary container from the connection to the redux store

😅 🤘

• write some marketing blurbs
• record video of use
• on rachelralston.com or github Pages?

in line

The code is getting a bit large and ungainly. Components can be filtered out & made more reusable.

make sure user can turn this off and choose different sounds
is this necessary?

our ui needs to be more customzable and design heavy than MUI is offering us.
consider: Is nextcss or sass a better choice?

None of the prop types are defined on any of the components :/

the total loops should only increment while timer is moving forward. If a user clicks 'previous' from the top it shouldn't increment the total number of loops

• figure out MUI's withStyles HOC
  • work with this on nested nav
  • api
  • overrides

background from Unsplash api