How could an artist focused app on atproto look like? In the first episode of this 'artist app diary' I sketch some general ideas that I have in mind.
Some more ideas about how I think to build an atproto app for artists from the needs I see in my community, and how I envision to grow this into a longer term project. I am curious about your feedback and who is interested to participate.
Artist app diary (2): how to stay sustainable with community building and financial funding
hilkeu.leaflet.pubI finally put some ideas into words about the artist focused app that I would like to build on atproto. I am looking for collaborators, especially artists and UI designers.
Artist app diary (1): the general idea
hilkeu.leaflet.pubsome thoughts on atproto as a post-app paradigm
Ecosystem Plugins
notes.wesleyfinck.orgsome thoughts on atproto as a post-app paradigm
Ecosystem Plugins
notes.wesleyfinck.orgThis is partly why I think atproto needs a more convincing vision about being a post-app protocol. A future where atproto is a bunch of apps and each app governs their own lexicon diminishes a lot of its potential in the long-term.
Laurens
yeah i think i might actually, theres a very interesting story here that the main thing that matters is a focal point around which consensus over a lexicon can get formed
Some initial atproto-related learnings from #Rebuild Helsinki ๐ซ๐ฎ * most people building apps here have no idea what atproto is, which is a shame since especially when building social apps, atproto is a great starting point for many reasons
I've been thinking a lot lately about how lexicon authors could help app developers understand intent. #atproto trezy.codes/blog/what-if-lexicons-knew-hoโฆ
What If Lexicons Knew How to Look? - A Thought Experiment About Display Intents on the Atmosphere
trezy.codes
winter
has anyone thought about the multi repo feed yet or are we still in the era of "this is a <app.bsky.*> viewer" and "this is a <site.standard.*> viewer"
Imagining atproto as a post-app protocol starts with materializing the social filesystem โ decomposing apps and their data into materials and instruments. For the time being, this guestbook is a good example where the display element is a material and the sign element is an instrument.
dan
in any case, the end game is composing these little guys, whatever goes on behind the scenes. social components
individual atproto uis are already remixing data from different apps. so the concept of an "app" blends โ each product is a prism over the shared ecosystem. and if nothing except authorship is firmly gluing different pieces, could an application be glued together from different authors' pieces?
atproto apps
not really exhaustive list, more to store the ones i might have missed
ATmospheric Apps
Things that use ATProto to create their own records (NOT Bluesky clients / Appviews)
Skywatch Statistics
AT Todo - Decentralized Todo App on AT Protocol
About - Monomarks
plyr.fm - music streaming on atproto
Popfeed
Rocksky
import.py
Archivers AT
Brickster โ Build anything, together.
BlueHarbor
Kimbia - A training journal that belongs to you.
Currents
