Clean idea and very practical. I like that the calendar data stays in the browser — that’s a thoughtful detail. Smaller-city search would definitely make it even stronger.

Thanks! And appreciate the feedback! You&#x27;re right the location database is currently limited to larger cities. I&#x27;ll take a look at closing this gap.

This is excellent, fantastic UX and implementation.The only thing is that smaller towns don&#x27;t seem to show up in the location search, which is a shame.10&#x2F;10

Awesome to hear! Let me know if you have any feedback!

Works great! Have used on many trips. Clean no frills UX

Scheduling meetings across multiple time zones has always been painful for me, especially across daylight saving time transitions. So I built a visual timeline that makes it easy to find overlapping availability.Add your locations, drag to select a time range, and share a link. Recipients see the proposed times in their local time zone automatically.A few things that might be interesting:* Location search over GeoNames with fuzzy matching using weighted edit distance, so typos and partial names still resolve correctly.* Shareable links encode the selected time range and locations in a base62 payload to keep URLs short and stateless — no database lookup needed.* Handles the annoying edge cases: DST transitions use the IANA timezone database, and 15&#x2F;30-minute UTC offsets (Nepal, India, Newfoundland) work correctly.* Google Calendar and Outlook integration, but all calendar data is fetched and processed entirely in the browser. Events are never fetched or stored on the server.Would love feedback on what&#x27;s useful, not useful, or could be improved!

Show HN: Timezone App – Visual meeting scheduler for distributed teams

Comments

eonebill

l1ng0

choogi

guymorita

choogi