linusrachlis/fringr2-fe

Visual planning tool for attending shows in Toronto Fringe

fringr2-fe's Issues

Export selections to ical

Will this require a backend?

Support multiple festival data sets

• Needs a standardized format
• Needs a UI affordance to switch between festivals
• If done after #37, need to refactor the save mechanism to be "per-festival"

Indicate a show you haven't scheduled yet

Indicate if a show is sold out

This requires backend service constantly updating, or on-demand fetch and crawl from FE code

Better colours (and further distinction for colour-blindness)

Use min-width for calendar so it doesn't get too squashed on small screens (on mobile, have to H-scroll)

Restrict show times you're interested in

For example, if someone can't do week days from 9-5, or evenings after 10pm, they could filter out those show times.

UI complexity may balloon in proportion to flexibility...

Save selected shows and selected perfs

I think the best option is to encode them in the URL and update it live as you change state. Then you can copy the URL at any moment and share it to share your state.

If that's too much data for the URL for some reason, it could be in localStorage instead.

Or it could be in LS by default, with a button to copy a URL to share.

Automatic conflict detection

Examples:

• Warn if you select overlapping performances.
• Can you look up travel times progammatically with GMaps or another API? If so, could warn when perfs are too close together to travel between.

Continuously deploy

Set up a subdomain + Netlify

Button to expand/collapse additional info for all calendar items

Replace show data with Next Stage 2023 data

• Will require work on the scraper, https://github.com/linusrachlis/fringr2-scraper
• May require refactoring for data format changes

Confirm switching selection if show is already scheduled

Otherwise it's too easy to lose your previous selection by mistake

Easy directions lookup between venues

Options:

• select two calendar items to lookup map directions?
• provide a link for a given day that looks up map directions for all that day's venues, in the right order?

Compute unique colour from show title?

The idea is essentially "hashing" a given show title into the 24-bit colour space available. Cool, but not sure how good this UX would actually be.

Concerns:

• Some colours might coincidentally be too close together. However, given a realistic number of shows and a hashing algorithm with good uniformity, I think this is unlikely.
• How to account for colour-blindness? Depends how I solve #36. I was thinking to address that using shapes or other non-colour factors. Might be neat to compute unique shapes too, like Github's Identicons.

Address type errors

As a follow-up to #33 , address type issues and learn more about modern React/Typescript.

• Reinstate noImplicitAny rule
• Fix all type errors

Don't wrap show / venue names

They should be able to extend farther than the "end time" line, as long as that line is still clear. This will save lots of vertical space and allow seeing more performances without scrolling so much.

Note, they may still have to wrap for performances that are at the right edge of the screen. Not sure how to deal with that yet.