Send screen streamlining

[owenkemeys]

Upon hitting the Send button, from memory, previously Phoenix would go to a camera view with a paste button.

Since a recent update, it now goes to a Contacts screen, with buttons for Paste / Choose Image / Scan QR.

Personally, my Lightning usage is 60% QR scan and 40% pasted invoices, 0% contacts. Of course this varies by user.

However, I always appreciated the camera coming right up and it would usually scan instantly too, making it really slick touch-free experience.
Usually when I'm paying a QR it's at a store, so it's slightly time sensitive, can be in less than ideal lighting conditions, may have hands full, etc. Whereas the other uses are in more relaxed circumstances. Having to press an extra button to get past a screen for those uses is clunkier.

Option A: bring back the camera view as the default Send screen, with buttons on the bottom for alternate options
Option B: let the user customise what their default screen is when they hit the Send button.

[dpad85]

Option C would be to add a "Scan" button in the home screen which would also fix the issue of having to press Send to scan a withdrawal link (there's a scan button in the Receive screen, but it's awkward and not very visible anyway).

[yashrajd]

I like the idea of a "scan" button on the home screen for lightning wallets, since user might scan for either sending or receiving. It would also address Owen's point about 1-tap scan access.

[owenkemeys]

I like the idea of a "scan" button on the home screen for lightning wallets, since user might scan for either sending or receiving. It would also address Owen's point about 1-tap scan access.

That nicely fits with the user's mental workflow which, upon being confronted with a QR, is likely focused on the immediate task of "I want Phoenix to deal with this QR". Software can figure out if it's a send or receive, he surely doesn't need to tell it.

This also made me notice the inconsistency between the QR button when sending (bottom right) and receiving (top right). Although this is a minor issue, it harms discoverability (I never noticed the Receive one)