Improve Flights

[dcramer]

Built a quick MVP, but we want some more details:

1. Should keep you within the flight details as best as possible, that is it should be easy to record a tasting/etc and return to the flight.
2. Should capture the flight as part of the tasting details.
3. Should show other people who have participated in the flight, maybe some stats?
4. Maybe include a way to rate a flight?

[dcramer]

https://peated.app/flights/8xuhjsjpgie7

Sentry hosted an event in SF for employees and did a tasting, so something like this would have been nice. Especially if we enrich the display and make it more fluid.

[ghost]

Hi @dcramer,

I've thoroughly analyzed Issue #77 regarding the enhancements to the flight tasting MVP. The requirements are clear, and I can see the potential these improvements offer, especially in light of the Sentry event in SF.

To tackle this, I've come up with two possible approaches:

Approach 1:

• Modal Input System: Implement a modal to allow users to record their tasting details without leaving the flight details page. Once done, closing the modal will bring them back to the flight details.
• Database/ API Enhancement: Extend the schema to ensure each tasting note is automatically linked and stored with its associated flight detail.
• Participants Display: Add a sidebar or section on the flight details page to display other participants using avatars or names. Interactive elements can provide quick stats and possibly a ratings leaderboard.
• Rating System: Incorporate a star or slider-based mechanism for users to rate their experiences directly within the flight details.

Approach 2:

• Slide-in Panel: Use a slide-in panel for tasting notes, maintaining the context of the flight while users input their experiences.
• Tagging System: Ensure each tasting note is automatically tagged with its flight detail.
• Dynamic Stats Bar: Introduce a bar that updates in real-time, offering quick insights about participants and average ratings.
• Interactive Rating Mechanism: Think emojis or icons for different satisfaction levels, offering a richer user interaction.

Does this align with your vision for the improvements? If these suggestions resonate, I'm ready to delve into this issue. Could I kindly request assignment, and if there are more specifics or details you'd want, please share?

Thanks for your consideration! Muditya Raghav

[dcramer]

I haven't given it much thought, and have mostly been incremental with changes given its more or less just beta right now.

• I think solving the database layer is a no-brainer - we need to link a tasting to a flight to do anything, so thats an obvious change that has to happen.

• For participants, makes sense and I think is interesting. We'll just need to make suer to respect the privacy settings (e.g. only show users who are public or you're friends with).

• Rating I have second thoughts on. We could rate a flight, but is that useful? I guess it could be, but do we need it? I am not sure I have a strong opinion.

One note is that a lot of he UI challenges come from the need to support both mobile and desktop flows, and those aer quite often very different. I haven't gotten a good system down that keeps it stable when making changes, and even right now I think there are some mobile bugs.

[dcramer]

Few updated thoughts:

1. Flight details should showcase which flights you've already captuerd tasting notes on.
2. Clicking a bottle should pop a modal/slideout (we dont have UI for this yet, just rough thinking) - keeps you on the page more eaisly.
3. Slideout+table should probably show a "Record Tasting", and disable that once you've recorded it for the given row.

[dcramer]

I added the slide out + tracking of flights with tastings. Still need to have it showcase which ones you've recorded already, and pull in some interest stats about flights. Almost feels usable though!

Oh, and def needs some mobile improvements on the slideout pattern. A lot of work I need to do on component standardization yet so its easier to make stable UI.