Content
@
1 reply
0 recast
2 reactions
woj ツ
@woj.eth
i'm thinking about building on web vs on mobile the same way @dwr.eth thinks about building on warpcast vs on the protocol — iterate on first one but the endgame is on the second one for @super to make sense i need to build a product that some people (not everyone!) love and prefer to use over warpcast — and they love it so much that they will pay for it as many already noticed, this isn't easy and to get there i need to ship fast and iterate a lot and because i'm a full stack web dev, iteration on web comes much easier for me — thus, i'm focusing on the desktop for now but mobile is where the avg farcaster user is so don't worry — once supercast has its 10x features and all protocol infra is there, there will be a great supercast mobile app and it may come faster than i previously assumed thanks to incredible work of @slokh and @emo.eth
20 replies
4 recasts
133 reactions
acai 🚽🐇
@acai
i really think this has a lot to do with what user group you want to curate supercast for, e.g. reddit, twitter, or instagram, etc. ? the former is better fit for long form content, hence desktop makes more sense, while mobile is more ideal for the latter two. warpcast imo is kinda stuck in the middle (especially after the recent case letter count increase) and still trying to find its identity. supercast may have to make a bet on which direction it wants to go towards, and hopefully take over that specific user group. worst case scenario, pivot later. 118✨
1 reply
0 recast
1 reaction
woj ツ
@woj.eth
tbh i just want to build great software — and make a business work around it as a secondary goal 982 $DEGEN
3 replies
0 recast
1 reaction
