add meeting notes: visual design

meeting-notes/2025-05-25-visual-design-meeting.md

@@ -0,0 +1,40 @@
+# Fediversity design meeting 2025-05-25
+
+Present: {thijs,timon}@slik, {lois,kevin,kiara}@procolix
+​
+- timon: *demonstrates design*
+- timon: i already selected some relevant icons, selected colors for dark/light themes together with one accent color, a kind of professional blue. for branding the application we could either offer a pre-set selection of colors, or a color picker.
+- thijs: we can also display recent releases, e.g. to show newly released versions of mastodon.
+- kiara: it isn't obvious we can always update deployed applications automatically, as deployments involve user-selected options that may be non-trivial to migrate, potentially requiring new user choices - tho it may also be desirable to just give users more agency in choosing when to update applications, sooner or later.
+- thijs: maybe we could let users select updating policies separately by application.
+- kiara: in the future, perhaps.
+- thijs: will you write update posts, or the hosts?
+- kiara: maybe we could just link to the application developers' release notes, but on the other two... eventually both, maybe?
+- thijs: as for billing, does it make sense to show a 'used disk' meter with an upgrade button?
+- kiara: capacity such as disk space may in part be bound to deployed applications, tho for other parts like immutable storage we may be able to just meter actual usage, rather than requiring space be reserved upfront.
+- thijs: maybe you could also offer hosts different options for the billing.
+- timon: i made a help button including an FAQ, knowledge base and support. for the search field, would we like context-sensitive or general search results?
+- kiara: eventually context-sensitive as well, altho we haven't really gotten to the point of thinking about search so far.
+- timon: i also added an 'install app' button (maybe just app-specific install buttons), and notifications categorized like releases / changelog.
+- thijs: so the notifications can be categorized this way.
+- timon: the install button i imagined to be at the host level, so they can choose whether to install and offer an application to their operators.
+- kiara: the target audience of this web interface are the operators, as hosts already had the skills to install these applications.
+- thijs: hosts could instead use a config file to enable/disable certain applications.
+- timon: ok, then this button can be removed.
+- timon: what applications might you offer down the road?
+- kiara: *mentions some open-source and fediverse applications*
+- timon: how about number of applications?
+- kiara: operators could have multiple deployments, each of which could have different applications deployed.
+- timon: should we incorporate this into the design using a workspace switcher?
+- kiara: maybe, although i could imagine views where deployed applications might be grouped by such a deployment as well.
+- thijs: i think you could prevent various concerns by letting users focus on a single workspace at a time for now, in case these say pertain to different clients of theirs.
+- timon: we also made a mock-up for an application detail page, e.g. a mastodon one with some general description, potential user actions, maybe update/action history logs.
+- timon: the mock-up for the install view shows different steps, some sample toggles.
+- kiara: so far the designs have focused on a desktop setting, had you already considered responsiveness for e.g. mobile displays?
+- thijs: we will eventually work on a mobile setting as well, yeah, but the desktop case is easier to present, if not probably our first use-case here.
+- thijs: maybe koen will have some feedback as well.
+- lois: could you maybe send him the design already?
+- thijs: in fact, it can be found [at this link](https://www.figma.com/proto/AZbFAac2Xjxs3q1H3orXzO/Fedi-Design-system?page-id=97%3A1682&node-id=104-1754).
+- kiara: *mentions challenges wrt visualizing diffs in configurations / options*
+- TODO@procolix: offer example options for e.g. mastodon.
+- lois: i'll send an invite for the meeting with koen.