Meemoo 2022 Q & A

[forresto]

I can make a lobby-track thread about https://meemoo.org/ and my ideas for not needing to manage hosting for the creative tools that it makes.

Meemoo makes creative apps with a boxes-and-wires interface.

I was storing the apps in an anonymous gist, and local storage, but Github shut off that API years ago. And local storage isn't very portable.

Images go to Imgur, which still works, but is meh.

And,
I want Meemoo to become more like a protocol for hackable/composable frontend app communication.

Some examples:
https://meemoo.org/hack-our-apps/
https://meemooapp.tumblr.com/

[automata]

What about a fediverse app?

And brainstorming a bit out-of-topic here:

• Should Meemoo free herself from the medium? Move out from the Web browser to Unity/Unreal-based app so she could leverage 3D rendering?
• If we could make Meemoo an Oracle generative ML model, what it would look like?
• Talking to APIs for current generative model's wrappers (Galactica, Stable Diffusion, ...) by prompts could be an initial MVP?

[forresto]

Fediverse can be social bolted on the side of an app. Webnative SDK is a file system interface on top of IPFS... that might be a better match, to replace Meemoo's localStorage faked file system, and make it so that other "Webnative" apps can interact with Meemoo graphs and artifacts.

• I'm personally still betting on the Web... can't beat the reach.
• Prompting apps into existence? Prompting is an awkward interface for most though. But maybe easier than Meemoo's library and wiring. "Stop motion app with Instagram-like filters."
• Fermat.ws is showing what is possible with talking to AI APIs from a whiteboard.

[forresto]

A big dream that I keep poking at is a project format that can be viewed and edited as

• a wiki with interactive embed blocks (1D: docs)
• zoomable whiteboards (2D: prototyping, moodboards, dataflow)
• embeddable responsive accessible app

[forresto]

Maybe that's just reinventing Smalltalk. 😅 https://pharo.org/features

[forresto]

I think that meemoo-elements design goals feed into that. One API for

• Elements: base-level UI
• Components: reusable UI that can compose elements and other components
• Apps: wire together components and state. Can compose apps, components, and elements

Standard web components / custom elements are missing:

• A way to "expose ports" (typed props and events) so that a dev tool can generate knobs 🎛️
• A way to compose apps (iframe communication?)