Content
@
https://warpcast.com/~/channel/condensed
0 reply
0 recast
0 reaction
antimo 🎩
@antimofm.eth
My book on design is 96 pages long The quickest way to open source it is making a frame, but the pages are 2:1 so we're cutting them into vertical halves - it works, I just want to remake the index pages so they fit in one frame page Currently working with @0xconca.eth on this, will keep you posted
10 replies
0 recast
12 reactions
Steve
@sdv.eth
From this scale it looks like generative art. Very pretty! Though echoing other sentiments; why do a frame and not mini app? Frame would be brutal to navigate through
1 reply
0 recast
1 reaction
antimo 🎩
@antimofm.eth
We're thinking about it Mainly because a frame would let you share a specific page?
1 reply
0 recast
0 reaction
Steve
@sdv.eth
I would think/hope a mini app could do the same, especially as a composer action
1 reply
0 recast
0 reaction
antimo 🎩
@antimofm.eth
But that's the thing, composer actions are a bit hidden What would the flow look like? I'll be honest it's not entirely clear to me whether it could work technically / ux-wise
1 reply
0 recast
0 reaction
Steve
@sdv.eth
Oh right sorry, I guess at the surface it is technically a frame. What I imagine is a frame with an image of the page plus two buttons (Open Book) (Share) The first button prompts the mini app modal to an optimized view of the book as a web app, letting you quickly move through pages with prefetched images. Below the page image there’ll be a share button that composes a new cast that just links the page as a frame. The second button just composes a new cast with the current page. It’s technically a composer action (and iirc that’s currently a requirement for it to surface a mini app) but the initial surface area for most people will indeed be a frame. My pushback on a traditional frame would be navigation + all the time it takes to render each page would make it hard to go through and enjoy.
1 reply
0 recast
0 reaction
