Dear Nick,
I recommend we do not limit the following pages to exclusively Fam parties:
Explore
Profile
Allowing existing parties to be imported into the Fam toolsets is a feature, not a bug. Composability allows us to build music legos. Bring-your-own-party (byop) expands by:
new customers - with an existing need to use their party with Fam tools (Zora create/collect)
simplicity/smolbrain - it takes more time to filter to only Fam parties. Inclusive is the lowest lift.
faster onboarding - skip the create flow. visit your profile, find your Fam, already there.
I understand the desire to limit those pages to exclusively Fam drops. Those other parties aren't a part of Fam. It might be too much info & confusing UX. Filtering our UI to exclusively Parties created in the Fam UI could create a cleaner experience.
I very much appreciate working with Fam professionally. Fam has opened my eyes to Party protocol & the value of multiplayer music onchain. Whichever path we choose, I'm excited to show everyone what we've been building. We have contributed open source tools for any party to collect music on Zora & Sound. Thank you for supporting my practice. - Sweetman.eth
![highlight](/api/highlight?text=Fam%3A%20Curation%20vs%20Composability&author=sweetman&url=%40sweetman&avatarUrl=https%3A%2F%2Fstorage.googleapis.com%2Fpapyrus_images%2F41c7e6e9a9db832b717e0e295bc6bd43.png&featuredImageUrl=&size=512)
![sweetman logo](/_next/image?url=https%3A%2F%2Fstorage.googleapis.com%2Fpapyrus_images%2F41c7e6e9a9db832b717e0e295bc6bd43.png&w=384&q=75)