# "Add as Second Device" desktop UI/UX **URL:** \ **Category:** Feature Proposal\ **Tags:** android, desktop\ **Created:** [September 22, 2025, 6:22pm UTC](https://forum.delta.chat/t/add-as-second-device-desktop-ui-ux/4138 "2025-09-22T18:22:18Z")\ **Posts on this page:** 1\ **Showing post:** 4
**Author:** ![bencan](https://forum.delta.chat/letter_avatar_proxy/v4/letter/b/eb9ed0/32.png) [@bencan](https://forum.delta.chat/u/bencan)\ **Post date:** [September 23, 2025, 10:47pm UTC](https://forum.delta.chat/t/add-as-second-device-desktop-ui-ux/4138/4 "2025-09-23T22:47:53Z")
> [@lnkr](#): > > I did not consider it safe to pass the authorization string from my phone to my computer via other channels If you lack an existing secure channel or access to a cable as suggested by Raiden, you can create a secure channel by creating a temporary chatmail account on your desktop, scanning the contact QR code with your mobile, and passing the authorization string this way to your new temporary account. You can delete your temporary account later if you no longer need it. However this is maybe not an obvious workaround. Someone else already suggested inverting the flow for adding a second device, or allowing it in both directions, as for contacts: > [@Reverse the "Add 2nd Device" flow](https://support.delta.chat/t/reverse-the-add-2nd-device-flow/3965): > > I believe that the QR-Code scanning flow for adding a secondary device should be inverted. By that I mean, the target device intended to receive the profile should show a QR code, not the device that the profile originates from. Rationale for this is simple: Many desktop computers have no camera. Many tape over their laptop cameras, turn them off, or use shutters. I suspect more of the “origin” devices are gonna be phones, as opposed to laptops or desktops. Those devices also tend to have ca… --- _[View the full topic](https://forum.delta.chat/t/add-as-second-device-desktop-ui-ux/4138)._