With a tiny user base, I think you want clients to be able to use as many events as possible.
I am becoming an "opinionated event kind" maxi. Nostr kinds could be designed for specific user experiences instead of general types. Like the picture kind Olas uses. Right now it accepts multiple image sizes but we could have one kind that only takes squared images for those clients to use.
It's similar to nostr:nprofile1qy2hwumn8ghj7erfw36x7tnsw43z7un9d3shjqpqdergggklka99wwrs92yz8wdjs952h2ux2ha2ed598ngwu9w7a6fsr4ma0r 's pitch of kind 1s with a 240 chars limit. We could copy kind 1 into a new kind whose expectation is to render only the first 240 chars of content and ignore all the rest. We could have Nostr clients that only render (and make the best UI for) those events.
Discussion
Not really. We all think that is the case, but the more we develop, the more we realize users don't want that. They just one one little thing.
I feel like every dev would just be remaking the same app in that case.
Which is kind of the case right now, at least with the Twitter clone apps.
Kind1 will be the thing that holds it all together, combined with alt-tags.
The friction to switch between apps is already so low, which is actually one of the 'unique selling points' of Nostr, so we should leverage it