Content pfp
Content
@
https://warpcast.com/~/channel/fc-devs
0 reply
0 recast
0 reaction

Manan pfp
Manan
@manan
We've made managing and using @farcaster signers quite simple, but requesting permissions for signers is still a complicated UX to build. We'd seen the hard work @ampsfun, @dashapp, and others had put in to get a system for sign-in + signer approval going within their mini app, and decided to simplify it to the point where it's as simple as a component. It's secure - the signer identifier and API key never touch the client. It'll work across 1. Farcaster - iOS & Android apps + desktop web. 2. Web app - desktop & mobile. Yes, it works outside the mini app context as well. 3. @baseapp.base.eth - iOS and Android apps coming as soon as they build the signer approval flows. cc @aneri.base.eth @dylsteck.eth :) 🪐
4 replies
5 recasts
24 reactions

compusophy pfp
compusophy
@compusophy
these apps need to call sdk.actions.close after the openURL the deeplink, because the farcaster connect signer requestor opens behind the app
1 reply
0 recast
1 reaction

compusophy pfp
compusophy
@compusophy
^ @phil @sayangel for improved ux
1 reply
0 recast
1 reaction

Angel pfp
Angel
@sayangel
On Farcaster this happens? Mobile or PC? I haven't had any reports of this. I've observed openUrl redirecting to the browser outside of FC which then redirects back to FC approval page. Do you have a video? That would be helpful!
1 reply
0 recast
1 reaction

compusophy pfp
compusophy
@compusophy
android. showed a QR code, but the deeplink opened behind the mini app, so had to close the mini app i think this is on farcaster end though, the signed key deeplink doesnt behave like other deeplinks that would minimize the mini app also weird behavior between Android and ios, have found farcaster:// to work best and /~/ routes to sometimes work on one but not the other will send a vid when i can
1 reply
0 recast
0 reaction

Angel pfp
Angel
@sayangel
ah ok I see. is this right? - click create signer (or whatever prompts the signer flow) - redirected to browser via signer link - browser redirects back to FC via deeplink - when you land back on FC the signer approval isn't visible because it's covered by mini app
1 reply
0 recast
1 reaction

compusophy pfp
compusophy
@compusophy
exactly...some recent change it started happening or maybe when the domains switch idk minor inconvenience to ux, ill send some screenshots
1 reply
0 recast
0 reaction

Manan pfp
Manan
@manan
@compusophy we went though the pain to resolve the "connect screen opens behind mini app" in the solution we implemented above. Check out these lines of code, there's another deeplink URL format that doesn't encounter this bug. Hope this helps! https://github.com/neynarxyz/create-farcaster-mini-app/commit/5fa624a0633a87182051d4abde882d140aa60975#diff-e567c4b9fa2adc0bd8a6f7ca44fd3adb54b8ee906883eb72cbeb84cfa1c4f678R194-R209
1 reply
0 recast
1 reaction

compusophy pfp
compusophy
@compusophy
awesome! that's really good to know i turned the signer getter logic into its own mini app auth relay, so if i need a user's signer i just launch this mini app, instead of building it into every project https://farcaster.xyz/compusophy/0x77a49e0e
1 reply
0 recast
0 reaction

Manan pfp
Manan
@manan
Neat! How do I try the flow? Is it implemented in an existing mini app I can try?
1 reply
0 recast
1 reaction