Content pfp
Content
@
1 reply
0 recast
2 reactions

​woj ツ pfp
​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

Kartik pfp
Kartik
@slokh
imo focusing on web is the right move, warpcast is focusing on mobile, lots of opportunities for a good desktop experience
2 replies
0 recast
31 reactions

shazow pfp
shazow
@shazow.eth
+1, there are a lot of scenarios where I simply won't even bother with x or farcaster on my phone. E.g. if it's a nuanced conversation and I need to write a detailed/edited response, I'll just wait until I'm back at my computer. I bet there's a bunch other scenarios too that could be captured well.
0 reply
0 recast
0 reaction