Replying to Avatar PABLOF7z

1. Making things looking/acting alike too much

2. Hiding the possibilities of new UX paradigms (albeit it’s very unlikely that the architecture of nostr has consequences all the way to UI components)

I’m much more persuaded by 1 than 2.

FWIW, there is an ndk components library, it’s just unstyled and very non-exhaustive (yet)
Avatar
Niel Liesmons 2y ago

1. Yup, it's probably even less confusing for newcomers to get the interoperability part when the interoperable apps look and feel completely different.

2. I guess we shouldn't underestimate that neither

Thanks, needed that!

Reply to this note

Please Login to reply.

Discussion

Avatar
PABLOF7z 2y ago

1. True. I’m not a fan of picking on too many battlefronts at the same time, but I philosophically dislike component libraries that make everything look the same, but I think this is downstream of a million different things so attacking this problem right now is not sensible.

To me the balance is in having unstyled components with very basic functionality, but maybe I’m wrong

Avatar
Niel Liesmons 2y ago

"I’m not a fan of picking on too many battlefronts at the same time" 😹

You might not be interested in battlefronts, but battlefronts seem to be enormously interested in you then #infinitePabloApps

Avatar
PABLOF7z 2y ago

Oh shit, I didn’t see that one coming

😂😂😂😂

Here: 👑