Am 02.02.23 um 16:45 schrieb sms:
> On 2/2/2023 7:27 AM, Jason H wrote:
>
> <snip>
>
>> Anyway, IP based messaging solutions (even Metastatic's awful Facebook
>> Messenger) are vastly better than SMS.
>
> Google is also upset that Apple refuses to implement RCS on the iPhone,

Guess why!
RCS is more than dead and completely outdated. We discussed that already
hundreds of times in these groups. Apple has to lose a unique position
and Google is the big loser in the messenger field and has no service/app.

> In any case, the good news is that Android users that do want iMessage
> capability there are now multiple options. AirMessage is one, Beeper is
> another.

Not of any interest.

--
Gutta cavat lapidem (Ovid)

sms <scharf.steven@geemail.com> wrote:
> On 2/1/2023 7:51 PM, Michael wrote:
>> On Wed, 1 Feb 2023 13:11:43 -0800, sms wrote:
>>
>>> As many are aware, one big selling point of the iPhone is iMessage,
>>> which unlike multi-platform messaging apps such as WhatsApp, Signal,
>>> Line, or WeChat, is only available for Apple operating systems.
>>
>> How is being "only available for Apple" the imessage selling point?
>> Anyway my message app already works for non-group and message group chats.
>
> No, it's not an iMessage selling point, it's an iPhone selling point, at
> least in the U.S. where platform-independent messaging apps are not that
> popular.
>
> We've all read about "green bubble versus blue bubble," as in the
> article "iPhone or Android? Your phone choice could be hampering your
> love life"
> <https://www.cnet.com/culture/iphone-or-android-your-phone-choice-could-be-impacting-your-love-life/>,where
>
> OKCupid found that 31% of its users would not message someone that was
> not using an iPhone and 27% said that green bubbles are worse than
> mansplaining.
>
> That article also talked about how the iMessage issue has even come up
> in lawsuits: "There's been a question of whether iMessage's sheer
> awkwardness in getting along with Android amounts to stifling the
> competition." This is rather ridiculous, Google is just upset that its
> own messaging app, Google Chat, has not become widely used.
>
>
>
>
>

As an iPhone user the only thing I don’t like about the SMS green bubble is
the white text on green background which makes it hard to read compared to
the iMessage white text on blue background. And since it’s an iPhone I
can’t change the color to something with more contrast.

In article <trgr1q$vmrj$1@dont-email.me>, badgolferman
<REMOVETHISbadgolferman@gmail.com> wrote:

> And since it¹s an iPhone I
> can¹t change the color to something with more contrast.

yes you can, in accessibility, which has a lot more options than
android.

On 2/2/2023 9:14 AM, badgolferman wrote:

<snip>

> As an iPhone user the only thing I don’t like about the SMS green bubble is
> the white text on green background which makes it hard to read compared to
> the iMessage white text on blue background. And since it’s an iPhone I
> can’t change the color to something with more contrast.

Yes, that is a bit annoying. It would be a little better to have black
text on that green background, but even that is not that great, what
they need is to use a darker shade of green. But the chance of them
doing anything to improve iMessage⇄SMS messaging is slim.

nospam wrote:

>In article <trgr1q$vmrj$1@dont-email.me>, badgolferman
><REMOVETHISbadgolferman@gmail.com> wrote:
>
>> And since it¹s an iPhone I
>> can¹t change the color to something with more contrast.
>
>yes you can, in accessibility, which has a lot more options than
>android.

Okay, I changed the contrast setting and will test it for awhile. Now
the light green bubble is dark green. Thanks for the tip!

In article <trgsjd$vprr$1@dont-email.me>, sms
<scharf.steven@geemail.com> wrote:

>
> > As an iPhone user the only thing I don¹t like about the SMS green bubble is
> > the white text on green background which makes it hard to read compared to
> > the iMessage white text on blue background. And since it¹s an iPhone I
> > can¹t change the color to something with more contrast.
>
> Yes, that is a bit annoying. It would be a little better to have black
> text on that green background, but even that is not that great, what
> they need is to use a darker shade of green. But the chance of them
> doing anything to improve iMessage?SMS messaging is slim.

once again, you're wrong.

the ability to change contrast and other options has been there since
before there was imessage.

Am 02.02.23 um 18:41 schrieb sms:
> On 2/2/2023 9:14 AM, badgolferman wrote:
>
> <snip>
>
>> As an iPhone user the only thing I don’t like about the SMS green bubble is
>> the white text on green background which makes it hard to read compared to
>> the iMessage white text on blue background. And since it’s an iPhone I
>> can’t change the color to something with more contrast.
>
> Yes, that is a bit annoying. It would be a little better to have black
> text on that green background, but even that is not that great, what
> they need is to use a darker shade of green. But the chance of them
> doing anything to improve iMessage⇄SMS messaging is slim.

Nothing but bullshit again. Go visit your ophthalmologist.
I can easily read the text in the green bubbles from a distance of more
than 4 feet.

--
Gutta cavat lapidem (Ovid)

On 2/2/2023 9:53 AM, badgolferman wrote:
> nospam wrote:
>
>> In article <trgr1q$vmrj$1@dont-email.me>, badgolferman
>> <REMOVETHISbadgolferman@gmail.com> wrote:
>>
>>> And since it¹s an iPhone I
>>> can¹t change the color to something with more contrast.
>>
>> yes you can, in accessibility, which has a lot more options than
>> android.
>
>
> Okay, I changed the contrast setting and will test it for awhile. Now
> the light green bubble is dark green. Thanks for the tip!

Turning on bold text also helps.

One thing nice about my Google Pixel 7 Pro, compared to my iPhone 11, is
that the Pixel's accessibility settings are a lot more comprehensive
than those on my iPhone 11, but I think that this is a Pixel thing and
not for all Android 13 devices.

In article <trh15g$10inn$2@dont-email.me>, sms
<scharf.steven@geemail.com> wrote:

> One thing nice about my Google Pixel 7 Pro, compared to my iPhone 11, is
> that the Pixel's accessibility settings are a lot more comprehensive
> than those on my iPhone 11,

obvious trolling and very much false.

sms wrote:

>> Okay, I changed the contrast setting and will test it for awhile. Now
>> the light green bubble is dark green. Thanks for the tip!
>
> Turning on bold text also helps.
>
> One thing nice about my Google Pixel 7 Pro, compared to my iPhone 11, is
> that the Pixel's accessibility settings are a lot more comprehensive
> than those on my iPhone 11, but I think that this is a Pixel thing and
> not for all Android 13 devices.

Why would Apple lock users out from assigning colors to each contact?

All Android devices have the choice of default messenger app, some of which
are quite sophisticated, where changing colors would be trivial for them.

Must Apple cynically control virtually every aspect of the user experience?

On Thu, 02 Feb 2023 14:16:59 -0500, nospam wrote:

> very much false.

I like that Android messenger apps can set a different ringtone for each
important contact. Can the iMessage app do the same for iPhone owners?

In article <trh2us$11253$1@dont-email.me>, alan <bitbucket@nospam.com>
wrote:

> I like that Android messenger apps can set a different ringtone for each
> important contact.

custom ringtones has been there since the first iphone.

On Thu, 02 Feb 2023 14:34:11 -0500, nospam wrote:

>> I like that Android messenger apps can set a different ringtone for each
>> important contact.
>
> custom ringtones has been there since the first iphone.

You can set a custom iMessage incoming message tone & custom vibrate
pattern for each iMessage contact like you can with Android messages?

In article <trh3n3$116ft$1@dont-email.me>, alan <bitbucket@nospam.com>
wrote:

>
> >> I like that Android messenger apps can set a different ringtone for each
> >> important contact.
> >
> > custom ringtones has been there since the first iphone.
>
> You can set a custom iMessage incoming message tone & custom vibrate
> pattern for each iMessage contact like you can with Android messages?

what part wasn't clear?

On 2/2/2023 11:19 AM, Nic wrote:
> sms wrote:
>
>>> Okay, I changed the contrast setting and will test it for awhile. Now
>>> the light green bubble is dark green. Thanks for the tip!
>>
>> Turning on bold text also helps.
>>
>> One thing nice about my Google Pixel 7 Pro, compared to my iPhone 11, is
>> that the Pixel's accessibility settings are a lot more comprehensive
>> than those on my iPhone 11, but I think that this is a Pixel thing and
>> not for all Android 13 devices.
>
> Why would Apple lock users out from assigning colors to each contact?

Every feature that a company adds to an operating system has costs:
software development, testing, and support. There can also be legal
issues, if some feature is patented and royalties or licensing fees
would need to be paid.

The other issue is that Android users have a choice of many different
devices from different manufacturers so there's competition to include
features and capabilities. For iPhone, few users are going to move to
Android in order to get some minor feature that isn't available on an
iPhone, they'll just do without.

<snip>

> Must Apple cynically control virtually every aspect of the user experience?

Only some aspects!

In article <trh4rf$11clt$1@dont-email.me>, sms
<scharf.steven@geemail.com> wrote:

> > Why would Apple lock users out from assigning colors to each contact?
>
> Every feature that a company adds to an operating system has costs:
> software development, testing, and support. There can also be legal
> issues, if some feature is patented and royalties or licensing fees
> would need to be paid.

there are no patents for message colours. it's a simple design issue
entirely lost on android users.

> The other issue is that Android users have a choice of many different
> devices from different manufacturers so there's competition to include
> features and capabilities.

all of which are competition for iphone users.

> For iPhone, few users are going to move to
> Android in order to get some minor feature that isn't available on an
> iPhone, they'll just do without.

more commonly, android users move to iphone for the many features that
are available on iphone but *not* available on android.

apple periodically reports on switchers, and it's always higher *to*
iphone than away from it. there's an earnings call later today and they
may have updated data.

sms wrote:

>> Why would Apple lock users out from assigning colors to each contact?
>
> Every feature that a company adds to an operating system has costs:
> software development, testing, and support. There can also be legal
> issues, if some feature is patented and royalties or licensing fees
> would need to be paid.

I doubt there are patents for something as obvious as setting the colors.
> The other issue is that Android users have a choice of many different
> devices from different manufacturers so there's competition to include
> features and capabilities. For iPhone, few users are going to move to
> Android in order to get some minor feature that isn't available on an
> iPhone, they'll just do without.

Can iPhone users at least choose any default cellular sms text messenger?

>> Must Apple cynically control virtually every aspect of the user experience?
>
> Only some aspects!

You have to wonder why kind of person puts up with such cynical control.

nospam wrote:

> more commonly, android users move to iphone for the many features that
> are available on iphone but *not* available on android.

You have to wonder why kind of person puts up with such cynical control.

On 2023-02-02 11:42, alan wrote:
> On Thu, 02 Feb 2023 14:34:11 -0500, nospam wrote:
>
>>> I like that Android messenger apps can set a different ringtone for each
>>> important contact.
>>
>> custom ringtones has been there since the first iphone.
>
> You can set a custom iMessage incoming message tone & custom vibrate
> pattern for each iMessage contact like you can with Android messages?

Please change your posting nym if you're going to be this stupid.

On 2/2/2023 12:42 PM, Nic wrote:
> nospam wrote:
>
>> more commonly, android users move to iphone for the many features that
>> are available on iphone but *not* available on android.
>
> You have to wonder why kind of person puts up with such cynical control.

There are some features available on iPhones that are not available on
any Android device, and for which there is no Android equivalent, either
native or via an app and no workaround. It's not "many" but it's "some."

I went down the list in the document "50 iOS & iPhone Features Which
[many] Android Users Wish they Had and 210 Android & Android Phone
Features Which [many] iOS Users Wish they Had
<docs.google.com/document/d/1JznrWfGJDA8CYVfjSnPTwfVy8-gAC0kPyaApuJTcUNE>,
looking for items for which there is no Android workaround or
equivalent. I found seven.

On the other hand, there are about 150 items on the Android list for
which there is no workaround to get that capability for iOS: some are
possible if you jailbreak the iOS device, but for many it's a hardware
limitation that prevents the iPhone from having the feature.

That said, even when there is a workaround on iOS, or a workaround on
Android, it's often not an optimal solution compared to the
implementation on the other platform.

The general response, from our resident trolls, whenever a missing
feature is pointed out is "well not a lot of users are interested in
having that feature" or "no platform has every feature."

In article <trhbde$12fji$1@dont-email.me>, sms
<scharf.steven@geemail.com> wrote:

> There are some features available on iPhones that are not available on
> any Android device, and for which there is no Android equivalent, either
> native or via an app and no workaround. It's not "many" but it's "some."

actually, it is 'many', *far* more than what you claim.

> looking for items for which there is no Android workaround or
> equivalent. I found seven.

your list is deliberately and woefully incomplete to further your
trolling narrative.

> On the other hand, there are about 150 items on the Android list for
> which there is no workaround to get that capability for iOS:

demonstrably false. most of what you claim having no workaround can
easily be done, often without any additional apps, i.e., it's part of
ios itself. either you don't know how to do it or you are lying about
it being impossible. you also refuse to acknowledge that there can be
alternate solutions to a given task, further skewing your numbers.

> some are
> possible if you jailbreak the iOS device, but for many it's a hardware
> limitation that prevents the iPhone from having the feature.

nope. the limitation is you.

whenever you can't figure out how to do something, you automatically
assume it is prohibited rather than take the time to find out how to do
it, which is usually takes very little time.

> That said, even when there is a workaround on iOS, or a workaround on
> Android, it's often not an optimal solution compared to the
> implementation on the other platform.

the opposite is true.

nearly always, ios implementations are easier and with less hassle,
often without needing additional apps.

> The general response, from our resident trolls, whenever a missing
> feature is pointed out is "well not a lot of users are interested in
> having that feature" or "no platform has every feature."

no, the general response is to explain how to actually do what you
claim can't be done, which you ignore and then bash people (as you did
above).

sms wrote:

>>> more commonly, android users move to iphone for the many features that
>>> are available on iphone but *not* available on android.
>>
>> You have to wonder why kind of person puts up with such cynical control.
>
> There are some features available on iPhones that are not available on
> any Android device, and for which there is no Android equivalent, either
> native or via an app and no workaround.

I think probably the "main feature" is Apple advertises to scared people
that they'll be "safer" by Apple controlling every aspect of the iPhone.

> It's not "many" but it's "some."

You have to be careful that you prioritize features that don't exist on one
platform or the other rather than focusing on features "you like better."

An example would be sd card slots don't exist on iOS, so that's fair game,
but in your document you listed things like Apple News, which of course
isn't on Android and you may like it better but "news" apps are on Android.

More words than are in the English language have been expended upon the
relative merits of certain applications, like newsreaders, which are on
both platforms, but where the Apple newsreader is perhaps better.
> I went down the list in the document "50 iOS & iPhone Features Which
> [many] Android Users Wish they Had and 210 Android & Android Phone
> Features Which [many] iOS Users Wish they Had
> <docs.google.com/document/d/1JznrWfGJDA8CYVfjSnPTwfVy8-gAC0kPyaApuJTcUNE>,
> looking for items for which there is no Android workaround or
> equivalent. I found seven.

It would be nice to look in more detail at those seven because Android is
much like Windows and Linux in that everything you want to do, you can do.

What you need to focus on first & foremost in your doc are features which
are on one platform but are completely missing from the other platform.

For that you've mentioned seven but I went to look and couldn't find them.

An example is you noted the battery percentage indicator in your doc, where
you can like the Android options better but at least the iPhone has it too.

More words than exist have been expended on the merits of two different
apps that do the same thing, whether on the same or different platforms.

No consensus will ever be found for such things as people will consider
each variant of the same feature differently - so you need not go there.

What you want to focus on are the features completely missing from one or
the other first, and make sure those are properly described in your doc.

> On the other hand, there are about 150 items on the Android list for
> which there is no workaround to get that capability for iOS: some are
> possible if you jailbreak the iOS device, but for many it's a hardware
> limitation that prevents the iPhone from having the feature.

If you have to jailbreak a device just to get it to do what you want to do
with it, then that's a limitation of the device that shouldn't be there.

> That said, even when there is a workaround on iOS, or a workaround on
> Android, it's often not an optimal solution compared to the
> implementation on the other platform.

It's easiest to first start with the seven things that are not on Android.

> The general response, from our resident trolls, whenever a missing
> feature is pointed out is "well not a lot of users are interested in
> having that feature" or "no platform has every feature."

If the feature exists on either iOS or Android then "enough" users want it.
What are those seven that you found on iOS completely lacking in Android?

On 02 Feb 2023, nospam <nospam@nospam.invalid> posted some news
<news:020220231820301859%nospam@nospam.invalid>:

> your list is deliberately and woefully incomplete to further your
> trolling narrative.

Why don't you post the URL to your Google doc instead of always saying all
five hundred pages of his Google doc must be wrong because you said so.

On 2023-02-02, rdb <rdb@usa.usa> wrote:
> On 02 Feb 2023, nospam <nospam@nospam.invalid> posted some news
><news:020220231820301859%nospam@nospam.invalid>:
>
>> your list is deliberately and woefully incomplete to further your
>> trolling narrative.
>
> Why don't you post the URL to your Google doc instead of always saying
> all five hundred pages of his Google doc must be wrong because you
> said so.

Hear hear! Only those who have Google doc lists of advocacy talking
points have any place in these discussions. ; )

--
E-mail sent to this address may be devoured by my ravenous SPAM filter.
I often ignore posts from Google. Use a real news client instead.

JR

On 2/2/2023 3:38 PM, rdb wrote:
> On 02 Feb 2023, nospam <nospam@nospam.invalid> posted some news
> <news:020220231820301859%nospam@nospam.invalid>:
>
>> your list is deliberately and woefully incomplete to further your
>> trolling narrative.
>
> Why don't you post the URL to your Google doc instead of always saying all
> five hundred pages of his Google doc must be wrong because you said so.

It's only 105 pages. If I missed anything, for either iOS or Android,
I'm happy to add it.

---------------------------------------•-----------------------------------------
✓ 50 iOS & iPhone Features Which [many] Android Users Wish they Had ✓
✓ 210 Android & Android Phone Features Which [many] iOS Users Wish
they Had ✓
<https://tinyurl.com/iOS-Android-Features>

✓ 105 Pages of Extensively Referenced Information with Hundreds of
Citations ✓
✓ 100% Fact Checked ✓
---------------------------------------•-----------------------------------------