Samo on Warpcast

Content pfp

1 reply

0 recast

2 reactions

woj pfp

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 @supercast 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

54 reactions

Samo pfp

That issue is simple: web for now, you'll see later. But here's my thinking on the potential, no matter the choice: HUGE RISKS - the strategy for FC + Warp is unclear; 2 years ago you had FC + clients (including Warpcast), now the official FC website is a Warp billboard - history (Twitter) showed us that strategy can change as a company grows, so they can cut access to API (huge risk!) - I asked DWR even 1+ years ago, if he doesn't feel that an all-dev-team is a risk for the project due to a lack of perspective; maybe then it wasn't, but looking at some of their recent decisions (priority mode, remove basic features, etc) I think it will have an increasing negative impact HUGE OPPORTUNITIES - the Warpcast app is lacking many core features already confirmed on other platforms (long form content, media - video + pics, gifs, now animated pfps, nft pfps, scheduling, drafts, etc) ⬇️

2 replies

0 recast

2 reactions

woj pfp

saving this for later 🫡 982 $DEGEN

2 replies

0 recast

1 reaction

Samo pfp

0 reply

0 recast

0 reaction