This only benefits future mobile layouts with reduced info display. As the whole backend needs to be refactored before we consider restructuring the UI, this would not be good DX. It would inform the user of a QR code misclick, but those are only viable on mobile, scanning from the screen of which requires another mobile device. Low priority.
This only benefits future mobile layouts with reduced info display. As the whole backend needs to be refactored before we consider restructuring the UI, this would not be good DX. It *would* inform the user of a QR code misclick, but those are only viable on mobile, scanning from the screen of which requires another mobile device. Low priority.
We should add name, language, description, WAU, the preview URL and the join URL to the QR code modal.
I imagine something similar to this:
This only benefits future mobile layouts with reduced info display. As the whole backend needs to be refactored before we consider restructuring the UI, this would not be good DX. It would inform the user of a QR code misclick, but those are only viable on mobile, scanning from the screen of which requires another mobile device. Low priority.
@SomeGuy At this point, this is viable - a component can be constructed with placeholders for group details to be filled in on display. New priority?