Stop exaggerating, you hated RCS long before Apple implemented it. It is new for iOS and still being worked on by Apple with their mobile operator partners. It is actually more stable than I imagined it would be and from my experience works about 90% of the time.
You don't have to first send as sms. The way Apple has implemented the RCS registration system is not working properly, yet.
Just like iMessage. Mid conversation it switches back and forth. This conversation was last Wednesday with a friend via iMessage. RCS in contrast has been more stable for me than iMessage.
That is an Apple design issue that they can fix but just like their implementation of RCS they are doing the bare minimum.
Not true, the setting is there but I it doesn't work properly. Sometimes it attempts to send as SMS and sometimes it doesn't just like iMessage. Another Apple implementation issue that they need to fix.
Apple needs to fix that.
It is not. There are lots of things Apple can implement using RCS tapbacks to make them on par with iMessage but it requires them actually being Pro consumer and working with Google but they won't.
RCS was a mess on Android prior to Google taking over the implementation.
Apple can port same features from iMessage to RCS to make them on par because RCS is expandable just like Google has done for RCS on Android. Make the implementation open for Google to adopt but your response is "No". Yet you are complaining that it is sms 1.5.
Features in Google messages
1. E2EE
2. Rich tapback with emojis, animations, full screen and reaction effects
3. Texting 911
4. Voice messages with voice mood tapbacks
5. Custom bubbles
6. Profiles
7. etc
Yes, let's applaud the trillion-dollar corporation for making the customer experience terrible. Because that makes sense to do as a customer.
You literally said you were never going to use it. I truly hope your circle of friends are smarter than that.