Table of Contents
Somewhere in my fire-damaged house is a dog-eared, scribbled, underlined, autographed copy of Friedhelm Hillebrand’s 2010 book, full of optimism about the then-nascent MMS format. This week’s Builder’s Log got me wishing for the book.
Quick Win:
RCS supports up to 100 MB of rich media. I tested it with the WHF Timeline video I posted last week—no 3 MB MMS limit, no messy transcoding. It just works. Try it yourself—scan the QR code.
Lesson Learned:
It’s still clunky. On iOS, you have to download the video before watching. That makes sense since RCS uses the customer’s data channel and gives them the choice. On my Pixel 9, though, the video downloaded automatically. Shows how operating systems can have different experiences on the same channel.
We, as an industry, never got MMS right. Canada, for example, didn’t fully support A2P MMS until last year. Maybe with RCS, we can stop trying to make MMS work and, over twenty years later, finally move on.
What’s Next:
I wade into the iOS v. Android debate. Follow me on LinkedIn to see what I find.
RCS Builder’s Log is my running series of notes, takeaways, and experiments from building and deploying RCS in the wild. Read other entries here.