Wait mobile apps can intercept and modify screenshots??

Wouldn’t it be cool if your link created minimized version of this as an embed in the post so the most essential info is immediately available? Could even be interactive. (Drawing attention to it since this sort of cross-app discoverability feature seems to be a core part of the 2026 roadmap.)

bsky and tangled share the same auth, so bsky the app could support "rich" embeds: if a user has a tangled repo in their post, the like button could be a tangled star button instead!

atproto has one big idea: apps should be lenses rather than boxes this idea is still unknown to majority of internet users. even to the majority of web developers we’re still at a phase where, if you explain it to someone, you can literally see it clicking for them in real time

What's the intended app/user etiquette for atproto apps with regards to publishing to the same lexicon? Like, say I build an atproto app, would it catch users by surprise if the wrote to the same records (e.g. posts, likes, etc?) that show up in the bsky.app? Or should my app be isolated?

I’ve put atmospheric feedback in @standard-reader.app and it’s been amazing! - @userinput.app for feedback - @atstore.fyi for reviews Read about my approach 👇

A little step: working on an AppView and small Lexicon to make contribution information modular and transparent - so it is easier to signal if you're looking for support, and how to provide it; will have the repo public soon, and hope to get the alpha public later this week - feedback welcome!

This 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.

i wonder how much of this can be prototyped in userland with no new ui eg just a thing that creates “collection” accounts operated by bots. curators can post stuff there by dm’ing the bot. as a reader, you follow the account, so naturally it plays into your Following and For You etc

Today's example of #AtmosphericUX Designer of one app identifies a scenario where it'd be worth capturing data to appear properly in an otherwise unrelated app All that's required is a one-post explainer of the tiny lexicon record to write + they're sharing data directly Zero integration code!