Content
@
0 reply
0 recast
0 reaction
Samuel
@samuellhuber.eth
This is your weekly call to rename Composer Actions to Mini Apps (and just accept that mini apps will be able to edit casts in the composer) Cast Actions & Composer Actions are too similar in naming and users think of the composer as cast. That means no one knows what they are talking about. Simple naming. Mini App for everything that renders iFrames. Cast Action for the thing you press as context menu on a cast Frame for everything adhering to the FC:Frames spec opengraph extension Thanks
6 replies
2 recasts
36 reactions
Dan Romero
@dwr.eth
We will likely do this at some point. Name is not preventing people from building.
2 replies
0 recast
5 reactions
Jacob
@jrf
in my experience, it's difficult to explain to someone *which* of the 2x2 grid buttons they should press to interact with my app i get that the nomenclature is a work in progress, but you could fix it pretty quickly by calling it 'action' button in the feed, and using a different ''app' button in the composer if it's tough to explain ppl how to get to your app that is a blocker to building
1 reply
0 recast
1 reaction
Dan Romero
@dwr.eth
Just call it an app.
1 reply
0 recast
1 reaction
Jacob
@jrf
but it's a 'composer action' which is identical button to the 'cast action' i'm not being deliberately obtuse
1 reply
0 recast
3 reactions
Samuel
@samuellhuber.eth
Yes get that, but to 95% of people it’s both action
1 reply
0 recast
1 reaction
Jacob
@jrf
it really doesn't matter what i call it, it matters how users understand how to get to it calling my composer action "an app that you access from the 2x2 grid button in the cast composer, not the 2x2 grid button ion a cast in the feed" is really ridiculous i understand deep links are coming so this may be moot, but... warpcast should just create a new button in the cast composer and call that the app button
1 reply
0 recast
1 reaction
