Some unique :event: Event creation UX coming together
nostr:npub1w5d4ws7d607qwszk4nwm3ugkzkzvvge8mmv0jxfk7edthfnlqhrs8n72uv
https://cdn.satellite.earth/e485d2348a176a47f7ff9131518d7f55b56b106ece7627f3262380b0c673fca6.mov
Discussion
I keep on seeing all your great UI components. What clients are using them?
nostr:npub18stt78efprta2el02tzgnez6ehghzgtt000v58967wvkgezjmprs0n7h7u and soon nostr:npub10r8xl2njyepcw2zwv3a6dyufj4e4ajx86hz6v4ehu4gnpupxxp7stjt2p8 and a buuuunch of micro-apps.
Trying to get all the components to a good enough place (asap) where you can easily build beautiful small one-content type apps with it that can tap into a Community daily driver like Zapchat.
But doing this in between freelance, dad and farm work.
That plus my high UI standards = 🐢 mode.
Are you building a connection so a user could link up their own micro apps within nostr:npub18stt78efprta2el02tzgnez6ehghzgtt000v58967wvkgezjmprs0n7h7u ? Would be great to provide an environment for users to integrate what’s important to them.
Every Community specifies the content-types they (want) to work with in the #communikey event. Whatever they need to work toward their niche / goal.
These can be content types that Zapchat doesn't support AT ALL. Zapchat is there as a daily driver to handle the replies, zaps, reactions, labeling, etc... AROUND those publications. With a relatively large pool of content types that it displays and let's you create within the app.
For example: it makes zero sense fir us to render and let users Collab on 3D models or Figma-like files. But, we can handle the replies on those files, no problem.
And then link out to the Apps the community recommends for opening/creating those 3D models.
TLDR: Yes, and the integration is on the protocol level. Not something custom to Zapchat. Chachi is already building on the sane pattern.
Thank you for the response, learning a lot. What you are building looks and sounds great. Excited to see it come to life!