• Dandroid@dandroid.app
    link
    fedilink
    English
    arrow-up
    61
    arrow-down
    1
    ·
    1 year ago

    Maybe Google can work with Google on implementing a user-level API for Android so manufacturers don’t have a monopoly on RCS apps.

    • AaronNBrock@lemmy.world
      link
      fedilink
      English
      arrow-up
      24
      arrow-down
      1
      ·
      1 year ago

      Maybe Google can work with Google on implementing RCS on Google’s own product Google Voice.

      • averagedrunk
        link
        fedilink
        English
        arrow-up
        10
        ·
        1 year ago

        They all but abandoned that years ago. They ain’t implementing shit on it.

    • EddieTee77@lemdro.id
      link
      fedilink
      English
      arrow-up
      9
      ·
      1 year ago

      And hopefully everything becomes a standard so people on both operating systems can leverage these features together

      • skuzz@discuss.tchncs.de
        link
        fedilink
        English
        arrow-up
        7
        ·
        1 year ago

        They won’t. It’s part of their “slowly-closed-source-all-of-Android” plan. The old messaging app used to be part of AOSP and you could read the source, how delightful that was.

        Would be a good time for a contender to start the third OS. In a few years, more of the population would have interest enough that it might actually get traction.

        • TheMadnessKing@lemdro.id
          link
          fedilink
          English
          arrow-up
          4
          ·
          1 year ago

          They have abandoned the app and multitudes of others in favour to their closed source apps. Multiple Open Source apps exists to fill the gaps though.

      • Sendbeer@lemm.ee
        link
        fedilink
        English
        arrow-up
        6
        ·
        1 year ago

        Fucking A. I hate using Googles shitty messaging app, and maybe I would have more than 2 other rcs users in my contacts if the 3rd parties could implement it.

  • aiman@lemdro.id
    link
    fedilink
    English
    arrow-up
    11
    arrow-down
    1
    ·
    1 year ago

    Any bets on which implements RCS first, iOS or Google Voice?

  • katy ✨@lemmy.blahaj.zone
    link
    fedilink
    English
    arrow-up
    8
    ·
    1 year ago

    let us have rcs with google messages when we link our google fi account or let us get our visual voicemails in the google dialler already :(

    the only reason i link my account and turn off rcs is for visual voicemails on the web since the stock voicemail app is rubbish

    • charliegrahamm@lemm.ee
      link
      fedilink
      English
      arrow-up
      1
      ·
      1 year ago

      I had visual voicemail on my previous 2 pixels (O2 in the UK), but not on my galaxy s23 ultra on the same network. Seems to be a pixel/iphone exclusive feature.

    • ForgotAboutDre@lemmy.world
      link
      fedilink
      English
      arrow-up
      4
      arrow-down
      1
      ·
      1 year ago

      Google’s paying for it and Apple’s going to be using jibe.

      It the same shit as Google being the default search on safari and iPhone.

      Data scraping and advertising dollars.

      Google currently has very limited insight about iPhone users messaging habits. iPhone users are using apple’s iMessage, SMS, WhatsApp, Facebook messenger, telegram, signal, discord, slack etc. Most of which have limited Google interactions. On Android Google at least gets some info from third party messaging services. Like use time, installation, stored data size etc. On iPhone they can only scrap through search and Gmail.

      Google has been trying to crack the messaging space for a while. They keep dropping messaging apps because they haven’t been able to get the mass adoption. They’ve found their solution with RCS.

      Take a open protocol that no carriers will seriously implement. Adapt it to your needs and restrict acces to it (no third party apps only Google and limited second party like Samsung). Create the implementation (jibe) give it to the carriers. When carriers don’t do it, make a fallback to jibe in the messenger app. Unlike apple, Google messaging service is hard to notice - therefore easier to slip by. RCS messages have small text only at the start and a slightly different shade of blue.

      Once it’s established on Android. Publicly shame apple for not using your open standard, where most messages run through your server. Privately pay them for adoption and ensure it meshes with your version of the open standard. Taking away one of the last reasons the messenger app on android has to avoid Google by default.

    • rikonium@discuss.tchncs.de
      link
      fedilink
      English
      arrow-up
      4
      arrow-down
      1
      ·
      1 year ago

      It was the next, more feature-rich SMS/MMS. It floundered with carriers, Google flip-flopped several times on messaging and today, it has two forms. Google’s RCS, but I’d liken it more to Google iMessage. And RCS the standard, which Google’s implementation is based on and Apple will be adopting. I am hoping that this is a kick in the butt that everyone needs to actually get on the same page for an SMS successor.

    • vxx@lemmy.world
      link
      fedilink
      English
      arrow-up
      2
      ·
      edit-2
      1 year ago

      Rich Communication Service.

      It’s SMS or MMS but better.

      You don’t need a messenger app and share your contacts with Facebook and Co.

      • ForgotAboutDre@lemmy.world
        link
        fedilink
        English
        arrow-up
        2
        arrow-down
        2
        ·
        1 year ago

        You do need a messenger app. Google wants you believe you don’t but you do.

        It’s baked into Google messages and Samsung messages (Samsung messages is just rebranded Google messages). It pre installed and defaulted if the person you tried to text can receive it.

        Google RCS goes through the internet, not carrier networks. Most likely Google jibe service. Which you carrier may have Google implement for them, if not it will default to Google’s own jibe service.

      • superweeniehutjrs@lemmy.world
        link
        fedilink
        English
        arrow-up
        12
        arrow-down
        11
        ·
        1 year ago

        If a practically brand new flagship like the Pixel 6 has more bugs than an ancient iPhone XR, I don’t think base Android can survive much longer. Basic functionality like YouTube PiP and theming glitch out regularly. Not to mention extended features like bubbles in Messages being broken since day one. Sure, I can sideload on Android, but if that comes to iPhone…

        I can’t seem to make $200 per year for a device work out with Android anymore. The pixel 6 should last 3 years in my opinion, but support for the 6 has been limited since the pixel 7 came out. Even at $900, I think the iPhone could prove to be a better deal with 6 years of support backed by a history of keeping such promises. USB-C, RCS, Sideloading are all I’ve been waiting for.

        • 13617@lemmy.world
          link
          fedilink
          English
          arrow-up
          2
          ·
          1 year ago

          I’ve had a ton of bugs on iPhone. But I completely agree with you. especially for the average consumer, iPhone will be just the easy choice.

          Also Pixel 6 is just god awful with bugs. At this point I don’t think Google can fix all of them, so many just feel related to the chip. I’d assume it’s better on their newer phones but you shouldn’t have to buy a newer phone to get a bug fixed.

          I have been diehard android but this is really testing me. I want to use the best phone, and Apple had already been making the hardware. (Though, snapdragon 8 gen 2 has really redeemed itself, absolutely incredible, efficient and great chip. One of the reasons I just can’t see myself using a Pixel again)