Tobias Steckenborn (Jul 01 2026 at 07:49): Tobias Steckenborn (Jul 01 2026 at 07:49):Given different platforms and deployment targets, does someone feel capable of starting a foundation for a shared design/visual language?
Reading through the other threads it seems like we need a description of fundamental elements (modal, popup, tooltip, (…) and eventual visuals e.g. like tailwind) if we‘d want to share visual consistency between web and gui, that needs to be abstract enough to leave the concrete implementation to a potentially platform specific implementation :sweat_smile:?
Anton (Jul 01 2026 at 11:54):I don't have time to do this myself but I do like the initiative :)
Tobias Steckenborn (Jul 01 2026 at 13:20):Given I was on the go a bit more context to my thoughts here:
There are elements of an application that might be recurring on most graphical interfaces. Samples could be alerts, autocompletes, avatars, buttons, checkboxes, dialogs, drawers, forms/inputs, some sort of navigation, some sort of popover, input fields, tooltips, toasts or the like.
All of these might come with corresponding information such as e.g. where to position them, how to style them, potentially how to animate them (maybe also in relation to something else, e.g. if you reach a nav menu item from the left you might want to animate out the previous to the right and in the new one from the left and so on).
Not all of these will work on all platforms (?in the same way?). These might apply for websites, desktop apps and potentially mobile apps, likely not for clis.
If I'd want to create an app and distribute via mobile, desktop or browser it could be nice to reuse as much as possible atleast from the principles (e.g. position, behaviour, animation durations?) while other things might not be directly applicable.
So potentially if someone has experience with that it likely would be a four step approach (very simplified):
Last updated: Jul 23 2026 at 13:15 UTC