The Android enthusiast community is stoked about RCS messaging. Being excited about a new messaging protocol is the exact kind of thing Android nerds would get excited about, and the fact that it's generally being positioned as a new unified messaging platform to be "iMessage for Android" has elevated its appeal.

But sadly, RCS continues to have a rocky rollout. Carriers are dragging their feet in supporting it, as are phone makers — and while the latter can be addressed with a third-party messaging app, there's little you can do about the former. Cross-carrier (to say nothing of cross-country) RCS support is a mixed bag, and in some cases they're forming messaging alliances on the side to muddy the waters further.

RCS isn't ready for prime time yet, and you don't have to use it until it is.

With all of the tumult surrounding the rollout of RCS, I just don't understand why so many people are so enthusiastic about using it right now. At this point, you have to work to get RCS. There's a "hack" (of sorts) to enable it on any phone, but that's not guaranteed to stick around forever — or even long enough for carriers and phone makers to actually support it properly. Outside of that you need to be using a specific app and only certain carriers — and that goes for everyone you talk to. Having to think about apps and carriers and protocols is exactly the problem RCS is aiming to solve — yet you have to deal with it all to use RCS right now.

It's not my duty as a messaging app user to be the one to die on the RCS hill. There is zero reason for me to keep trying to rely on RCS as it's rolling out and clearly in an unfinished state. A messaging app means nothing if the people you talk to most often aren't on it — or willing to switch to a new platform that supports it. And with all of the caveats involved with RCS right now, you aren't going to be finding all of your friends and family jumping through hoops to start chatting with you using RCS.