Skip to content

[ALIGNMENT]: Share a contact or channel set #153

Open

Description

@jamesarich

Share a contact or channel set

Decision

Every client shares a contact or a channel set from one surface that offers the QR code, a link handed to another app, and an NFC tag write where the hardware allows it. That surface names what is being shared, explains each affordance in plain language, and never offers a control the device cannot honor.

Context

NFC alignment across the clients is largely done. Meshtastic-Apple #2136 gave iOS channel writes, an in-app reader and share-sheet placement, and Meshtastic-Android has had all of that since #6030. The audit at standards/audits/nfc-alignment-audit.md records the current state; refreshed in #152.

Closing that work exposed a different gap. The share surfaces themselves diverged while attention was on the NFC plumbing underneath them, and the divergence is in what the surface tells the operator rather than in what it can do.

The payload is not in question. Both share types are the same base64url URLs behind meshtastic.org/v/# and meshtastic.org/e/# that QR codes and deep links already carry, so this is a UX alignment, not a protocol one.

Where the clients stand today:

iOS offers ShareLink on both surfaces, sending the QR image and the URL to any app. Android offers copy to clipboard and nothing else. QR and NFC both need the other person in the room; the link is how you reach someone who is not, and on Android that is a clipboard paste the operator has to route themselves.

iOS names the node being shared and explains what the QR is for. Android shows the raw URL and explains only NFC.

Both clients let an operator choose whether a shared channel set adds to or replaces the recipient's channels. iOS puts that choice in the share screen with a sentence describing the consequence. Android puts it on the channel list as two segmented buttons labeled Replace and Add, with no consequence text and away from the share action, so it can be changed without the operator seeing what changed or seeing the setting at all while looking at the QR.

Neither client checks for NFC hardware at runtime. Android supplies its NFC capability flag as a constant true, so the affordance appears on a phone with no NFC radio and fails when used. iOS gates on the OS version only.

Both clients still name the channel share surface after the QR code: Generate QR Code on iOS, Share Channels QR Code on Android. Meshtastic-Apple #2464 already made this correction for contacts and left channels.

Android additionally ships this surface to Compose Desktop, where standards section 4 asks for a hover tooltip on an icon-only button and there is none.

Tag emulation, where the phone itself answers as the tag, is in review for Android in meshtastic/Meshtastic-Android#7124. iOS has no third-party tag emulation, so this one stays asymmetric and is not part of the decision above.

Required Client Behavior

  1. Offer a link share from the same surface as the QR code, handing the URL to the platform's share mechanism so the operator can send it through any app. Include the QR image where the platform supports sending one.

  2. Name what is being shared on the surface itself: the node's long name for a contact, the channel set for channels.

  3. Explain the QR code in plain language, not only the NFC affordance. Section 6.

  4. Present the channel add-versus-replace choice on the share surface, next to the share actions, with a sentence stating what the recipient's radio will do in each case.

  5. Show an NFC affordance only where the device has the hardware, checked at runtime rather than assumed from the platform or the OS version. Section 3.

  6. Name the channel share surface for what it does rather than for the QR code, matching the contact surface.

  7. Where the surface reaches desktop or web, give every icon-only control a hover tooltip. Section 4.

Acceptance Criteria

A contact and a channel set can each be shared to another application as a link, from the same surface that shows the QR code, on iOS, Android and Compose Desktop.

The share surface states which node or channel set it is sharing, and a first-time operator can tell from the surface alone what the QR code is for.

Changing add-versus-replace is possible without leaving the share surface, and the consequence is stated on screen.

On a device with no NFC radio, no NFC control is present on any share surface.

No share surface is named after the QR code.

Platform Tracking

References

Activity

  1. jamesarich commented on Sep 10, 2026

    @jamesarich
    CollaboratorAuthor

    One more divergence, found while checking the Android surface against Material 3.

    iOS presents both share surfaces as sheets. ShareContactQRDialog is shown with .sheet and a drag indicator, and ShareChannels is a navigation destination. Android presents the same content as an AlertDialog.

    That matters more now than it did when each surface held a QR code and one button. Both now carry three actions and three lines of explanation. Material 3 describes modal bottom sheets as an alternative to menus or dialogs, particularly for long lists of actions or items requiring detailed descriptions, which is what these surfaces have become. The Android dialog is not breaking a rule as it stands, since Material 3 caps the trailing action row at two buttons and it has one, but the content has outgrown the container.

    Suggested addition to Required Client Behavior: present the share surface as a sheet rather than a dialog, so it can hold the actions and their explanations without crowding. iOS already does. The Android work in flight keeps the dialog and improves what is in it, which is the smaller step; the conversion is worth doing separately.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions