calendly and savvycal are mainly calendar apps and work well for the scheduling use case only. However, this is only one use case that a global clock can be use

calendly and savvycal are mainly calendar apps and work well for the scheduling use case only. However, this is only one use case that a global clock can be used for. Another use case that those apps don't solve is global events e.g. SpaceX launching a rocket at 11am ET, or the Apple event yesterday at 10am PDT. If I don't live in those time zones, I don't know when those events are going to take place in my time. Thus the idea of eliminating time zones and replacing that with a global clock would solve many more use cases than scheduling. There is no need to store datetime or locale for the clock to work. The clock knows where you are, using your sys time, or GPS, and according to that it rotates the UTC layer that is represented in letters according to you location. This means the clock adjusts itself for you in order to give the right local-global (UTC) time mapping. And that's all done by the clock's algorithm that manages the rotation. The main reason I'm using letters instead of numbers for UTC is to distinguish between local and global hours, simply for better communication. That's how it works :)