Apple's CFO Suggests iPad Pro Won't Be Refreshed in 2019

[RevTEG]

Mmmm, just last night used it for 2hrs in bed and lost 50% charge. (from 88% to 40%). iOS 13.2

It wasn't an issue on iOS 12 so not sure its entirely a hardware issue... could be software related, but don't really want to reset. Waiting and hoping for an 13.2.x update to improve it otherwise I will be trying a reset, then asking Tim Apple about a replacement.

Go for the replacement. The masses are not having you issues, so why wait on a maybe fix? Just take it in..

 

[Macaholic868]

Exactly. I’ve been saying this for years. Apple needs to upgrade hardware and software less often. However, most people don’t seem to understand this and every time I say what you just said I get a response from someone saying that it’s impossible, that Apple can’t, that they have to keep the stockholders happy, etc.

I would simply say that anybody who claims that Apple

Exactly. I’ve been saying this for years. Apple needs to upgrade hardware and software less often. However, most people don’t seem to understand this and every time I say what you just said I get a response from someone saying that it’s impossible, that Apple can’t, that they have to keep the stockholders happy, etc.

People who respond to you in that way don’t know what they are talking about. Apple can do whatever it wants to do regardless of what shareholders think so long as they maintain their level of profitability and the board of directors is onboard with the direction of the company.

We already know that the board understands that changing market conditions are leading to reduced year over year sales of mobile devices. Apple hasn’t hidden the fact that it’s focusing more on services to help make up for that lost revenue.

They could easily make a change like this. Obviously they can’t put out a new hardware rev without putting out an updated OS to support it but the iOS 13 release fiasco is a prime example of why their hardware and software release cycles need to be changed and unlinked from one another.

Code supporting the iPhone 11 line of hardware should’ve been inserted into both the iOS 12 and iOS 13 code bases so that Apple could have shipped the device with whatever version of iOS was the most ready for prime time when the hardware was ready to ship.

It’s not like Apple shipped the iOS 13 golden master with support for all of the software features that were possible as a result of the new iPhone 11 hardware. Apple should’ve never made iOS support for the new iPhone 11 hardware completely and totally contingent on the release of iOS 13.

Instead of being prepared to ship the iPhone 11 whether or not iOS 13 was ready for prime time Apple knowingly shipped it with a version of iOS 13 that it knew had issues expecting non-iPhone 11 users to know that they should wait for the iOS 13.1 update that Apple was going to release a week later. That’s unacceptable, embarrassing and unnecessary.

Then they follow that beauty up with the iOS 13.2 HomePod bricking issue. Apple has had several weeks of bad PR and will continue to go through times like this until they put a stop to these artificially self-imposed yearly hardware and software refresh cycles.

 

[lartola]

New feature rollouts in .1, .2, .3 releases are already common. I can’t remember the last time all the features promised at WWDC came in the .0 release. They’re added when they’re ready. Some complain loudly and incessantly when that occurs but that’s no surprise

That's exactly the problem. Every time Apple has had to roll out new features in .1,.2,.3 releases that means the software announced in June wasn't ready for a September launch. If that was the case, Apple shouldn't even be announcing new software every year in June in the first place, but rather they should have scheduled each WWDC event at least a year and a half after the previous one to have additional time to work on the software. And that, it turn would have give them extra time to work on the new hardware too and come up with a much better hardware refresh. It's clear as crystal that 3-3.5 months is not even close to being enough time for Apple to have a new software update ready to launch. iOS 11 showed that more clearly than any other iOS version, as Apple had to postpone one of its promised features (messages in the cloud) for nearly an entire year after the initial release of the software and released it just a couple of days before the next WWDC event where iOS 12 was announced.

 

[PickUrPoison]

That's exactly the problem. Every time Apple has had to roll out new features in .1,.2,.3 releases that means the software announced in June wasn't ready for a September launch. If that was the case, Apple shouldn't even be announcing new software every year in June in the first place, but rather they should have scheduled each WWDC event at least a year and a half after the previous one to have additional time to work on the software. And that, it turn would have give them extra time to work on the new hardware too and come up with a much better hardware refresh. It's clear as crystal that 3-3.5 months is not even close to being enough time for Apple to have a new software update ready to launch. iOS 11 showed that more clearly than any other iOS version, as Apple had to postpone one of its promised features (messages in the cloud) for nearly an entire year after the initial release of the software and released it just a couple of days before the next WWDC event where iOS 12 was announced.

WWDC is for developers. So they can get help directly from Apple, and hear about what’s coming up, so they can start to contemplate how Apple’s planned features might interact, inform and inspire their own future features/products. It’s not the start of 3-3.5 months of work to get those features ready; they’ve been many months or even years in the making.

Apple will often say feature xx is planned for a later version of OS Y.0. They didn’t promise Apple Cash, Messages in the Cloud, AirPlay 2 or whatever other new feature someone wants—and they want it now, daddy—would be in the .0 release. Quite the contrary.

Features are ready when they’re ready. The alternative to needing some extra weeks or months to implement some feature isn’t holding that feature for 6, 8 or 10 months until next September’s .0 release. That would be crazy, simply incredibly disruptive. It’s not a viable way to schedule software feature rollouts.

Which is not to say that some features might not be delayed until next year’s .0 (or later). For every release cycle, there’s always the above the (cutoff) line and the below the line features from the must-do list. Everyone goes like hell to get the most important features in a releasable state. (Which of course doesn’t mean bug-free, but you do everything you can to make sure it’s showstopper-free... then you cross your fingers and pray.)

 

[Steve121178]

I’m glad, I got the impression when buying the iPad Pro I wouldn’t have to upgrade for another year and a half or two. of course the battery has taken a massive hit with iOS 13 and it already makes me wanna upgrade. When I first got the thing it was really crazy. Sucks iOS 13 destroyed a12 devices with their battery life.

My iPad Pro 10.5" with it's A10X runs like a champ with iOS 13 (clean install). Since installing iOS 13, any hit to battery life hasn't been noticeable at all. Again, with the clean install all my apps are freshly installed & set-up.

Maybe ipadOS 13.3 will add further optimisation and solve your issues, or maybe it will make things worse? If I were you I'd nuke my iPad and set-it up as-new and see if that resolves your issues.

And you don't "have" to upgrade just because Apple release a new model.

 

[lartola]

WWDC is for developers. So they can get help directly from Apple, and hear about what’s coming up, so they can start to contemplate how Apple’s planned features might interact, inform and inspire their own future features/products. It’s not the start of 3-3.5 months of work to get those features ready; they’ve been many months or even years in the making.

Apple will often say feature xx is planned for a later version of OS Y.0. They didn’t promise Apple Cash, Messages in the Cloud, AirPlay 2 or whatever other new feature someone wants—and they want it now, daddy—would be in the .0 release. Quite the contrary.

Features are ready when they’re ready. The alternative to needing some extra weeks or months to implement some feature isn’t holding that feature for 6, 8 or 10 months until next September’s .0 release. That would be crazy, simply incredibly disruptive. It’s not a viable way to schedule software feature rollouts.

Which is not to say that some features might not be delayed until next year’s .0 (or later). For every release cycle, there’s always the above the (cutoff) line and the below the line features from the must-do list. Everyone goes like hell to get the most important features in a releasable state. (Which of course doesn’t mean bug-free, but you do everything you can to make sure it’s showstopper-free... then you cross your fingers and pray.)

Yeah, WWDC is for developers, but Apple also uses the WWDC opening keynote to announce the yearly major software update. Thus, if there were no major software update on a given year, then having a WWDC event that year would make no sense. That’s why I say WWDC ought to be only every other year or whenever the next major update is coming. On the timing, I still think 3-3.5 months of developer and public beta testing is clearly not enough time to have a stable and fully featured OS. The beta period ought to be much longer than that, at least 6 months, even if it means having a new major update every other year instead of every year. Apple doesn’t need to release a new .0 software update every single year, nor do they need to release new iphones, ipads, etc every single year either. They’re too greedy and too stubborn.
[automerge]1572975600[/automerge]

I’m glad, I got the impression when buying the iPad Pro I wouldn’t have to upgrade for another year and a half or two. of course the battery has taken a massive hit with iOS 13 and it already makes me wanna upgrade. When I first got the thing it was really crazy. Sucks iOS 13 destroyed a12 devices with their battery life.

You might have a defective battery. I am running iOS 13.2 on my almost 2 year old 10.5” ipad pro and don’t see a significant difference in battery life with respect to iOS 11, which was what it shipped with, or iOS 12, which was its first major update, so it’s pretty surprising that iOS 13 would drain the battery on a newer iPad and not on an older one. It seems to me that it’s a hardware issue rather than the software update that’s causing the problem.