• Carighan Maconar@lemmy.world
          link
          fedilink
          English
          arrow-up
          27
          ·
          1 year ago

          Then this is irrelevant for them because they wouldn’t be using Google’s Messages application. They’d be using another one.

          • 𝒍𝒆𝒎𝒂𝒏𝒏@lemmy.one
            link
            fedilink
            English
            arrow-up
            7
            ·
            edit-2
            1 year ago

            Google Messages replaced the AOSP SMS app, and is the only app that provides support for E2EE RCS and standard RCS if your carrier has not provided their own.

            It’s also one of the few mainstream mesaaging apps that won’t have a hissy fit about being installed on a rooted device

            Edit: Ah, my point got lost. There is no other app on Android that will let you do RCS mesaaging from a desktop.

          • inasaba@lemmy.ml
            link
            fedilink
            English
            arrow-up
            6
            arrow-down
            4
            ·
            1 year ago

            It’s the only app that has RCS. I don’t use it, but I think it’s kind of terrible that Google has a monopoly on the format.

            • MindlessZ@lemm.ee
              link
              fedilink
              English
              arrow-up
              4
              arrow-down
              4
              ·
              1 year ago

              It’s terrible that no one else has decided to make an rcs app? That’s not really under googles control

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

                Google has blocked anyone’s ability to make an RCS app by making the API a system-level API. In order to make an RCS app, you must make an Android device. So Samsung could make one and bundle it with their phones, but Textra can’t make one and make it available on the Play Store.

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

                  Ah ok, other replies mentioned API access in relation to servers so I misunderstood the issue. It looks like that API is hardlocked to Google (and Samsung?) devices. Thanks for the info

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

                    Samsung was just an example. I have been out of the Android development game for a while now, so my information might be outdated, but back when I worked for an android device maker (Android 5 timeframe), any Android device maker could use the system level APIs. You just needed to sign your app the the same keys your Android source code was compiled with.

              • butter@midwest.social
                link
                fedilink
                English
                arrow-up
                4
                ·
                1 year ago

                They won’t open the api. Anyone else who tries to make one would be starting from scratch. Including with a server

                • MindlessZ@lemm.ee
                  link
                  fedilink
                  English
                  arrow-up
                  2
                  arrow-down
                  2
                  ·
                  1 year ago

                  Sure, but isn’t that just complaining that Google runs the largest implementation of RCS? It would’ve been great if this was handled by carriers, but they never would pick up the task so Google just did it inhouse. I think if they hadn’t rcs would just be dead by now (for better or worse)

              • inasaba@lemmy.ml
                link
                fedilink
                English
                arrow-up
                1
                ·
                1 year ago

                It’s because Google hasn’t allowed anyone else access to the RCS API, actually.

                • MindlessZ@lemm.ee
                  link
                  fedilink
                  English
                  arrow-up
                  2
                  arrow-down
                  2
                  ·
                  edit-2
                  1 year ago

                  Google doesn’t open their own RCS API to the public. Nobody is stopping you from running your own server and service so far as I can tell

      • Cris@lemm.ee
        link
        fedilink
        English
        arrow-up
        6
        arrow-down
        9
        ·
        edit-2
        1 year ago

        If the qr code options stays then its absolutely a positive, but RCS is already a (very frustratingly) closed ecosystem: locking certain features behind an account would just kinda suck, since google messages (or I think maybe Samsung messages also) is the only way to use RCS presently

        • cloaker@kbin.social
          link
          fedilink
          arrow-up
          14
          arrow-down
          1
          ·
          1 year ago

          That’s literally not this. This is for accessing on tablets and computers via the web app.

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

            Yes, I know. I’d like to have access to that feature without having to use my google account

              • Cris@lemm.ee
                link
                fedilink
                English
                arrow-up
                2
                arrow-down
                1
                ·
                1 year ago

                RCS is the only way to get read receipts with most folks I know, and google messages is the only way to use RCS presently

                • cloaker@kbin.social
                  link
                  fedilink
                  arrow-up
                  2
                  arrow-down
                  1
                  ·
                  1 year ago

                  If you have a problem with using a Google account on a Google product, don’t use that Google product. Use signal, WhatsApp or any other messaging service.

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

                    While that is fair, messaging is a bit more complicated since you kinda have to use what other people in your life are using, and almost all of the people I talk to regularly have RCS but not other chat services I’d rather use. If RCS was available outside of google messages I’d gladly use a third party RCS app.

                    Like I said, its great to have an account option if you can still use it without your google account via the QR code, but loosing a feature unless you use a google account would be a bummer.

                    To be totally honest it seems weird to me that people would be so invested in debating my preference to not have to use a google account. I was just expressing my personal disappointment that a feature might go away unless I link an account- do I really need to justify that? Can’t I just be not-thrilled at something without people telling me I shouldn’t feel that way, or that I’m unjustified? 🤷

                    Regardless, I hope you have a good day :)