# GlobalTimeZones — Full Site Content

> Beautiful timezone tracking for the Mac menu bar. Compare times across 400+ cities, see working-hours overlap with color-coded availability, and plan meetings with a ±24h time slider in 15-minute steps. One-time purchase ($4.99), no subscription, free lifetime updates. Requires macOS 14 Sonoma or later (Apple Silicon & Intel).

GlobalTimeZones is a native SwiftUI menu bar app by ProductShake, LLC. It runs entirely on-device — no timezone data is sent to any server.

## Product (https://globaltimezones.app/)

### What it does

GlobalTimeZones lives in the macOS menu bar — no dock icon, no window management. Click the menu bar icon to see the current time in every city you track, each with a color-coded availability status.

### Features

- 400+ timezones: every major city covered; search by city name, country, or alias (e.g. type "Tanzania" to find Dar es Salaam)
- Smart availability: four color-coded statuses — working (green), near end of day (orange), off hours (gray), sleeping (red) — based on customizable working hours
- Time slider: plan ahead ±24 hours in 15-minute steps, with haptic feedback; quarter-hour precision keeps half-hour offsets like India (UTC+5:30) exact
- Native macOS: built with SwiftUI, feels like part of the system
- Free lifetime updates delivered automatically

### Pricing

- $4.99, one-time payment. No subscription. One license per Mac. Secure payment via Stripe.
- Requirements: macOS 14 Sonoma or later, Apple Silicon & Intel.

### FAQ

- Free trial? No, but there is an interactive demo on the homepage. One purchase, lifetime updates.
- macOS versions? macOS 14 (Sonoma) or later, Apple Silicon and Intel.
- How many Macs? One license per Mac.
- Updates? The app checks automatically and notifies you when a new version is available.
- Support? Email support@globaltimezones.app or X @williamengbjerg.
- Privacy? Runs entirely on your Mac; no timezone data is sent to any server.

## Guide: How to Schedule Meetings Across Time Zones (https://globaltimezones.app/guides/schedule-meetings-across-time-zones)

Why timezone math goes wrong: daylight saving time shifts on different dates per country (the US moves clocks ~2 weeks before Europe in spring); not every offset is a whole hour (India UTC+5:30, Nepal UTC+5:45); countries change DST rules regularly. Never compute offsets in your head — read current local times from a tool tracking the IANA timezone database.

Steps: (1) Find the working-hours overlap — block out each participant's local 9–17 and intersect. Three-region calls (e.g. San Francisco / London / Singapore) often have no shared window, so someone must flex. (2) Rotate the pain — don't let the same region always take the 7am call; put the rotation in the invite. (3) Propose times in the recipient's local time. (4) Plan in 15-minute increments when working with half-hour-offset regions.

Checklist: check today's offset (DST), stay inside or adjacent to working hours, rotate bad slots, state times in local time, offer async alternatives.

## Guide: Best Menu Bar World Clock Setup for Mac (https://globaltimezones.app/guides/best-menu-bar-clock-apps-mac)

What macOS gives you out of the box: the menu bar clock shows only your local timezone; World Clock widgets (Sonoma+) show up to four cities but hide behind windows and show raw times only; Calendar's secondary timezone column helps for one extra region; Spotlight/Siri answer one-off lookups.

Where built-ins fall short: they all answer "what time is it there?" — but the real question is "can I talk to this person right now?", which requires knowing working hours and doing offset math.

What a dedicated menu bar world clock (GlobalTimeZones) adds: color-coded availability statuses instead of raw times, a ±24h planning slider with 15-minute steps, 400+ searchable cities, native SwiftUI, fully on-device. $4.99 one-time with free lifetime updates.

Bottom line: occasional checks → built-in widget is enough; one region, mostly meetings → Calendar secondary timezone; daily coordination across time zones → GlobalTimeZones.

## Guide: See Team Availability Across Time Zones (https://globaltimezones.app/guides/see-team-availability-across-time-zones)

The four statuses: green = working (inside working hours), orange = near start or end (the hour before work starts / after it ends), gray = off hours, red = sleeping (~22:00–06:00 local). Working hours are configurable in Settings (default 9–17) and apply to every tracked city. Cities can be renamed after people ("Priya" instead of "Kolkata"). The city picker has a "working now" filter to find who is currently available, and the ±24h slider previews statuses at any proposed meeting time.

## Guide: UTC vs GMT (https://globaltimezones.app/guides/utc-vs-gmt-difference)

GMT is a time zone (Greenwich, UTC+0); UTC is the atomic time standard all zones are defined against. Their clocks agree, but: the UK leaves GMT for BST (UTC+1) in summer, so "3pm GMT" from a Londoner in July usually means BST; abbreviations like CST and IST are ambiguous across countries; software, aviation ("Zulu"), and logs always use UTC. Safest practice: schedule by city name ("9am New York time") and let tools resolve DST via the IANA timezone database.

## Guide: Best Times for US-Europe-Asia Meetings (https://globaltimezones.app/guides/best-times-us-europe-asia-meetings)

Typical windows (DST shifts these ±1h): US East–Europe: 9:00–12:00 NY = 14:00–17:00 London (the easy one). US West–Europe: one honest hour, 8:00–9:00 Pacific = 16:00–17:00 UK. Europe–India: 9:00–12:00 Berlin = 12:30–15:30 Mumbai (mind the half-hour offset). Europe–East Asia: 8:00–10:00 Berlin = 15:00–17:00 Singapore. US–Asia: no overlap — go async by default, or use US evening = Asia morning (18:00–20:00 Pacific = 9:00–11:00 next-day Singapore), and rotate the pain. All three regions: ~7:00–8:00 NY = 12:00–13:00 London = 20:00–21:00 Singapore.

## Guide: Work Remotely From Another Time Zone (https://globaltimezones.app/guides/work-remotely-from-another-time-zone)

Define and publish 2–4 overlap hours with your team's core day; set a hard end-of-day once, publicly; go async by default outside overlap. Make work visible while HQ sleeps: end-of-day written updates, artifacts (PRs, docs, recordings) over meetings, questions asked before your evening so answers arrive overnight. Re-check overlap every March and October when DST shifts it.

## Guide: Daylight Saving Time Explained (https://globaltimezones.app/guides/daylight-saving-time-explained)

Regions switch on different dates: US/Canada spring forward 2nd Sunday of March and fall back 1st Sunday of November; EU/UK use last Sunday of March and last Sunday of October; southeast Australia and NZ run opposite (roughly October–April); India, China, Japan, Singapore, most of Arizona, Hawaii, and Queensland never change. Danger weeks: mid-late March (US moved, Europe not — NY–London temporarily 4h) and late October–early November (reverse). Sydney–London shifts by two hours across changeovers. Safe practice: pin recurring meetings to one named city, avoid seasonal abbreviations like EST/CET, verify offsets live from the IANA database.

## Guide: Half-Hour Time Zones (https://globaltimezones.app/guides/half-hour-time-zones)

India and Sri Lanka are UTC+5:30, Myanmar +6:30, Iran +3:30, Afghanistan +4:30, Newfoundland -3:30 (with DST), central Australia +9:30, Nepal +5:45 and Chatham Islands +12:45 (quarter-hour). Nearly two billion people live on non-whole-hour offsets. Consequences: hour-rounded mental math is 30 minutes wrong, hour-stepping tools cannot land on Indian times, "IST" is ambiguous (India/Israel/Ireland). Schedule on the quarter hour and use tools with 15-minute precision.

## Guide: Async Communication Across Time Zones (https://globaltimezones.app/guides/async-communication-across-time-zones)

With little or no overlap, every unclear message costs a day — write messages that need no follow-up (context included, explicit ask, default action with deadline). End-of-day written handoffs turn the gap into a 24-hour relay. Decisions live in documents with comment deadlines, demos become recordings; live calls are reserved for sensitive feedback, incidents, and relationship-building, rotated fairly. Use scheduled send and check availability before pinging.

## Guide: Freelancer Time Zone Tips (https://globaltimezones.app/guides/freelancer-time-zone-tips)

Every deadline gets an explicit timezone in both calendars. Publish availability in the client's local time. Promise turnaround in business days instead of fake 24/7 presence. Offer call slots in the client's time and cluster international calls. Watch DST weeks and quarter-hour offsets for Indian clients. Sell the overnight-turnaround advantage of the offset.

## Guide: Track Time Zones While Traveling (https://globaltimezones.app/guides/track-time-zones-while-traveling)

Before departure: add destination, home, and team cities to your world clock; review next week's calendar in destination time; save local plans with the destination's timezone. Bookings print local times — compute layovers from offsets. During the trip keep two anchors, local and home, and glance at the other person's clock before calling. Schedule critical meetings for day 2–3 after long eastward flights, not landing day (~a day of adjustment per zone crossed).

## Company

- Maker: ProductShake, LLC (https://productshake.com)
- Other products: VPN To US (vpntous.com), ClawHost (clawhost.online), MakePost (makepost.com), Prompt Pro (trypromptpro.com), Claude Kit (getclaudekit.com), Active Now (activenow.app)

## Support

- Email: support@globaltimezones.app
- X: @williamengbjerg