Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
This is just another example of Apple nickel-and-diming the most basic of features in an attempt to get the upsell.

I honestly suspect it’s a case of “Apple knows 99.9% of customers buying the non-pro phone don’t care about transfer speeds (which they know because of analytics)” and so saving $1 will add up over ~100m phones.

I seriously doubt any significant number of people were upsold on the phone because of transfer speeds. I honestly suspect 90% of people using the Pro phone don’t transfer data via a cable.
 
And Apple is being required to offer it to others by the EU, which you accused me of lying about when I stated it.

Are you going to retract that accusation?
You stated they are required to provide their APIs. WiFi aware isn’t apples. They don’t own it and not a single line of code is needed by Apple to be provided to other phones.
surferfb said:
When talking about EU regulation, everyone should remember the same regulators picking what APIs Apple is required to offer thought EVERY PHONE

The only think that is required is an existing phone using their existing WiFi aware protocol to transfer data to an iPhone that already have the protocol installed and enabled.

Example you download the app quickshare will now be able to file drop to a windows computer or android phone.

But without needing to go in the app you can click on a file in…. Files and send using it
 
Well then you would agree that if everything becomes chromium by the choice of users

Majority chose Chromium on desktop. I'm still tasked with fixing issues on Safari/Mac and Firefox. Unless it's near 100% marketshare, other browser engines need to be supported. Users so far aren't choosing 100%.

And safari have never had zero day exploits either

You asked "2: what security issues?". I provided an answer.

🤔 I wonder what you need to do to exploit 100%

Never said Safari didn't have security issues. You responded as if I made up "security issues" with respect to Chrome. I'm showing you that Chrome security issues are not "made up".

As a wise user said: Apple doesn’t care about market share but revenue growth.

When a user buys an iPhone, they'll possibly buy iCloud storage/Apple TV+/Music/News/Games/AppleCare and so on. And they'll buy into the ecosystem. adding to phone marketshare compounds the revenue growth with services and family of devices.

To say Apple doesn't care is objectively false

Yes because it’s not something users ever have a meaningful impact

that just goes to show port selection isn't all that important to the product. nothing but a minor inconvenience at its worst.

Thebipad transition went backwards for Andre generations for zero resons instead of going with usb c

I have no idea what you wrote here.
 
  • Haha
Reactions: rmadsen3
This is just another example of Apple nickel-and-diming the most basic of features in an attempt to get the upsell.
so USB-C mandate didn't really solve the USB2.0 issue you're trying to point out about lightning.
 
You stated they are required to provide their APIs. WiFi aware isn’t apples. They don’t own it and not a single line of code is needed by Apple to be provided to other phones.
surferfb said:


The only think that is required is an existing phone using their existing WiFi aware protocol to transfer data to an iPhone that already have the protocol installed and enabled.

Example you download the app quickshare will now be able to file drop to a windows computer or android phone.

But without needing to go in the app you can click on a file in…. Files and send using it

I didn’t state they had to provide their APIs. What I said was:

When talking about EU regulation, everyone should remember the same regulators picking what APIs Apple is required to offer thought EVERY PHONE should use Micro USB.

The EU is telling Apple what APIs they have to offer. The EU also thought every phone should use Micro-USB. Where is the lie?
 
Majority chose Chromium on desktop. I'm still tasked with fixing issues on Safari/Mac and Firefox. Unless it's near 100% marketshare, other browser engines need to be supported. Users so far aren't choosing 100%.
Well unless iOS users also chose to use chromium because they favor those browsers over WebKit versions
You asked "2: what security issues?". I provided an answer.
I asked regarding the security issues of allowing a separate webengine on iOS instead of WebKit being the only allowed option. Currently you mention something that is currently the statuesque
Never said Safari didn't have security issues. You responded as if I made up "security issues" with respect to Chrome. I'm showing you that Chrome security issues are not "made up".
I didn’t ask about chrome
When a user buys an iPhone, they'll possibly buy iCloud storage/Apple TV+/Music/News/Games/AppleCare and so on. And they'll buy into the ecosystem. adding to phone marketshare compounds the revenue growth with services and family of devices.

To say Apple doesn't care is objectively false
Then they would target market share, and obviously we see they aren’t but vertical integration to maximize revenue generation
that just goes to show port selection isn't all that important to the product. nothing but a minor inconvenience at its worst.

I have no idea what you wrote here.
I would say it’s a major inconvenience , but not enough to overcome the über inconvenience of Android for me to switch.

I wrote Apple went backwards regarding their usb c implementation with the launch of a newer iOS with lightning and apple pencil 2 with lightning.

So my take is Apple used lightning as another part of their ecosystem strategy to maximize revenue generation.
 
I didn’t state they had to provide their APIs. What I said was:



The EU is telling Apple what APIs they have to offer. The EU also thought every phone should use Micro-USB. Where is the lie?
What API is Apple required to give to anyone else?

The APIs are firmly embedded in iOS. And not a single api is executed on other devices. Everyone else is running their own code.

What API? What framework? What code written by Apple do they give away to Samsung, LG, Microsoft?

(Well the extra punctuation do make a big difference. As I understood you as claiming EU requires their APIs to be executed on other devices.)
 
What API is Apple required to give to anyone else?

The APIs are firmly embedded in iOS. And not a single api is executed on other devices. Everyone else is running their own code.

What API? What framework? What code written by Apple do they give away to Samsung, LG, Microsoft?

(Well the extra punctuation do make a big difference. As I understood you as claiming EU requires their APIs to be executed on other devices.)
What I was saying was the EU is dictating what API’s Apple is required to offer. And the EU thought all phones should be required to have Micro-USB ports. With the unstated implication that the EU isn’t qualified to be making those sorts of decisions - because either they’ve never used Micro-USB and still thought it was ok to mandate everyone use it, OR they have, still thought it was a good idea to make everyone use it, and therefore clearly have no business telling anyone in tech anything 🙂.
 
  • Like
Reactions: I7guy
Well unless iOS users also chose to use chromium because they favor those browsers over WebKit versions

I don't know what you mean. The argument is developers are comfortable developing for 1 engine(webkit) for 1 platform (iOS)

I asked regarding the security issues of allowing a separate webengine on iOS instead of WebKit being the only allowed option. Currently you mention something that is currently the statuesque
You accused me of making up security issues when I pointed out that allowing Chromium engine would allow for security issues.

I didn’t ask about chrome

You responded to my post that was responding to AppliedMicro that mentioned "If Chrome...". If you're going to join the conversation, read the post history.
Then they would target market share, and obviously we see they aren’t

Expanding to China is literally a marketshare driven goal.

I would say it’s a major inconvenience

you would. anecdotal. wallet among many voted for not enough inconvenience to stop buying for most.

but not enough to overcome the über inconvenience of Android for me to switch.

that would be a minor inconvenience. agree to disagree here.

I wrote Apple went backwards regarding their usb c implementation with the launch of a newer iOS with lightning and apple pencil 2 with lightning.


So my take is Apple used lightning as another part of their ecosystem strategy to maximize revenue generation.

Recall I wrote "To say that iPhone would have stuck with lightning for the next 10 years is ridiculous. Obviously they would go portless or USB-C, but definitely not include lightning any longer considering iPads were already switching to USB-C before the mandate."

I don't understand what you mean " Apple went backwards " and "So my take is Apple used lightning as another part of their ecosystem " when Apple launched iPad with USB-C without any sort of mandate.
 
What I was saying was the EU is dictating what API’s Apple is required to offer. And the EU thought all phones should be required to have Micro-USB ports. With the unstated implication that the EU isn’t qualified to be making those sorts of decisions - because either they’ve never used Micro-USB and still thought it was ok to mandate everyone use it, OR they have, still thought it was a good idea to make everyone use it, and therefore clearly have no business telling anyone in tech anything 🙂.
Well as far as I’m aware the APIs are already offerd with the exception of contractual agreements that prevents some of their uses that makes any alternative options impossible to use properly.

And the standard was provided by everyone in the industry. EU didn’t pick micro USB. The group Apple was part of did. The specification EN/IEC 62684 was active from 2009 to 2014.

The exact same date USB C was launched notice how the standard just disappeared and stop being used

And you might have forgotten but when this was implemented we had a sea of cables. And the market industry decided what they were to use, not EU. EU just asked them to pick one
IMG_2249.jpeg
 
What I was saying was the EU is dictating what API’s Apple is required to offer. And the EU thought all phones should be required to have Micro-USB ports. With the unstated implication that the EU isn’t qualified to be making those sorts of decisions - because either they’ve never used Micro-USB and still thought it was ok to mandate everyone use it, OR they have, still thought it was a good idea to make everyone use it, and therefore clearly have no business telling anyone in tech anything 🙂.
Well it seems to be a sounding success regarding apples new WiFi aware framework
I don't know what you mean. The argument is developers are comfortable developing for 1 engine(webkit) for 1 platform (iOS)
Well if it was chromium on all devices it would be easier as well. (iOS,Android, windows and Mac)
You accused me of making up security issues when I pointed out that allowing Chromium engine would allow for security issues.

You responded to my post that was responding to AppliedMicro that mentioned "If Chrome...". If you're going to join the conversation, read the post history.
Fair but doesn’t seem to be a security issue that matters considering it’s the status quo. Especially when said exploit would only impact the chrome users, and not WebKit users and viseversa.

Expanding to China is literally a marketshare driven goal.


you would. anecdotal. wallet among many voted for not enough inconvenience to stop buying for most.

that would be a minor inconvenience. agree to disagree here.
Well the inconvenience of iOS/iphone isn’t great enough to justify the larger inconveniences of Android.
Recall I wrote "To say that iPhone would have stuck with lightning for the next 10 years is ridiculous. Obviously they would go portless or USB-C, but definitely not include lightning any longer considering iPads were already switching to USB-C before the mandate."

I don't understand what you mean " Apple went backwards " and "So my take is Apple used lightning as another part of their ecosystem " when Apple launched iPad with USB-C without any sort of mandate.
I guess agree to disagree. I believe Apple would have continued lightning for many more years. Might have even updated it to usb 3.
 
  • Love
Reactions: rmadsen3
Well if it was chromium on all devices it would be easier as well. (iOS,Android, windows and Mac)

I'm glad you agree it would be easier for developers!
My original statements are:
"The argument is developers are comfortable developing for 1 engine(webkit) for 1 platform (iOS)"
and
"I, along with many other engineers, enjoy only working with one engine to implement websites for."

Fair but doesn’t seem to be a security issue that matters considering it’s the status quo. Especially when said exploit would only impact the chrome users, and not WebKit users and viseversa.

Not sure what you mean. iOS users using Chromium engine getting exploited is a security issue.

Well the inconvenience of iOS/iphone isn’t great enough to justify the larger inconveniences of Android.
That would be a minor issue.
I guess agree to disagree.

I don't know what I'm agreeing to disagree with as I'm saying for the third time I really don't understand what argument you're trying to make here with respect to what I said.

I believe Apple would have continued lightning for many more years. Might have even updated it to usb 3.

Ah, ok. So you're saying Apple would have used the same lighting port until 2035. Yep agree to disagree here. That is ridiculous IMO.
 
  • Haha
Reactions: rmadsen3
I honestly suspect it’s a case of “Apple knows 99.9% of customers buying the non-pro phone don’t care about transfer speeds (which they know because of analytics)” and so saving $1 will add up over ~100m phones.

I seriously doubt any significant number of people were upsold on the phone because of transfer speeds. I honestly suspect 90% of people using the Pro phone don’t transfer data via a cable.
Most people buying the Pro phone probably don't realise it's a Ferrari to go to the shops. There is a strong arguement the average consumer doesn't need anything more than a Pixel 9a/16e. I know I'm in that bracket.
 
  • Like
Reactions: surferfb
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.