Back to the episode map

Research Note

Messaging Protocol Comparison Record

The iPhone Messages interface can send through iMessage, RCS, SMS, or MMS. The interface, contact, thread history, and bubble color do not fully identify which service ca

Aug 4, 20262 min readBy Dalton Anderson

Messaging Protocol Comparison Record

The iPhone Messages interface can send through iMessage, RCS, SMS, or MMS. The interface, contact, thread history, and bubble color do not fully identify which service carried a particular message.

Apple describes iMessage as its data-based messaging service between supported Apple devices. It supports richer media and interaction features and is end-to-end encrypted.

Apple describes RCS as a carrier-provided service that can operate over Wi-Fi or cellular data when iMessage is not in use. Current features include richer media, receipts, and typing indicators. End-to-end encryption is a current beta capability in supported configurations, not a universal property of all RCS.

SMS and MMS are carrier-provided legacy messaging services. SMS typically carries text. MMS extends carrier messaging to media and group content. Apple states that SMS and MMS are not end-to-end encrypted.

Comparison boundary

DimensioniMessageRCSSMS or MMS
Primary providerAppleCarrier and implementation partnersCarrier
Common transportWi-Fi or cellular dataWi-Fi or cellular dataCarrier messaging service
iPhone colorBlueGreenGreen
Rich mediaSupportedSupported in current implementationsMore limited and carrier-dependent
Receipts and typingSupportedSupported in current implementationsNot a general SMS or MMS property
End-to-end encryptionApple states yesConfiguration and conversation-dependent beta on current iPhoneApple states no
Fallback riskCan fall back when enabled and unavailableCan fall back when unavailableFinal fallback layer

Reader evidence

The reader should inspect the composer label, current thread state, participant set, device version, carrier support, and visible encryption indicator. Bubble color is useful interface evidence, but it is not a protocol analyzer.

The maintained comparison should avoid implying that standards eliminate platform, carrier, client, identity, spam, metadata, backup, or fallback differences. It should also avoid universal cost claims because plans and data charges vary.

Sources

Follow the evidence.

  1. support.google.com: 15283615support.google.com
  2. daltonanderson.ghost.io: apple rcs pixel 9 pro ai missing pixel buds reviewdaltonanderson.ghost.io
  3. gsma.com: gsma rcs universal profile 3 0 specificationsgsma.com
  4. daltonanderson.net: apple rcs pixel 9 pro ai missing pixel buds reviewdaltonanderson.net
  5. Gemini Apps Privacy Hubsupport.google.com
  6. gsma.com: rcc 16 rich communication suite end to end encryption specificationgsma.com
  7. support.google.com: 7158570support.google.com
  8. support.google.com: 9642886support.google.com
  9. NIST AI Resource Centerairc.nist.gov
  10. support.apple.com: 109526support.apple.com
  11. c2pa.org: Explainerc2pa.org
  12. open.spotify.com: 0oFCWqUfkKDPZ3TVaxmWFJopen.spotify.com
  13. support.google.com: 15312581support.google.com
  14. support.apple.com: iossupport.apple.com
  15. support.google.com: 15436763support.google.com
  16. support.google.com: 7685360support.google.com
  17. youtu.be: mHgvtRIwfi8youtu.be
  18. support.apple.com: 104972support.apple.com
  19. support.apple.com: 122195support.apple.com
Messaging Protocol Comparison Record