search

revelrylabs / bn-mobile-react

BigNeon React Native Repo
BSD 3-Clause "New" or "Revised" License
2 stars 8 forks source link

Attendee - My Tickets - Do not show static information about a ticket more than once #797

Open iamjoshfrank opened 5 years ago

iamjoshfrank commented 5 years ago

via @bryanjos on #765:

Why? The information stays the same. There is a bug caused by loading a huge gif multiple times. We can still carousel the dynamic info

iamjoshfrank commented 5 years ago

@bryanjos - I'm not sure I understand. Screen shot / capture or point me to an example? I trust you and assume this is a good idea, I just don't understand it enough yet.

bryanjos commented 5 years ago

These screenshots may help. The app has to render the image for every single ticket. It's not really needed besides for design purposes.

Simulator Screen Shot - iPhone Xʀ - 2019-05-23 at 14 18 23

Simulator Screen Shot - iPhone Xʀ - 2019-05-23 at 14 18 31

iamjoshfrank commented 5 years ago

@bryanjos - ah, now I understand what you mean.

I wonder how common a use case is it for a single Event Ticket Holder to be holding multiple tickets to the same event, outside of maybe "I have 6 tickets for myself, my kid, and my kids' four friends to go see this concern."

Like, would we be re-designing and re-engineering this view to solve a problem that only starts to present itself when an Event Ticket Holder has above ... 10? 20? 40? ... tickets for a single event?

I was forced to use the MLB Ballpark app for our tickets to the USWNT soccer game at Busch Stadium last week. I wonder if I could look at that to get an example of another digital wallet in the wild. I vaguely remember having a similar carousel of tickets situation, but maybe once the first was scanned I didn't have to flip through to have them scan each individually.

Which sparks an interesting idea for the Doorperson, maybe?:

iamjoshfrank commented 5 years ago

Maybe I'll grab my small whiteboard and try to sketch up a slightly different view for this ticket carousel that doesn't rely on re-drawing the image for every single ticket.

iamjoshfrank commented 5 years ago

After discussion, we think this is probably true:

Like, would we be re-designing and re-engineering this view to solve a problem that only starts to present itself when an Event Ticket Holder has above ... 10? 20? 40? ... tickets for a single event?

Leaving this open so that I can spin out this idea into a new Issue: