Comment by fodkodrasz

Comment by fodkodrasz 6 days ago

3 replies

Really nice, but it is unclear to me how time is represented with regard to timezones.

Some large countries may have multiple time zones, and itineraries can be confusing, this needs consideration from data modeling and ux side as well. The first glance at the UI didn't make it obvious for me how this is handled, I suppose local time is used always.

kenrick95 6 days ago

Yeah this is not that obvious, but the selected 'destination time zone' is the only time zone that one will be working with when planning the activities within the trip. (When inputting/reading the activities' time zone, they are all the destination's time zone)

The only local time zone used is at the comments (but hopefully it is clearer since I show the time zone offset there? I don't show it on the events since I feel it could be way too verbose)

I understand that there could be case where one's trip crosses multiple time zones, but at this moment that wasn't supported yet.

  • pimlottc 6 days ago

    At the very least, you have to consider time zones for travel to/from your destination, as that's quite often a different time zone for international travel. Don't want to miss your flight...

    • kenrick95 5 days ago

      That's a very valid use case I haven't thought of. Thanks for pointing it out!