Content
@
0 reply
0 recast
0 reaction
Ray F. 🎩
@cryptowenmoon.eth
Dear Warpcast team, This is the Rewards Frame. When I click on someone’s profile, I can follow/unfollow them… but I can’t actually go to their profile? Respectfully requesting: a Go to profile button. Sincerely, The 37 of us who check the frame. cc: @dwr.eth
9 replies
1 recast
21 reactions
MattwithouttheT 🎩
@mathew.eth
Yes, I’ve noticed this too. Let us click on their PFP or name or something to take us to their profile!
2 replies
1 recast
2 reactions
The Dude Bart🐘🌳 ⌐◨-◨
@thedude
yes! I want this too!
1 reply
0 recast
1 reaction
max ↑
@baseddesigner.eth
+1
0 reply
0 recast
1 reaction
Catwifhat🎩
@dainu
Plz!! 🙏🏻
0 reply
0 recast
0 reaction
Kamil Z 🟣
@kamilz
I was just thinking this the other day. Would love to get into their profile from that screen.
0 reply
0 recast
0 reaction
Rocky 🇦🇷🔵🎩🌐
@argentina
Yes, change the “Follow” button, or add next to it another button “View profile”.
0 reply
0 recast
0 reaction
D-wayñe 🎩🕴
@drrrner.eth
Supported
0 reply
0 recast
0 reaction
CRAZY KING 😺 🎩🎨
@kingcrazy
Some one is representing "All of us"
0 reply
0 recast
0 reaction
Goksu Toprak
@gt
We have heard this many times. We are aware this is a sub-optimal UX but we are taking our time on "fixing" this and want to explain why. Most frames are stateful so if we allowed them to navigate to screens we would have to first build a way for users to get back to their last state in the frame when they indicate "back" action. Simply put: you scroll to item 60 in rewards frame, you press to see user profile, frame closes, app navigates. You know press back. What do you expect to see? Most users expect to see frame to open when they last seen it (item 60). This means in practice — we have to either build a way for frames to work "picture in picture" or some stateful pattern or we move the rewards frame out of frame context and make it its own screen so everything works as expected on Warpcast. Short term we are likely to move rewards to its own screen and deprecate the frame implementation.
0 reply
0 recast
4 reactions
