• Zak@lemmy.world
    link
    fedilink
    arrow-up
    61
    ·
    2 months ago

    SMS/MMS has really low file size limits, and iPhones may downscale a little more aggressively than required.

    Just pick an internet based messaging service. I like Signal, but they all work.

    • AlternateRoute@lemmy.ca
      link
      fedilink
      English
      arrow-up
      24
      ·
      2 months ago

      The next version of iOS should add support for RCS which should allow for cross platform larger images as well.

        • AlternateRoute@lemmy.ca
          link
          fedilink
          English
          arrow-up
          22
          arrow-down
          1
          ·
          2 months ago

          To be far, apple has had iMessage since 2011 and no one cared about RCS until it was adopted on Android in 2019.

          • 9tr6gyp3@lemmy.world
            link
            fedilink
            arrow-up
            13
            ·
            2 months ago

            To be additionally fair, Android still has phones out there in use that still dont have the RCS feature, and never will because those phones are no longer supported.

              • curbstickle@lemmy.dbzer0.com
                link
                fedilink
                arrow-up
                1
                ·
                2 months ago

                Yes but it wasn’t marketed that way. Which is why there is more interest.

                Apple has been blatantly obvious that they want it to remain proprietary and exclusively on their hardware.

                • Bitrot@lemmy.sdf.org
                  link
                  fedilink
                  English
                  arrow-up
                  2
                  ·
                  2 months ago

                  This is true, Google has cared less about the hardware and more about being the platform to run all of it. Not all that different than Android in that regard.

                  I’m still not sure why people are so quick to jump on board though. You can degoogle Android, it’s much harder to degoogle RCS.

      • Zak@lemmy.world
        link
        fedilink
        arrow-up
        8
        ·
        2 months ago

        RCS from what I can tell still has some significant limitations, like the version common on Android having some Google proprietary extensions it’s not clear if other vendors will fully support. I’d still recommend something like Signal to most people, though RCS improves the experience for those not using that.

    • proudblond@lemmy.world
      link
      fedilink
      English
      arrow-up
      11
      arrow-down
      2
      ·
      2 months ago

      I have an iPhone and whenever my Android-owning friend sends me something, it’s a tiny thumbnail of a photo. So yeah, goes both ways.

      • CrimeDad@lemmy.crimedad.work
        link
        fedilink
        English
        arrow-up
        8
        arrow-down
        1
        ·
        2 months ago

        The trick is to send a link to the photo or video instead of the actual file. This is also how iPhone users can use FaceTime with people on other platforms.

      • halcyoncmdr@lemmy.world
        link
        fedilink
        English
        arrow-up
        5
        ·
        2 months ago

        That wouldn’t be an issue today if Apple had started supporting RCS, the replacement for the old SMS/MMS system years ago like every Android phone. Instead of trying to strangle it by acting like iMessage on iOS was the only solution.

        • Snot Flickerman@lemmy.blahaj.zone
          link
          fedilink
          English
          arrow-up
          5
          arrow-down
          1
          ·
          2 months ago

          RCS has been around since 2008 and got Universal Profile specifications in 2016.

          It took Google until 2019 to get RCS out, and they include proprietary Google extensions that may or may not be supported by other providers, further complicating rollout of RCS.

          They’re genuinely not somehow way better in this regard.

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

            Well I’ve been able to RCS with basically everyone on an android phone since 2019 with almost no issues. That’s 5 years now.

            I don’t really care how Apple wants to try and justify it. The answer is they don’t want to add support for an alternative to their walled garden proprietary system that no one else can use. They want to force everyone onto an iPhone and iMessage if possible. The only reason they’re even looking at RCS support now is because of regulators starting to look at their glaring lack of support for interoperability.

            • Bitrot@lemmy.sdf.org
              link
              fedilink
              English
              arrow-up
              3
              ·
              edit-2
              2 months ago

              That’s because almost everyone on an Android phone is using Google Jibe for RCS, they even turned it on through software for carriers that didn’t support it. It’s not surprising that a Google competitor didn’t jump to implement Jibe.

              Verizon, T-Mobile, AT&T all ditched their own RCS, they also use Google RCS. They’ve positioned themselves central to the entire stack.

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

                And absolutely zero users care about the reasons. They only know that sending messages back and forth is dogshit.

                The source of the lack of support across is Apple not wanting to even try because they want everyone to use their proprietary system on their devices instead. Google at least implemented a system to get RCS support to as many devices as they could, even when carriers didn’t do anything to help. Apple instead had to be threatened by regulators before they even began to consider looking at it.

                • Bitrot@lemmy.sdf.org
                  link
                  fedilink
                  English
                  arrow-up
                  3
                  ·
                  2 months ago

                  “As many devices as they could” with Google at the center of nearly all of it (and if you want all the features, you want the Google one). This isn’t done out of altruism.

  • ninjaturtle@lemmy.today
    link
    fedilink
    English
    arrow-up
    35
    arrow-down
    1
    ·
    2 months ago

    Its due to compression of the video in order to fit on a MMS message, which is very small. Android uses RCS as a new message standard that can send bigger files but Apple has yet to add it to their OS. Its similar to how Apple uses iMessage to do the same, however this is not a standard and is locked to only apple devices.

    Apple is supposedly adding support for RCS during the new iOS update but until then you can use a different messaging app to send better/larger files.

    I recommend Signal as it is easy to sign up and start using while also being private.

  • Snot Flickerman@lemmy.blahaj.zone
    link
    fedilink
    English
    arrow-up
    24
    arrow-down
    1
    ·
    edit-2
    2 months ago

    It’s because Apple has refused to adopt new messaging standards like RCS (not that Google is doing that much of a better job), but it’s purposefully broken interoperability to force people into buying into product ecosystems (iPhone vs. Android) to make you stick with one and get stuck on it.

    It’s stupid anti-competitive and I freakin’ hate it.

    Literally doesn’t have to be this way, it’s a choice (mostly by Apple, but once again doesn’t mean Google is better).


    https://www.theverge.com/2024/6/15/24178470/apple-rcs-support-wwdc-announcement-android-imessage

    Apple was largely forced to support RCS in response to the mounting pressure from global regulators and competing companies. That may help explain the somewhat disgruntled approach to announcing its rollout in iOS 18.


    https://www.tomsguide.com/how-to-switch-on-rcs-messaging-in-ios-18

    Here’s a walkthrough to ensure RCS is enabled on your wife’s iPhone, once iOS 18 drops in the next month or so.

    • Bitrot@lemmy.sdf.org
      link
      fedilink
      English
      arrow-up
      10
      ·
      2 months ago

      A lot of RCS is using Google Jibe, it’s one of the ways they were able to roll it out so fast not necessarily with carrier support. I can’t fault them too much for not immediately embracing it. Based on the Toms Hardware link it looks like they are depending on carrier hubs. For me that means I may not get support for a long time as an MVNO user.

      • Snot Flickerman@lemmy.blahaj.zone
        link
        fedilink
        English
        arrow-up
        10
        ·
        2 months ago

        The Google proprietary extensions in their implementation of RCS is honestly pretty crappy imho as well. Neither of these companies are “good guys” in terms of RCS standards.

          • halcyoncmdr@lemmy.world
            link
            fedilink
            English
            arrow-up
            1
            ·
            2 months ago

            Eh, no one else is doing anything to provide support apart from Google either. Anyone else could do their own thing, no one is prevented from their own support. But very few companies and carriers even began to develop support for RCS, even after the Universal Profile. That is why Google developed their own support and built that support into the native app.

            Verizon had their own RCS support via a proprietary carrier-specific app that never worked with anyone outside Verizon as far as I remember, and they dropped it in favor of Google’s option as soon as that was available. Samsung had their own RCS support in their proprietary Messaging app, also dropped because Google provides the same support on all of their products and Samsung doesn’t have to do anything or support it in any way. Google now provides an option for all Android devices specifically because almost no one was adding support on their own.

            Anyone can, no one else will, because they have no reason to. The average user doesn’t care whether it’s Google, their carrier, or the manufacturer providing support for sending high quality photos to their friend’s phone number as long as it works.

        • bdonvr@thelemmy.club
          link
          fedilink
          arrow-up
          3
          ·
          2 months ago

          That’s why I’m kinda hoping Apple would adopt standard RCS and then the ball’s on Google for not cooperating.

    • Scrubbles@poptalk.scrubbles.tech
      link
      fedilink
      English
      arrow-up
      2
      ·
      2 months ago

      Don’t forget to add in the primary reason they don’t want to implement it is exactly because of comment’s like OPs, because it makes it look like Android phones are the problem. Most people assume that it’s because it’s an android it doesn’t work right, and so everyone should just have iPhones. Why fix what is already great marketing for them, even if it is a complete lie?

  • potentiallynotfelix@lemdro.id
    link
    fedilink
    English
    arrow-up
    14
    ·
    2 months ago

    Apple doesn’t do RCS. This should be changing soon, but for now you should be using another messaging app, because everything you send is unencrypted and shittier quality

  • Obinice@lemmy.world
    link
    fedilink
    arrow-up
    7
    arrow-down
    1
    ·
    2 months ago

    Sending multimedia via traditional text messaging uses the MMS service, which is ideal for very low resolution images, like sub megabyte, I didn’t even know it could support videos! Wild.

    I suggest you add her on something like Discord, or WhatsApp, LINE, whatever works for you, and send each other multimedia that way :-)

    Also depending on your provider you may incur lower costs and faster load times, too.

  • fjordbasa@lemmy.world
    link
    fedilink
    English
    arrow-up
    5
    ·
    2 months ago

    Messaging between iPhones uses iMessage and messaging between android probably uses RCS, both of which do not have the limitations of MMS, which is a limit of around 3.5 MB for most carriers. “Texting” pictures and videos from iPhone to android or vice versa will likely use MMS, hence the blurry media. Until Apple joins the party, the solution is to use another app like WhatsApp, telegram, signal, etc.

    • Bitrot@lemmy.sdf.org
      link
      fedilink
      English
      arrow-up
      3
      ·
      2 months ago

      Not that surprising. Google Jibe is the largest player in RCS. Samsung created their own RCS alternative to Jibe and there are a few others, but Google is hands down the dominant platform. Apple had their own thing already, not exactly jumping to integrate Google Jibe or create another product isn’t surprising.

      • halcyoncmdr@lemmy.world
        link
        fedilink
        English
        arrow-up
        1
        ·
        2 months ago

        Samsung had support before Google and Jibe… but they have abandoned their own RCS support. Simply because Google’s works on all of their devices and they don’t need to do any development to support it going forwards. Why pay for development and support for a system you don’t have to and get nothing from? No one is buying a Samsung phone for the Samsung Messages RCS capability.

  • Vanth@reddthat.com
    link
    fedilink
    English
    arrow-up
    2
    ·
    2 months ago

    What do the videos look like on her phone?

    If they’re shit there, it’s the phone (or the operator). If they look good there and change to shit when they get to your phone, it’s something in that process. Perhaps set to send a low res version by default.

  • Roopappy@lemmy.ml
    link
    fedilink
    English
    arrow-up
    2
    ·
    2 months ago

    The real reason: Apple intentionally doesn’t support the open protocols that send pics and videos to non-Apple devices. These protocols are a decade old and work great. They use a proprietary protocol instead, which they will not share with other phone manufacturers.

    What the average iPhone user thinks: Apple is better than Android!

    It’s pretty dumb.

    • smackjack@lemmy.world
      link
      fedilink
      arrow-up
      0
      ·
      2 months ago

      The thing is, Apple phones do support these things, but only if they change the default messenger app, and most Apple users won’t do that. IPhone users are worse than Windows users when It comes to changing their default apps.

      • Roopappy@lemmy.ml
        link
        fedilink
        English
        arrow-up
        2
        ·
        2 months ago

        Unless I did a really poor job researching it, you cannot change your default SMS/MMS application on an iPhone.

        You can use other messaging apps like Signal, Whatsapp, Telegram, or AIM. But if you want to use SMS, you have to use iMessage.

        Maybe this is US-specific though. Europe often forces Apple to do things they don’t do here.

      • PM_Your_Nudes_Please@lemmy.world
        link
        fedilink
        arrow-up
        1
        ·
        2 months ago

        If you mean changing which app natively gets used for texting, that’s not something you can do on iOS. You can choose to open a different app, but if I tell Siri to text someone it will always 100% without a doubt no way to circumvent it use the standard Messages app. iOS doesn’t let you change your default for texts.

        Hell, they only allow you to change your default web browser because they were dragged into court kicking and screaming. And even then, all third-party browsers are forced to use Safari’s engine for the backend, and aren’t allowed to use their own engines. Even Chrome, Firefox, and Brave are just reskins of Safari on iOS. And even then, any apps that open an in-app browser will still use Safari even when your default browser is different. For instance, I’m browsing lemmy on Voyager, and it opens all links in a built in Safari browser, (even though my default browser is set to Firefox.)

  • Coolkidbozzy [he/him]@hexbear.net
    link
    fedilink
    English
    arrow-up
    2
    ·
    edit-2
    2 months ago

    they use proprietary file formats (MOV and HEIC) that need to be converted to a universal format like jpg or MP4 to be viewed on android (I think this can be changed in iPhone settings), and the conversion looks like shit

    • 2xsaiko@discuss.tchncs.de
      link
      fedilink
      arrow-up
      1
      ·
      2 months ago

      It’s very funny you say MOV and HEIC are proprietary and then list MP4 considering

      • HEIC is just H.265, the video codec, used to encode images
      • H.264, the codec used for most mp4 files has the same license as H.265 with patent bullshit license fees going on
      • MP4 container is pretty similar to MOV, and is also not an open standard
      • this also means MOV and MP4 can be losslessly converted
      • Apple provides documentation for MOV format free of charge while ISO really wants you to pay to get official standard PDF
      • All this doesn’t matter anyway because ffmpeg can decode everything (though I guess it might matter in bizarro land where software patents are a thing)

      Also Android can totally read at least HEIC images. Not sure about MOV. Any of this is also not related to the problem the OP has.

    • bdonvr@thelemmy.club
      link
      fedilink
      arrow-up
      1
      ·
      edit-2
      2 months ago

      HEIC is not proprietary to Apple at all, they were just one of the early adopters of it.

      My Android phone takes pictures in HEIC/HEIF by default, and it’s not nearly as much of a problem anymore almost all software can handle the format now.