4 ms·
Many carriers already have. The main issue is that Google is steamrolling their own IaaS solution (Jibe) while some carriers (like Swisscom for instance) have a
by hocuspocus 5y ago
Many carriers already have. The main issue is that Google is steamrolling their own IaaS solution (Jibe) while some carriers (like Swisscom for instance) have actually implemented Universal Profile on their own, and are now left out.
- tssva 5y agoHow are they left out? If they have implemented Universal Profile they should be able to interoperate with those using Jibe's.
- hocuspocus 5y agoGoogle seems not interested in interconnected third party RCS hubs anymore. The current situation means that people who are directly connected to Google's own Jibe infrastructure can message carrier-operated Jibe deployments. But they can't message third party RCS networks or vice-versa.
- cmurf 5y agoWhat a hilarious way to kill RCS growth beyond where it is. Why?
- hocuspocus 5y agoThe people I asked didn't know. Pure speculation: Google got frustrated with carriers moving too slowly even after acquiring Jibe. I understand carriers not being compelled by Google's lack of vision for mobile messaging then. Especially given that Apple won't give a damn. A few years pass and Google decides to pivot their messaging services once again, and that now is the time to push RCS for real. Google managed to convince big carriers on several continents that Jibe is the solution. And they probably think the small ones will eventually cave in.
- toast0 5y ago> Why? This is only speculation, but it's Google. You don't get promoted for making an existing messenger work, or work better. Better to abandon it and join a team making a new messenger.