That probably has some validity, but I still maintain that the majority of iPad users, folks that don't visit this forum or Apple sites in general, like iPadOS just fine.
Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Apple Criticized for 'Fundamentally Misguided' Approach to Stage Manager in iPadOS 16
- Thread starter MacRumors
- Start date
- Sort by reaction score
Doesn’t have to be MacOS. It has to enable users to use it for true multitasking. Give it pro apps. Give it something, anything to clearly allow users of this device to justify it at up to $2k+. Sure Apple wants to sell you two devices, but at the profit they’re making on iPad Pro M1, they could give a few features to utilize the SoC.
They lost the most talented visionary for UI UX that day. He was supposed to be the future CEO and who Jobs wanted as CEO as soon as Cook finished a transitional role as leader while Forstall learned the executive side more. It’s sad what happened then as Forstall was a threat to Cook. Anytime there’s a threat, the person at the top finds a reason to fire them. Forstall wasn’t given the time or resources to allow maps to compete with Google. It was absurd. And it was given to Forstall with such a short timeframe and little resources so Cook would have the opportunity to fire Forstall. Biggest mistake Apple Board has ever made to let that happen.
We don’t want iPadOS trash on powerful iPad Pro hardware. We want the power of macOS in tablet form.
For real. forstall was a major loss and a major eff up on Tim Cook’s part. He was too busy bending over for Jonny who could care less about a good product but rather the aesthetic. iOS ui took a turn for the worse so much so that iOS was so flat no one knew how to use 3D touch so they canned it
what exactly is true multitasking?
For iPadOS 16, M1 iPad users have features to take advantage of the chip.
I completely agree with Federico Viticci on this one. This is one of the massive pitfalls of the annual release cycle. Leave the new versions of iOS and iPadOS and macOS in the oven until they're good and ready. Rushing something this substantial seems...foolhardy.
They should figure out how iPadOS is to mature out of its iOS roots and whether that experience will be across all of the iPad models or just the larger ones (excluding maybe the low-end iPad). And if just the larger ones, they ought to figure out what the software/UI identity of the iPad mini and lower-end iPad is. Maybe those two go back to using "iOS" where "iPadOS" is reserved for the higher-end iPads that are geared towards being able to do more by virtue of having M-series SoCs rather than A-series SoCs.
They should figure out how iPadOS is to mature out of its iOS roots and whether that experience will be across all of the iPad models or just the larger ones (excluding maybe the low-end iPad). And if just the larger ones, they ought to figure out what the software/UI identity of the iPad mini and lower-end iPad is. Maybe those two go back to using "iOS" where "iPadOS" is reserved for the higher-end iPads that are geared towards being able to do more by virtue of having M-series SoCs rather than A-series SoCs.
Stage Manager is imperfect. However – having used it for weeks – it’s a huge improvement on what we have. And that should be the standard for release. Problems insignificant to most like these can be fixed later.
Last edited:
I’m glad not being only one to see that the proposed solution is a waste in display real state. Insult to injury … 4 ways to manage windows … geezz.
There are so many other things in iPad OS that looks and feels broken … in particular mouse and keyboard support, why doesnt it work the same way as macOS? As well as the Files.
There are so many other things in iPad OS that looks and feels broken … in particular mouse and keyboard support, why doesnt it work the same way as macOS? As well as the Files.
I love how everyone is saying that they shouldn’t rush the release. I don’t think they have announced a release date, so I’m sure it will be released when it’s ready. I’m sure we will hear more about the release date in the October hardware announcement, if there will be one.
Sounds like that’s precisely what he is trying to do by getting employees back in the office, rather than continue to offer WFH indefinitely.
Choice is good. I’m sure the way you manage windows is not the same as everyone else, and that’s a good thing. People use to bash the Mac OS for not having enough options to do this or that. Now that we are starting to have multiple options, people are crying out loud that we have so many! Apple really is damned if they do and damned if they don’t.
... an absolute piece of dog feces. And I smell Apple politics, not technical limitations, for its implementation v. traditional UI windowing.
choice is good, I just think that at least on Mac, Stage Manager in it's current form with with yet another GUI element is not an elegant solution at all and means just additional unnecessary clutter.
If they incorporated some of it's niceties into the Dock, or Mission Control / Spaces, i guess most Mac users here wouldn't complain as much. At least i wouldn't, if done properly
It’s in ”beta.” And there’s already rumors of iPadOS 16 being released later than iOS 16 (October/November), clearly Apple intentions is waiting until it’s good and ready.
Well, that’s the point of releasing M1 specific features with iPadOS 16. The problem is… critics don’t care for those M1 specific features, all they want is macOS on an iPad. When clearly Apple has stated they are two separate devices.
Wow, you are so spot on! I don't think many people realize how utterly profound this proposal is! What a huge difference in development quality if they weren't racing every year to drop a whole-number update just for the sake of dropping a whole-number update. Why not just take the time to develop great features and drop those features in major point updates.
I'm all for the user beta cycle feedback loop...it's important and can (should) lead to better software in the end.
But, this sounds like a simple list of bugs/issues. How do bugs equate to "...design decisions built into Stage Manager are "fundamentally misguided"?
Seems a bit much.
But, this sounds like a simple list of bugs/issues. How do bugs equate to "...design decisions built into Stage Manager are "fundamentally misguided"?
Seems a bit much.
I don't think people understand what Scott did wrong.
Apple and Google had an entire year left in their iPhone Google Maps contract.
They could've delayed the launch of Apple Maps an entire year to work out the issues.
They could've waited until iOS7 to launch it.
Apple had over a year left on Google Maps contract, Google scrambling to build iOS app
The Verge is about technology and how it makes us feel. Founded in 2011, we offer our audience everything from breaking news to reviews to award-winning features and investigations, on our site, in video, and in podcasts.
www.theverge.com
And when it actually got people in danger, he refused to take responsibility.
Apple Maps' Six Most Epic Fails
see photostheamazingios6maps.tumblr.comClick for full photo gallery: Those Terrible iOS 6 Maps Apple's (AAPL) iPhone 5 includes two huge flaws that Steve Jobs would never have sanctioned. As I posted September 24, one of them is a new connector that forced one iPhone owner to spend $1,300 to...
www.forbes.com
This wasn't a tiny issue, it was a big, big issue.
If he refused to apologize for a possibly very dangerous mapping solution, imagine how he would've acted if there were bigger issues later.
Also, lets not forget that when Scott was fired, the rest of the company literally celebrated.
They hated "HATED" him.
This was not a Steve Jobs situation where the guy was difficult to work with, but at the end of the day he still got the job done, and he was admired by his employees.
This was a situation where other people at Apple didn't like him, didn't respect him, and celebrated when he was fired.
Former Apple SVP calls Forstall firing "deserved and justified"
Father of the iPod had his own run-ins with Forstall during iPhone development. Read the whole story
arstechnica.com
Forstall’s exit from Apple: Conflict with execs, “jubilation” from employees
Apple employees taken by surprise at sudden departure.
arstechnica.com
If Steve wanted him as CEO, he would've appointed him as CEO.
But Steve was smart, and new Scott as CEO would've been a disaster waiting to happen.
And by the way, I think the versions of iOS and Mac OS X under Scott were absolutely brilliant.
Doesn't mean I think he shouldn't have been let go.
Also, interesting to note that NO OTHER TECH COMPANIES (Besides Snapchat) have gotten Scott to work for them.
That has to say something.
If he was truly the next Steve Jobs, he would've had the ambition to go work for another company, or create his own.
Nothing stopping him, but he didn't.
I know its easy to look back on "The old Apple" and think that they were actually a lot better, but the truth is, they've always had issues.
The earliest versions of OS X were *not* great main machine OS's, the first iPod and iPhones were very flawed, their OS's have always been riddled with bugs.
They're just a lot bigger now because Apple themselves is bigger.
There's more Macs, there's more iPhones, there's more users, so when there's bugs, they seem a lot bigger than they would've 10 years ago.
But go read old MR threads and you'll see that not much has changed.
Every OS has had people saying it was "Not ready for release", every new product is picked apart for every little tiny issue, etc.
Last edited:
And yet ever since Cook & Craig threw Forstall under the bus iOS & MacOSX have been plagued & riddled with bugs, incomplete or outright missing features and went from a "Best In Class" to "Worst In Class" state. There's a reason everyone waits til the .1 release (and later, if at all) to upgrade.I don't think people understand what Scott did wrong.
Apple and Google had an entire year left in their iPhone Google Maps contract.
They could've delayed the launch of Apple Maps an entire year to work out the issues.
They could've waited until iOS7 to launch it.
But, because of Scott, they rushed it out early.Apple had over a year left on Google Maps contract, Google scrambling to build iOS app
The Verge is about technology and how it makes us feel. Founded in 2011, we offer our audience everything from breaking news to reviews to award-winning features and investigations, on our site, in video, and in podcasts.
And when it actually got people in danger, he refused to take responsibility.
That's not okay.Apple Maps' Six Most Epic Fails
see photostheamazingios6maps.tumblr.comClick for full photo gallery: Those Terrible iOS 6 Maps Apple's (AAPL) iPhone 5 includes two huge flaws that Steve Jobs would never have sanctioned. As I posted September 24, one of them is a new connector that forced one iPhone owner to spend $1,300 to...
This wasn't a tiny issue, it was a big, big issue.
If he refused to apologize for a possibly very dangerous mapping solution, imagine how he would've acted if there were bigger issues later.
Also, lets not forget that when Scott was fired, the rest of the company literally celebrated.
They hated "HATED" him.
This was not a Steve Jobs situation where the guy was difficult to work with, but at the end of the day he still got the job done, and he was admired by his employees.
This was a situation where other people at Apple didn't like him, didn't respect him, and celebrated when he was fired.
Former Apple SVP calls Forstall firing "deserved and justified"
Father of the iPod had his own run-ins with Forstall during iPhone development. Read the whole storyHe sounds like a dude who was in way over his head, hated by most of his employees, and refused to take responsibilities for his mistakes.Forstall’s exit from Apple: Conflict with execs, “jubilation” from employees
Apple employees taken by surprise at sudden departure.
If Steve wanted him as CEO, he would've appointed him as CEO.
But Steve was smart, and new Scott as CEO would've been a disaster waiting to happen.
And by the way, I think the versions of iOS and Mac OS X under Scott were absolutely brilliant.
Doesn't mean I think he shouldn't have been let go.
Also, interesting to note that NO OTHER TECH COMPANIES (Besides Snapchat) have gotten Scott to work for them.
That has to say something.
If he was truly the next Steve Jobs, he would've had the ambition to go work for another company, or create his own.
Nothing stopping him, but he didn't.
I know its easy to look back on "The old Apple" and think that they were actually a lot better, but the truth is, they've always had issues.
The earliest versions of OS X were *not* great main machine OS's, the first iPod and iPhones were very flawed, their OS's have always been riddled with bugs.
They're just a lot bigger now because Apple themselves is bigger.
There's more Macs, there's more iPhones, there's more users, so when there's bugs, they seem a lot bigger than they would've 10 years ago.
But go read old MR threads and you'll see that not much has changed.
Every OS has had people saying it was "Not ready for release", every new product is picked apart for every little tiny issue, etc.
I vividly remember the days when Apple fans would routinely ridicule Microsoft for less.
My understanding was that Scott Forstall was forced to leave because he didn’t get along with the other Apple executives. So in this context, it didn’t matter how talented he was. He represented a net detriment to the long term success of the company.