# RadiFedi: Storybook of radically innovative federated UX **URL:** \ **Category:** 💡 Ideation\ **Tags:** idea, list\ **Created:** [April 16, 2023, 11:35am UTC](https://discuss.coding.social/t/radifedi-storybook-of-radically-innovative-federated-ux/323 "2023-04-16T11:35:41Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![aschrijver](https://discuss.coding.social/user_avatar/discuss.coding.social/aschrijver/32/3_2.png) [@aschrijver](https://discuss.coding.social/u/aschrijver)\ **Post date:** [April 16, 2023, 11:35am UTC](https://discuss.coding.social/t/radifedi-storybook-of-radically-innovative-federated-ux/323/1 "2023-04-16T11:35:41Z")
An idea triggered by [fediverse-ideas/#16: Horizontal timelines](https://codeberg.org/fediverse/fediverse-ideas/issues/16) and taking inspiration from MercuryOS: > **[MercuryOS](https://www.mercuryos.com/)** > > Mercury is a reimaging of the operating system as a fluid modeless experience drive by human intent. [https://uxdesign.cc/introducing-mercury-os-f4de45a04289](https://uxdesign.cc/introducing-mercury-os-f4de45a04289) ## Explore innovative UX designs What if we launched a Storybook website and encouraged developers and designers to create radical new UX/UI designs and related components to surface federated services and solutions. We might offer a set of tools and guidelines for the development, maybe a standards-based techstack. - E.g. based on [NodeJS/React Storybook](https://storybook.js.org/) or [Elixir Phoenix Storybook](https://github.com/phenixdigital/phoenix_storybook). - E.g. based on de-facto standard [Block Protocol](https://blockprotocol.org/) that Github Blocks is also based on. - E.g. designed with [Penpot](https://penpot.io). Would be a way to get more Designers involved in thinking about Fediverse Futures. The site might be hosted at [fedi.foundation](http://fedi.foundation) or a subdomain thereof. See also: [From silo-first to task-oriented federated app design - Fediverse Futures - SocialHub](https://socialhub.activitypub.rocks/t/from-silo-first-to-task-oriented-federated-app-design/1457) ---
**Author:** ![aschrijver](https://discuss.coding.social/user_avatar/discuss.coding.social/aschrijver/32/3_2.png) [@aschrijver](https://discuss.coding.social/u/aschrijver)\ **Post date:** [January 2, 2024, 7:33am UTC](https://discuss.coding.social/t/radifedi-storybook-of-radically-innovative-federated-ux/323/2 "2024-01-02T07:33:40Z")
I just [commented](https://matrix.to/#/!RgLxjxIyunwZCUQQGy:matrix.org/$9AfDtbBW_JnzmFn-SFZhrH33HxVeSV6vfVgnhkO5lP0?via=matrix.org&via=catgirl.cloud&via=public.cat) to Semantic Fedi chatroom, and also wrote 3 [toots](https://social.coop/@smallcircles/111685243772240522) on the matter.. * * * > **[Displaying content as a graph: An exploration](https://thisisimportant.net/posts/content-as-a-graph/)** > > Most web content is displayed as a strict hierarchy, tree-based or otherwise. What if it wasn't?An exploration into the advantages of graph-based content design, the numerous pitfalls, and a few case studies along the way. I bumped into the article via [this HN discussion](https://news.ycombinator.com/item?id=38834780), making a fairly elaborate exploration of the concept. When it comes to envisioning a wholly LD-based Fediverse I imagine that this technical aspect would allow creation of innovative social experiences that go well beyond UX we are used to. A newcomer exclaiming in delight “Wow, what the heck is this?” and some reply-guy answering “This, my friend, is the power of Linked Data that we talked about for all these years”. That step, projecting the vision, is what I find is mostly always missing in LD ecosystem. “If only we do all these complex things, magic will happen”. There’s not much to inspire devs to take the leap. In an LD-based Fediverse not only content would be aggregated into interesting views, based on the semantics and context, but also the dynamic functionalities that act on said context. The current trend in LD is that folks in AI world see the merits, to improve their systems. Which, given how AI is thrown into society and damn the externalities, isn’t something I feel positive about. Would there be merit in depicting innovative UX/UI social networking concepts, that _require_ Linked Data to model them? ---
**Author:** ![wojciechxtx](https://discuss.coding.social/user_avatar/discuss.coding.social/wojciechxtx/32/681_2.png) [@wojciechxtx](https://discuss.coding.social/u/wojciechxtx)\ **Post date:** [January 3, 2024, 10:55am UTC](https://discuss.coding.social/t/radifedi-storybook-of-radically-innovative-federated-ux/323/3 "2024-01-03T10:55:56Z")
> [@aschrijver](#): > > Would there be merit in depicting innovative UX/UI social networking concepts, that _require_ Linked Data to model them? Given that LD is discable, yes there is solid merit in depicting UX/UI changes. ---
**Author:** ![aschrijver](https://discuss.coding.social/user_avatar/discuss.coding.social/aschrijver/32/3_2.png) [@aschrijver](https://discuss.coding.social/u/aschrijver)\ **Post date:** [June 6, 2024, 5:51am UTC](https://discuss.coding.social/t/radifedi-storybook-of-radically-innovative-federated-ux/323/4 "2024-06-06T05:51:19Z")
## “Storytelling UI” In malleable systems chat based on an article of [“User Driven UI”](https://garden.bradwoods.io/notes/design/user-driven-ui) an UX experience was discussed whereby a search box would lead to discovery of other UI features that are available in an app.. I responded with: > Mentioned in the article is how progressive disclosure may lead to overlooking features that exist in the app. I’ve read a number of UX discussions in the past arguing to avoid this pattern and make all possible navigation paths as clear as possible. A hard issue to solve, as you don’t want that ultra-complex cockpit either. > > Based on stuff that Bret Victor did wrt next-gen UI and the [MercuryOS](https://www.mercuryos.com/) conceptual design, I have been musing / dreaming about UI based on an infinite canvas whereby the UI widgets ‘unfold’ like a mind map from core concepts and gain more detail when focused and zoomed in on. The navigation on such canvas would work similar to how Prezi’s [“visual storytelling”](https://prezi.com/the-science/) works, except that it is not just used for presentation but for live and dynamic UI interaction. Furthermore the apps / services / widgets would use social networking and facilitate collaborative editing / interaction. > > In this UI paradigm you could open all kinds of navigation paths that pan out onto the infinite canvas, and still jump back and forth to different contexts. Like MercuryOS the paradigm is not based on a desktop metaphor, or a hierarchical file system. > > I should add that in this new UI paradigm there can be more differences to how we are usually perceive UI. Take for instance a code forge. Here we have a button “Create PR” or something. When we click it and go through the PR process, at the end of that procedure, a list entry has been added to a PR collection called e.g. “Add feature XYZ”. > > In this the UI is totally not process-oriented. It presents some abstraction of the overall state of the software project, from which via deduction we can reconstruct the ongoing work that is taking place. In my Prezi-like UI I might have a process-oriented perspective, presenting how I relate to the project and ongoing tasks. Esp. when zooming out. Zooming in ongoing work then leads to seeing more of the details that are part of current code forges. This UI paradigm explores a space of spacial computing with [infinite canvases](https://infinitecanvas.tools/), i.e. not VR/AR virtual environments but 2-dimensional spaces.. > **[Spatial Computing, Infinite Canvas, and new perspectives](https://chadkohalyk.com/2023/06/28/spatial-computing-infinite-canvas-and-new-perspectives/)** > > Over the past couple of months (years?) I have been overstimulated and generally unable to keep on top of all the information I consume. My zettelkasten practice certainly needs a rethink. I still … In malleable systems chat there was also mention of [Pad++](https://www.cs.umd.edu/hcil/pad++/), an old project that posed the idea of Zoomable User Interfaces, for gradual disclosure of large amounts of data. **See also** : [OCWG: Working Group for Interoperable Infinite Canvas Tools](https://www.canvasprotocol.org/) ### Example: Interactive Flowchart While it is not exactly like the UI paradigm mentioned above, the [“I Want a Better Catastrophe”](https://flowchart.bettercatastrophe.com/) flowchart, created by Potsdam University [Urban Complexity Lab](https://uclab.fh-potsdam.de/) ([@uclab\_potsdam@vis.socia](https://vis.social/@uclab_potsdam)), demonstrates the power of the paradigm (I found this via [this toot](https://mastodon.social/@stephenpa/112567207556344714)). ![Initial UI shows a small flowchart that can be expanded by clicking decisions, and branches out till it is huge](https://discuss.coding.social/uploads/default/original/1X/70ee2406d8a4f22ac3cb75aa55fba0f742d2e162.png) By making decisions in the flowchart progressively more information is disclosed about the “wicked problem” of climate change, and the UI invites to think about the ins and outs. The flowchart project code is at [github](https://github.com/uclab-potsdam/interactive-flowchart) and also has a course: > **[UCLAB • Interactive Flowchart](https://uclab.fh-potsdam.de/projects/interactive-flowchart/)** > > Navigating and Narrating Complexity Through Exploration and Storytelling Here are [more example flowcharts](https://uclab.fh-potsdam.de/interactive-flowchart/projects/) created by students. ### Example: Natto.dev - The future of code `@vadymir` in malleable systems chat [mentioned](https://matrix.to/#/!bQveTkYXFyxLJQwcLG:matrix.org/$W7uoOU5b4w0lPJe9SPL6XluwOKJg36hsDFFUulG0Xrw?via=matrix.org&via=aria-net.org&via=sealight.xyz) the [work by Paul Shen](https://www.bypaulshen.com/projects/natto) on spatial computing based on Javascript:their project Natto.dev. ![Screenshot of the Natto canvas as seen when navigating to it, containing introductory dialogs](https://discuss.coding.social/uploads/default/original/1X/b0f65f61efb3934762d9086ac1f32efcb2a79779.png) Example videos are on [Paul’s Youtube channel](https://yewtu.be/channel/UCQ6wOL_gYaeUg606ZhU4I8Q). Note: Natto is NOT open source, but great to learn from. ---
**Author:** ![aschrijver](https://discuss.coding.social/user_avatar/discuss.coding.social/aschrijver/32/3_2.png) [@aschrijver](https://discuss.coding.social/u/aschrijver)\ **Post date:** [February 16, 2026, 2:13pm UTC](https://discuss.coding.social/t/radifedi-storybook-of-radically-innovative-federated-ux/323/5 "2026-02-16T14:13:23Z")
## [Zircle UI](https://zircleui.github.io/docs/): A frontend library to develop zoomable user interfaces Zircle UI offers a [zooming user interface](https://en.wikipedia.org/wiki/Zooming_user_interface) where changing the zoom level of the viewable area exposes more information. ![Animated gif that shows the concept of the zooming interface. Zooming in on a circular area shows information that is not visible when zoomed out](https://discuss.coding.social/uploads/default/original/2X/9/9a6ada663367eae3bd8328031894dc9d5ff797a7.gif)