Both actually. But in specifics, I meant this:
Let’s assume someone built a health-tracker on top of Solid - the kind of service where being assured that the data is stored on a personal pod instead of some unknown internet part is actually a big selling point.
I’m using that app and also use the same pod to store my jogging activity logs that I regularly share with my friends on social media for bragging rights (“look, I made this run under 50 minutes today!”).
When I next open the social media app and say “share something from my pod”, I need to understand which parts I’m gonna share, and with whom. If all apps use a different data browser with a different design language, I have to re-learn this part for every app, to be sure that I’m not accidentally sharing the wrong thing.
For comparison: Right now, sharing things or giving access to stuff on my computer means that I’m uploading it to each new platform. And the uploading function always gives me my local computers file dialog, so I can be pretty sure of what I’m sharing.
Is this necessary for the technical part of Solid to work? No, not at all. Would it help increase adoption if there is such a common visual language? Absolutely.