snesjhon/mediadiary

MediaDiary

A Keep track of all your favorite media.

Goals

• An extensible way of tracking your media by exposing an API and giving you tracking abilities.
• Here are some common ones that you can add if you subscribe yourself to an API
• I thought that it'd be great to add a user ability for free and limited by day. Rate limited in the intermin, but then for free if you provide your own API keys.

mediadiary's Issues

Media Counter isn't showing the appropriate data

It should show the count of the items as well as sort.

v1: Redirect if not logged in

Routing

Add routes to the following

/
/{year}
/profile

Choose your own Rating system

It'd be cool to let the user decide their own rating system. Not everyone likes the 5 stars.

Would be awesome to let them decide and have that change in the UI.

Probably will have to override everything and reset them.

Ability to edit/delte media object

We should be able to provide a pleasant edit experience.

Add more information about the About page

The welcome screen doesn't really have any relevant information. Should add a better way of introducing what mediaDiary is all about.

v1: Add Activity router

Problem

• An activity section for all the nice stats that we can gather from this data.

Add different types of Media Filters

Different kinds of filters that allow for a pleasant experience to view your media.

Better Auth

The current auth architecture works, but it creates redundant renders for mediaDiary main component. So it'd be great to move to next/auth or do a SSG to assure these renders don't happen.

`useUser` causes unnecessary renders.

Although the user works and the UI gets the appropriate user, there's a bunch of renders because the hook renders regardless if we have a user or not.

v1: Add swipes

Problem

Although now that everything is within modals/drawers, there isn't an appropriate way to close things.

Let's use react-swipeable

v1: Something wrong with Edit

Problem

• When I save without information the loader spins and nothing happens

v1: Pagination

Pagination using swr is important to keeping the "downloaded" items to a minimum

Day Modal should always be loaded.

Problem

• I feel there's a lag between what I'm seeing and how it looks like when I click on an item. Something weird might be happening. So I'm thinking maybe the Day modal needs to be loaded properly instead of a conditional loader

going "back" in mobile safari has FOUC

Problem

Not sure why, but there's a weird issue with mobile safari and Drawer Modal

Add error logging for information

There isn't any proper error logging in place. Need different ways of determining what logging architecture would be in place.

Firebase title parsing

If there's a . in the title of an album that's been parsed, then firebase takes it and creates a separate object from it. I think it has to do with the parsing and encoding of the title when saving. Since Madlib Pt.2 the . gets put into an object. lol

v1: Editing _after_ saving

Problem

• After I edit and save an item. The old data is still persistent

Episode Support for TV

Add support for TV episodes, while also having the ability to do whole seasons

Add filters to view specific mediaTypes

@ jennifer's idea.

It would be good to hide/filter specific mediaTypes. It would allow to show only relevant information.

This would also need to be obvious to the user and a quick way of reverting back.

Fix the navigation onFocus Error

Main diary click goes to route instead of modal

Problem

I left the main onClick for mediaDiary to go to the route instead of modal

Add Preferences Site

I should be able to add a preferences site to decide what kind of information to put.

This should be an initial setup for the preferences page and doesn't need to be fully completed.

Add `/[user]` as the homepage

Instead of using /home as the "homepage" it should be your username

Move to a single Document instead of multiple collections

This is a hard change, but I believe in order to scale properly I'd have to keep a single record and do away with the media portion. This is because as I paginate I can't see myself paginating accurately as I go through.

And I have to paginate to keep the DOM from not being completely slow. The item still loads and I can add a loader, but man that's just not what I want to do.

Add swipe gestures

Mobile Modal

Mobile modal doesn't really work for anything. Mostly relies on width/height of the viewport.

Need to move this to a more cohesive style where it flows better while adding/viewing a record.

Year add/delete

Currently there isn't a way of adding/deleting a year. Should be the same way that we "create" one, we don't need the years to be edited.

Probably want some kind of warning about deleting everything in that store.

v1: Desktop Mode

Desktop mode doesn't look great. Because I've been focused strictly on mobile mode.

Non-Material UI icons

MaterialUI Icons are huge, let's remove them.

User Signup/Delete Flow

We need a way to create, and delete users.

If you're in home you can click signup, and it'd take you to the sign up page,

/ -> /signup -> /home
/ -> /login

The inspiration should be twitter.

v1: Remove SWR-firestore in favor on next api

Problem

• It looks like there's little to no caching using swr-firestore because it's using xhr with different queries. I thought otherwise. Thus i'm getting a ton of reads everytime I'm loading the app. This is unwanted.

Solution

• I'm going to use : https://leerob.io/blog/nextjs-firebase-serverless

Explore Parcel

Maybe webpack is adding a lot of crud that we don't need. Would be good to explore.

v1: Change Auth Flow on Spotify API

Problem

• Add media isn't working properly
• This would be a good way to start introducing tests since I have most of the UI built out.

Image enhancements - Progressive/Placeholder

• add a progressive image for the preview images
• Add placeholder images for images that don't work

Style updates

Currently there isn't any hovering information that let's the user know that there is something to be clicked on. This should change to let the user know that there is proper information.

Add API information when opening an item

Settings Page

Detailed Description

• The settings page should have a details options for when a user is using the system.
• Sections
  • Change Name
  • Dark Mode / Light Mode
  • Scary Section

Context

• I think it'd be great to have these initial options to be able to change certain options

Possible Implementation

Not obligatory, but suggest an idea for implementing addition or change

• Use fb realtime db to add /users/$UID/preferences/OPTION. Since I don't need to verify that this option exists it'd just override whatever is there or create it

v1: PWA Icon

Problem

• None of the icons work for the PWA logo. This should be an easy fix by updating the manifest.

Theme switcher

Currently no ability to theme switch

Add a "landing" page, when trying to redirect people

I need a landing page before trying to redirect. Because I don't want to see the homepage before I get redirected.

Global - Remove styled-system/component in favor of material-ui

Editing stars not working

Editing the stars while in editing mode isn't saving properly and you stay in loading mode.

Mobile Version

There isn't a mobile version for this app, and this is a main milestone

Drawers for all Search/Edit/Log

• Better drawer support

Layout Fixes for MediaDiary component

The styling for the mediaDiary component needs fixing since there's no overlap and the padding for the :hover isn't the best. Let's fix it.

v1: Fix pagination

Problem

• Pagination wasn't working with filterBy

Support "Binge Watching" for TV

Idea

• Binge watching would batch up multiple TV episodes into one.

Thoughts

• It'd be good to have multiple tv entries be combined into one, but how would we handle the rating?
• posters might be able to be stacked
• Could also add a "add more episodes" in the actual entry?

Remove routes

• Search, log, edit, don't need specific routes. I thought this was a good idea for modal, but it's just redundant

List was out of order

Regression from #82 that I didn't format the order correctly.