view the rest of the comments
Android
The new home of /r/Android on Lemmy and the Fediverse!
Android news, reviews, tips, and discussions about rooting, tutorials, and apps.
🔗Universal Link: !android@lemdro.id
💡Content Philosophy:
Content which benefits the community (news, rumours, and discussions) is generally allowed and is valued over content which benefits only the individual (technical questions, help buying/selling, rants, self-promotion, etc.) which will be removed if it's in violation of the rules.
Support, technical, or app related questions belong in: !askandroid@lemdro.id
For fresh communities, lemmy apps, and instance updates: !lemdroid@lemdro.id
📰Our communities below
Rules
-
Stay on topic: All posts should be related to the Android OS or ecosystem.
-
No support questions, recommendation requests, rants, or bug reports: Posts must benefit the community rather than the individual. Please post to !askandroid@lemdro.id.
-
Describe images/videos, no memes: Please include a text description when sharing images or videos. Post memes to !androidmemes@lemdro.id.
-
No self-promotion spam: Active community members can post their apps if they answer any questions in the comments. Please do not post links to your own website, YouTube, blog content, or communities.
-
No reposts or rehosted content: Share only the original source of an article, unless it's not available in English or requires logging in (like Twitter). Avoid reposting the same topic from other sources.
-
No editorializing titles: You can add the author or website's name if helpful, but keep article titles unchanged.
-
No piracy or unverified APKs: Do not share links or direct people to pirated content or unverified APKs, which may contain malicious code.
-
No unauthorized polls, bots, or giveaways: Do not create polls, use bots, or organize giveaways without first contacting mods for approval.
-
No offensive or low-effort content: Don't post offensive or unhelpful content. Keep it civil and friendly!
-
No affiliate links: Posting affiliate links is not allowed.
Quick Links
Our Communities
- !askandroid@lemdro.id
- !androidmemes@lemdro.id
- !techkit@lemdro.id
- !google@lemdro.id
- !nothing@lemdro.id
- !googlepixel@lemdro.id
- !xiaomi@lemdro.id
- !sony@lemdro.id
- !samsung@lemdro.id
- !galaxywatch@lemdro.id
- !oneplus@lemdro.id
- !motorola@lemdro.id
- !meta@lemdro.id
- !apple@lemdro.id
- !microsoft@lemdro.id
- !chatgpt@lemdro.id
- !bing@lemdro.id
- !reddit@lemdro.id
Lemmy App List
Chat and More
cause of lazy iOS users that can't be bothered to use anything else
Then why are we shaming Apple and not the iOS users? I think Apple is totally reasonable here.
Apple's biggest crimes here are creating a proprietary platform with an exclusive protocol and making it the default messaging protocol on their devices. None of this is really new, though. All that shit is common. We need Signal or Matrix to improve in user-friendliness and even do some marketing to the point where they become viable solutions.
The default messaging protocol is SMS. Unless you are talking with another Apple user
I can send pictures and video over SMS that are viewable anywhere. An iMessage user can only send a patch of 64 color changing macro blocks with some audio. While it's technically true it's the default. it's purposefully degraded to the point of unusability.
Really? That seems odd. I’ve never had a problem sending reasonable quality photos to Android users and I can’t see a business reason why Apple would degrade image sending purposefully- it would drive its own users to get third party apps.
The photos are less the issue than videos. But they definitely reduce the size of them far more than other clients do. At least for non iPhone/ iMessage users. It gets so bad that family doesn't share videos with many of us anymore because of how difficult it is to use something other than iMessage. Or Facebook. But that's a whole other problem.
iMessage degrades images and video on MMS regardless of the capability of the network.
I don't think that's correct - and I can't find anything that substantiates the claim with a quick Google. Source?
Depends on what the majority of people are using.
In markets where iPhone users are not in the majority, that's exactly what's happening: iPhone users are switching to third party apps.
If iPhones users are in the majority, though, then people will just default to iMessage, and non-Apple phones get associated with poor messaging quality. Which creates social pressure for non-iPhone users to buy an iPhone.
So it makes perfect business sense for Apple to degrade the messaging quality when a non-Apple phone joins the conversation.
in other words: the default messaging protocol is imessage, unless that's impossible, in which case it falls back to sms.
I am not an Apple fanboy at all, I have used iPhones for work previously.
RCS debuted three years before iMessage, Apple developed iMessage because no one could get RCS standards together. We still don't have this, Google has theirs, Samsung has another. Not all manufacturers support it and neither do all carriers. In my country it does not exist.
I use SimpleX, but when I used a company iPhone, iMessage worked very well, and it worked everywhere regardless of carrier. RCS does not 15 years after its introduction.
None of this is to say there should not be interoperability, clearly there should be. Historically at least, the blame lies with Google and mobile carriers.
I'm not letting Google off the hook, but Apple could also open the standard for iMessage and bypassed the whole problem. But they'd rather lock in customers than allow everyone to communicate securely and effectively.
More marketing would be nice
As for features, an easy remote backup solution (similar to be bettet than WhatsApp) is the big one for me. Especially on iOS
Android has an easy remote backup system built in. You can save a file to any location, including cloud locations, as long as the cloud service provider plugs into the API. Signal actively disables this feature because they would rather spite users than risk even the shadow of a chance that a user upload an encrytped backup to an internet service that could theoretically then be hacked and hypothetically maybe one day decrypted.
Matrix doesn't have this issue, it just stores encrypted messages on servers.
I'm not sure about Signal being the one, then we just give the power from one company (Apple) to another (Signal). If we want to improve then we should push open protocols where people can host their own infrastructure.
Ideally, I agree. In practice, until federation / decentralization is completely transparent to the end user (unless they choose otherwise), it'll never be adopted at a large scale. IMO that's one of the main obstacles of Lemmy, Mastodon, and others.
Signal is only relatively popular among the privacy-respecting options because setting it up is as easy as setting up WhatsApp. Just by adding a "choose your instance" step, you can cut your user base by an order of magnitude. And that's not mentioning the quality of service, which is much more achievable on a centralized platform, whether that's in terms of feature parity, uptime, bug fixes, or cross-platform support.
Message works, it’s seamless and does a good job. Sure I’ll change to something else if I need to send images or group chat with Android uses, but in the UK that generally means WhatsApp, which I am definitely not keen on.
There is absolutely nothing reasonable with using an inferior and outdated standard compared to what literally everybody else uses.