Message pressure from Google to Apple!

RCS crisis broke out between Google and Apple. Google wants Android and iPhone to use RCS service due to messaging issues.
 Message pressure from Google to Apple!
READING NOW Message pressure from Google to Apple!

Recently, there have been communication problems between iPhone and Android users for SMS services. Google has launched a campaign against Apple on this issue. The technology giant has also signed with many organizations and social media phenomena for the campaign.

Google calls for RCS for iMessage

Google has started to offer some features in the iMessage service in RCS standards with the Android Messages application. However, sending messages between iPhone and Android devices caused problems for Google. After that, Google began to pressure Apple to use this service.

With the #GetTheMessage campaign, Google reached agreements with many companies such as “ATTN” to put pressure on Apple. Announced in 2008, the RCS service offered users the opportunity to use the features used in the iMessage application such as end-to-end encrypted messaging, sending larger file attachments and reacting to messages.

Why doesn’t Apple use RCS?

BlackBerry, which was preferred by many users in the 2000s, was popular because of its own messaging application. Apple’s iMessage service, on the other hand, was one of the most important factors in favoring BlackBerry devices in the 2000s.

At the same time, the RCS service is not considered safe by Apple because it uses data centers of telecommunications companies. In addition, Google offers its application developed to provide better security in the RCS service to Android phones as a built-in messaging application.

In addition, the RCS standards introduced in 2008 were made available by Google in 2016. However, many companies around the world, with the exception of companies located in the USA, quickly adapted to this situation. In the USA, T-Mobile started to support it in May 2020 and AT&T in June 2021.

Comments
Leave a Comment

Details
206 read
okunma23267
0 comments