Content pfp
Content
@
0 reply
20 recasts
20 reactions

phil pfp
phil
@phil
Some chatter on this, especially around the “eat their lunch” phrasing My perspective as a user: Warpcast has a difficult role to play: as the largest product on the Farcaster protocol, their actions will drive the majority of new user growth Along the way, there will be other apps that emerge to fill gaps in the Warpcast value prop. Scheduled casts, onchain actions, real time chat, etc As those features are validated by users, the Warpcast team is then faced with a choice: integrate these features into the main app (thereby stimulating growth), or intentionally avoid building it to reduce competition with ecosystem partners The rub: if Farcaster doesn’t significantly grow, then all ecosystem apps will likely die anyway due to lack of sufficient users. My personal framework around this topic is less vibes driven and more realpolitik; as an app builder, you have to be prepared for your great feature idea to be copied as soon as it’s proven to be successful with users.
7 replies
27 recasts
212 reactions

Yassine Landa pfp
Yassine Landa
@yassinelanda.eth
Hey @phil please consider this: what if Warpcast was not the largest app in the ecosystem anymore. Imagine Zuck comes in and build a client or integrate FC into Threads, and starts eating everyone's lunch… client diversity is something to strive for if you believe in decentralized social, otherwise all the app builders will just leave and we're back to square 0. I am not saying it is not competitive but just pointing that the wording stuck a nerve exactly because it is quite discussed between builders already (not less).
1 reply
0 recast
0 reaction

phil pfp
phil
@phil
i think if facebook integrated the farcaster social graph that would be the best possible outcome for the protocol, no? fwiw, i'm not advocating for the team to actively try to copy ideas, nor do i think they have a record of doing that. i'm simply pointing out that if something fits within the warpcast value prop, and another app in the ecosystem proves that it has traction with users, then it's fair game to integrate it into wc, especially if it's something that has discussed many times before but not prioritized (e.g. integrating onchain data into the feed) the whole reasoning behind "good opportunity for another client" is that there are plenty of ideas warpcast can't or won't go after because it's not a fit for the wordcell style twitter app. but if you're building an app that directly competes with warpcast you should probably expect competition eventually
0 reply
0 recast
1 reaction