pull down to refresh

I did a bit more designing today!
This is a draft of what it would look like if you wanted to connect your Lightswap to a service that requires API details.
Asking users to enter API details (with instructions provided of course) represents some friction but using great product design, strong video demonstrations, and gamification makes this achievable.
What do you think?
If you're new to Lightswap... We’re building an app that lets you move bitcoin and fiat across your existing wallets, exchanges and bank accounts — using natural language, you just type it out! It makes moving and managing money much easier and much quicker. It already works with major exchanges, so you can buy, sell, send, query, automate DCA, and build workflows without leaving the conversation.
We’re opening a 100-person beta and I’d love to get early feedback from bitcoiners here.
JOIN OUR WAITLIST: www.lightswap.com
Looks good to me but what If the API key comes in a QR code? Can we import a picture?
reply
😮😮 is that a thing? Do you know of any examples so I can take a look?
reply
I don’t but I am often frustrated when data is only shown in QR code and I need to use an other app to get the raw text data
reply
21 sats \ 1 reply \ @Scoresby 5h
I agree that it introduces friction, but in my mind this is the "okay" kind of friction.
The first thing that comes to mind is that I might not know how to find the API details for an exchange I want to use. That little Learn more bit is going to be useful. Especially if it takes me to some docs that show exactly where I can find the API details.
reply
Yep, I'm even thinking of showing a page - before you get to this page - showing and describing how to get your API details, you can dismiss the screen if you know how to get the details or follow the instructions.
I think the friction is OK too but I'm aware that if the user can't get their API details, the app has limited use so I have to nail this.
reply