I suggest using a 24h format for the clock to correspond to international standards. For the timezones, I would just use an indication of the time in UTC next to the city, for example, Berlin: UTC+2.

There's more info here on time standards here: https://en.wikipedia.org/wiki/ISO_8601

This look a bit confuse. Please review which functionality you want to offer, and how it will work on mobile form factor and on desktop.

Do we want time, stopwatch, alarms and timers to be in the same app? We already have KTimer (h[[ https://phabricator.kde.org/M130 | ere a mockup) ]]. Should we develop the remain apps standalone like KTimer or merge it in this "Clock" app?

I like what I am seeing in theory. I would love to see an interaction map for this app just to understand how you go through different faces of the application.

For the different apps l would also make different tabs like in vvave where you have album, artist, playlist views in different tabs with an icon tab indicator.

For time app an flat worldmap with pinns where you have the time on it would be nice. There was an kde4 widget. Cause have different times mean that you want to know the time somewhere else in the world.

For wakeup clock i would use an old-school alarm bell for each alarm.

For stopwatch an stopwatch

And for a timer also some oldscool countdown layout.

But the first question would be, what would you like to have. Second question how it would be easy to understood

I think that KTimer and the timer in this clock can exist as separate applications. This is more like the AOSP default clock with only a basic timer. KTimer can offer more advanced stuff like multiple timers and running commands.

The global menu I am using is already acting like vvave's tabs.

For time app an flat worldmap with pins where you have the time on it would be nice. There was an kde4 widget. Cause have different times mean that you want to know the time somewhere else in the world.

I'm not sure what you mean. Could you clarify or give a link to the widget?