a10waveracer / bellhop Goto Github PK

The "Now" price on the card identifies which day and "AM/PM" you are at via your current browser's time.

Need to consider that some people are in different timezones, so there is a gap where the Now is no longer accurate.

Example: User A is in Eastern time, User B is in Central time. The time is 12:30PM Eastern.

• User A will see no current "Now" price for User B
• User B will see an incorrect "Now" price for User A

Need to update set_prices.js to add logic based on the "timezone" value sent in the "stalk-data" class.

If we want to support the first time buyer, we'll have to walk through the flow on how this feature would work.

The main difference in the prediction API seems to be that we have no chance of Large Spike on a week where first time buyer is checked.

If we don't want to implement the backend and UI, could consider putting a warning or disclaimer somewhere.