@r10s, who wanted to have this discussed here:
Two things to improve for releasing a basic version of the current QR-Code “contact scanning” feature from the current “lab code”:
- Show the own QR-Code during QR scanning.
- Keep the scanner running after a successful scan, to allow further scans (by the other side to let both sides add the OOB contact data, or scan further contacts in a group meetings).
- solves usability issues with current code
- have a basic, classic “two-way” contact setup functionality available (and released) independently from the nextleap developments “one-way scan + cross-channel hidden network messages and potential crypto lib weaknesses”, and from its security review process
- provide a direct comparison (benchmark)
- allows manual, round-robin 1-to-n “bulk scanning rounds” (events in meetings).
The underlying idea is just to display the own QR code within the scannig screen. For testing it may be possible to just place the QR in the title bar of the camera scanner view (if the title bar gets larger with a larger image). And to keep the scanner running after a successful scan.
---------- | <- | | QR | | | |----------| | | | video | | | | | ----------
One would then scan the devices in the same way as now, but should be able to do it in both ways intuitively, without having to decide in which direction, or who scans first, beforehand.
The experimental one-way, cross-channel contact setup method could be integrated by placing an optional button, when enabled:
After a successful QR scan, the screen could show an overlay message:
Scanned: <name and address> Let that contact scan your QR in return. If that's impossible: [Send a contact request message] [Done scanning]
So in case it is not possible to scan in both ways (one after the other), for example when scanning a business card, it could be possible to press the button and send a contact request instead.
(Original issue: https://github.com/deltachat/deltachat-core/issues/247)