Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Here is the part that makes no sense to me and maybe I’m alone with this thinking. But Apple already made a big error with the vaporware demo and not being close to ready. But what I don’t understand is if it works 60-80% of the time why not do what Apple has always done release it in beta to developers only and keep it in beta while you work on it. It’s not as though we don’t have historical reference regarding this practice. This approach would to me have minimized the backlash to an extent. I think people are more upset because not only they feel tricked with the iPhone 16 push but they feel like it’s nowhere near ready. 60-80% is manageable from a beta perspective. Am I wrong here ? It would calm all these speculations. What it makes you think that this working 60-80% is a lie. And the fact that Apple has now been caught in a lie to many in public they don’t have the credibility for it anymore. So prove everyone wrong and show where you’re at. What Apple is trying to do isn’t easy but being 60-80% is something I think will calm everyone down temporarily
 
You are right, Apples misrepresentation here deserves accountability from Apple.
I see what you did there: subtly shifting from ‘personal responsibility’ to ‘corporate blame’ as a way to avoid acknowledging the real issue. Classic deflection.

But here’s the thing: Misrepresentation only matters if someone makes a purchase solely based on an unverified promise. No one is forcing anyone to buy in before something is delivered—that’s a choice.

Expecting Apple to be held accountable for a customer’s impatience isn’t ‘accountability’; it’s just shifting blame.

But if outsourcing responsibility makes you feel better, by all means, carry on.
 
Productivity of a team is not fully realized when they’re working from home. I understand that Apple utilizes a hybrid WFH model. But these types of shortcomings will continue to happen until they bring everyone back to fully in-person work.
Or the lack of employee flexibility is preventing Apple from recruiting talented folks from a world wide candidate pool. Not all first rate developers live -- or want to live -- within a commutable radius of Cupertino.
 
You buy products based on promised future updates?
That’s a you problem.
When they push heavy advertising campaigns showing off a feature IN WORKING STATE on their new iPhone to advertise the new iPhone, that’s an APPLE problem.

Stop defending the 4 trillion dollar company, if it wasn’t ready then don’t advertise it.
 
Wait. So, it’s 60-80% NOW so when they demo it, I’m guessing it was around 20%? If so they had no business demoing it. I’d at least hope it was 60-80 when it was announced.
Exactly mate & that’s the point
They had absolutely no idea if it could actually work as expected but still announced the thing anyway & certain people think that’s acceptable
 
While I agree that buying a product based on promised features is a bad idea, I completely disagree with what you’re saying.

This is obviously a fundamental Apple problem. The fact that someone buys something based off what Apple promises means that they trust Apple. The fact that Apple is now just your typical tech company that announces vaporware and doesn't deliver means that we can no longer trust Apple. That is absolutely an “Apple” problem not a “you” problem.
He’s too busy sucking on the teet of capitalism to hear you.
 
Here is the part that makes no sense to me and maybe I’m alone with this thinking. But Apple already made a big error with the vaporware demo and not being close to ready. But what I don’t understand is if it works 60-80% of the time why not do what Apple has always done release it in beta to developers only and keep it in beta while you work on it. It’s not as though we don’t have historical reference regarding this practice. This approach would to me have minimized the backlash to an extent. I think people are more upset because not only they feel tricked with the iPhone 16 push but they feel like it’s nowhere near ready. 60-80% is manageable from a beta perspective. Am I wrong here ? It would calm all these speculations. What it makes you think that this working 60-80% is a lie. And the fact that Apple has now been caught in a lie to many in public they don’t have the credibility for it anymore. So prove everyone wrong and show where you’re at. What Apple is trying to do isn’t easy but being 60-80% is something I think will calm everyone down temporarily
My take is that they have an optics problem regarding Apple AI and have painted themselves into a corner. If they released a beta now that was only partially working it would be a PR disaster, essentially confirming it was false advertising.

If they had not previously marketed it as working, sure release a beta. Unfortunately for them they have no choice now but to release a polished, functional Apple AI.
 
  • Like
Reactions: Tagbert
By now, we should all know what hallucination is on LLMs, I think Apple is learning just like everyone else, that these models, specially small ones trying to do RAG locally, won’t be correct more than 80% of the time. That’s ok when you want to tell your son some chemistry lesson you had 30 years ago, BUT NOT COOL when you want to know when your mother is getting to the airport.

That’s why nobody else has this solution as well.
 
It was indeed a bait n switch. False advertising as well.
Apple needs to issue an apology.

Also, something else nobody seems willing to mention, but I’ll say it:
Productivity of a team is not fully realized when they’re working from home. I understand that Apple utilizes a hybrid WFH model. But these types of shortcomings will continue to happen until they bring everyone back to fully in-person work.
I know I’ll catch a lot of disagreement for this, but it’s the truth.
Have you headed both a wfh and in-office software development team? If so can you explain why in-office is the superior model?

Is it the office birthday parties? Or does commuting in SF traffic and having to live in one of the most expensive metro areas in the world really boost team morale? Maybe they’re stoked to be paying $1000/sqft for their home
 
My take is that they have an optics problem regarding Apple AI and have painted themselves into a corner. If they released a beta now that was only partially working it would be a PR disaster, essentially confirming it was false advertising.

If they had not previously marketed it as working, sure release a beta. Unfortunately for them they have no choice now but to release a polished, functional Apple AI.
Which I agree but maybe I’m delusional but it’s already a PR disaster now. Now everyone already feels it was false advertising. We already in that corner. Right now everyone thinks that you have nothing at all. They all think it’s a complete lie regarding the features. Would it not be better to say no everyone we are working on it. This is where we are at we just don’t want to release it officially to the public until it’s to Apple standards.
But until then we will utilize the beta program as it was intended. Because the beta program was meant to give developers the opportunity to test their apps with the new software and features but to also allow developers to experience the new features Apple is working on and give feedback. The device would be on non-daily driver as the program suggest and for those who don’t they take responsibility for the errors impacting them.

But I guess my thought is proving that guys we aren’t lying we didn’t bait and switch this was our intent. We have a working model but it’s not to the standards that Apple has is better than we not even close and we can’t even let developers and beta testers even get a glimpse of it. Seeing a 60-80% version to me would make me feel like ok it’s not perfect but at least I know it isn’t a pipe dream or never going to happen i just need patience for polished product.
 
  • Like
Reactions: tmarsden
Here is the part that makes no sense to me and maybe I’m alone with this thinking. But Apple already made a big error with the vaporware demo and not being close to ready. But what I don’t understand is if it works 60-80% of the time why not do what Apple has always done release it in beta to developers only and keep it in beta while you work on it. It’s not as though we don’t have historical reference regarding this practice. This approach would to me have minimized the backlash to an extent. I think people are more upset because not only they feel tricked with the iPhone 16 push but they feel like it’s nowhere near ready. 60-80% is manageable from a beta perspective. Am I wrong here ? It would calm all these speculations. What it makes you think that this working 60-80% is a lie. And the fact that Apple has now been caught in a lie to many in public they don’t have the credibility for it anymore. So prove everyone wrong and show where you’re at. What Apple is trying to do isn’t easy but being 60-80% is something I think will calm everyone down temporarily

That’ll be because it’s stuck at 70% and won’t get any better and that’s good enough.

If they release it and it is stuck there it’s useless and they’re in trouble.

This whole technology hype peak is a lie. If they had any backbone they’d have just skipped this. But the entire tech press was hounding them for it.
 
That’ll be because it’s stuck at 70% and won’t get any better and that’s good enough.

If they release it and it is stuck there it’s useless and they’re in trouble.

This whole technology hype peak is a lie. If they had any backbone they’d have just skipped this. But the entire tech press was hounding them for it.
But 70% is progress. It may not be as fast as we want but it’s progress. But to me that ain’t the point now. The point now is I don’t believe the 70% at all. So that’s my thing. Apple is getting cooked now even more because right now no one believe 2% let alone 70%. It would be seven more disastrous if they realized it to general public and it’s 70% but to beta testers why not use beta tester to get more feedback. The more feedback you get the better.

As long as you stamp a beta label on it and make it only accessible to beta developers and state that do not recommend on daily drivers you will create hype on what’s actually possible. And it will allow the hype machine to continue working with beta testers who have YouTube channels and etc talking about when it works it works well but still ways to go.

But right now everyone is saying it will never happen and you can squash that.
 
Hmmm…
WWDC 1998: Mac OS X announced, wouldn’t ship for another three years..
WWDC 2004: Tiger announced, didn’t release until April 2005.
WWDC 2005: Leopard announced for a late 2006 release.
WWDC 2006: Leopard demonstrated, scheduled for an early 2007 release.
WWDC 2007: Leopard demonstrated once again as it had been delayed from an early 2007 release to an October 2007 release. That is now two delays.
WWDC 2008: mobile me and push notifications announced for a September 2008 release. Mobile be launched and was a disaster, push notifications were pushed back until June 2009 with 3.0 instead of 2.1 as promised.
WWDC 2009: multimedia messaging and tethering released internationally, not available in the US until that September.
WWDC 2010: white iPhone 4 announced and scheduled for July, actually released in April 2011. iOS 4 announced for the iPhone and iPad, delayed for the iPad until November. Game Center announced for iOS 4, delayed until 4.1.
WWDC 2012: iCloud integration announced for OS X Mountain Lion, delayed two months after the initial release.
WWDC 2013: iCloud Drive announced for iOS 7, delayed until a month after initial release.
WWDC 2014: new Apple photos app announced, not scheduled to be released until the following year, which would be 2015.
WWDC 2017: messages in iCloud and AirPlay 2 announced for a fall ship date, didn’t end up shipping until May of the following year.

Delays are not new.
Running advertisements for unreleased features is, and it was a massive mistake, but almost every year of the iPhones existence they have saved a feature or two for a later date.

How many of those things were tied to hardware releases and the selling point in promotional material?
 
  • Like
Reactions: Mr_Ed and Beepster
But 70% is progress. It may not be as fast as we want but it’s progress. But to me that ain’t the point now. The point now is I don’t believe the 70% at all. So that’s my thing. Apple is getting cooked now even more because right now no one believe 2% let alone 70%. It would be seven more disastrous if they realized it to general public and it’s 70% but to beta testers why not use beta tester to get more feedback. The more feedback you get the better.

As long as you stamp a beta label on it and make it only accessible to beta developers and state that do not recommend on daily drivers you will create hype on what’s actually possible. And it will allow the hype machine to continue working with beta testers who have YouTube channels and etc talking about when it works it works well but still ways to go.

But right now everyone is saying it will never happen and you can squash that.
The gap from 70% to 100% may take years to close is the issue.

It may never even reach 95%, and that is in direct conflict with Apple’s entire “a thousand no’s for every yes” ethos.

Basic singular questions to Siri can fail (but shouldn’t) because you can point people to alternatives.

The tight system-wide integration to accomplish complex tasks which they described needs to work every time, especially for third parties to integrate it.
 
  • Like
Reactions: klasma
Yes. It only proves they delayed it for reasons unknown to any of us. Most likely it was working and they hit a snap in testing and decided to delay it to iOS 19.
You mean ios 20. Here Apple is still trying to promise something for the next version at the end of its update cycle. It loses its punch if you're marketing. Didn't they just try this? It's yet more marketing. 19.999999 Just can't say 20
 
  • Like
Reactions: nt5672 and I7guy
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.