Yes, this! Apple's new mode of operation. I never recommend to friends and family that they update to any new release until after several .x releases. I am still not recommending Catalina to anyone. There are just too many bugs that Apple apparently does not care about. And too many people that just use Apple devices for basic things and then sing Apple's praise.
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.
Developers Frustrated at Apple for Just One Day's Notice to Submit Apps Ahead of iOS 14 Release Today
- Thread starter MacRumors
- Start date
- Sort by reaction score
Yes, this! Apple's new mode of operation. I never recommend to friends and family that they update to any new release until after several .x releases. I am still not recommending Catalina to anyone. There are just too many bugs that Apple apparently does not care about. And too many people that just use Apple devices for basic things and then sing Apple's praise.
Everyone saying "tHeY HaD The wHOlE suMMeR ThO" clearly hasn't developed an app while on beta software.
Last edited by a moderator:
They are neither developers not power users instead they may be just stock holders
Yep, your right about that. It's not the App that is hard, it is dealing with Apple, Apple's buggy development tools, Apple's buggy never fixed APIs, and Apple's nanny oversight thats hard. It took Apple 4 years to finally figure out that the original iCloud API did not and would not ever work without tons of custom code to work around the issues.
Imagine you are running a company and you employ an engineering team. It's quite an expense, part of that team works on iOS - maybe they even have some QA. Imagine that those who are responsible for iOS know that it'll be updated a major version once a year around this time, then imagine scheduling around that.
Imagine having customers, signed contracts for deliverables, existing schedules, roadmaps, regular issues, etc.
This isn't a dev sitting in their mom's basement ignoring the writing on the wall, this is multimillion dollar companies having a wrench thrown into their engineering organization and then having to have the same org output something in some cases, in a rushed fashion, for a new tech, to mission critical users, in less than 24 hours.
I would expect these companies to be able to pivot when necessary. None of their apps worked with iOS14 from day one. And they only started pushing patches about two weeks ago to fix them.
And it is the reason that Apple gets away with letting their quality sink so low. If all you do is tweet, then you be really happy with Apple products.
Not sure why everyone is complaining.
(1). Knowing how buggy new updates tend to be, wouldn't you want to delay by a month before changing the OS???
(2). The month gives developers some time too, not a whole bunch for any eager beavers (I'm Canadian) out there but those of you who decide to jump ship to 14 may realize that the ship wasn't actually sinking and it was all a false alarm and you threw your luggage off the ship, pushed the kids and older people off the life raft, and went first. So too dang bad. Bunch of whiners everywhere.
(1). Knowing how buggy new updates tend to be, wouldn't you want to delay by a month before changing the OS???
(2). The month gives developers some time too, not a whole bunch for any eager beavers (I'm Canadian) out there but those of you who decide to jump ship to 14 may realize that the ship wasn't actually sinking and it was all a false alarm and you threw your luggage off the ship, pushed the kids and older people off the life raft, and went first. So too dang bad. Bunch of whiners everywhere.
Any developer caught off guard by this release only has himself/herself to blame. They had plenty of time to work with the betas and Apple announced yesterday’s event weeks ago. With the increase of frequency of beta releases, it was OBVIOUS that the full release was going to happen at the event yesterday. If you are a developer and weren’t ready, suck it up and admit it’s your own fault.
The comments on this thread are one of many reasons I have little hope for humanity. The personal attacks over this topic - I’m amazed everyday. It’s not about having a “thick skin”, decency and respect are out the window. I wouldn’t speak to a stranger in person the way some here address others online. SMH
So many whiners about the notice. Apple doesn’t care about you and it’s not like this timing is any kind of a surprise.
If you don’t understand why developers are complaining, reading the thread might be a good start for you.
How do you do that? We have a schedule, work in progress, customer responsibilities, we have to get the code out that we were already working on out
We *knew* we had time between GM & release... that is what changed. Apple only gave us the final RC a day before it was released, meaning organizations would have had to have known to make a different choice earlier in the release cycle, or they could of just told us a week ago.
It could have been handled in many different ways, all of them more ideal than this.
Sorry, how do I submit apps with no stable toolset to update with?
Yes, yes it is. Have you ever seen GM/RC tools released on one day, and then the final release the next day? While the tool used to work on it isn't even released yet?
It doesn't quite work like that.
We had all summer long to fix the bugs, this is true. But we need a final version of Xcode 12 to compile the apps.
Xcode 12 hasn't been released officially on the App Store, but it was released yesterday as a GM. So developers have to download it (a few gigabytes), unzip it (a good 30 min), compile their app, submit it to Apple (can take 15 minutes, or 2 hours depending on the update), and Apple would have to approve it overnight, and users also have to update their apps within today for the experience to be completely bug-free and seamless on iOS 14.
We had no idea when GM would be released though. And you are not going to any major work in one week which is all we ever get. The only thing that is majorly getting messed up is the final QA time. Which I understand is very important.
[automerge]1600280277[/automerge]
It's not like you are going to fix your app in a week if it doesn't work in 14.
No, the devs should be a bit upset and I understand that. I'm not sure why there seem to be non-devs griping or have no pity!
We do in fact traditionally take advantage of that time, whats' the alternative? To fix things in circles as Apple evolves iOS 14? That would mean we update our app with every beta release, while maintaining current work and planning for the future. We can't afford to do that and stay competitive, there's no way to slice it to make it ok, Apple F*d us and by doing so, our users. Mine happen to be doctors and nurses that use the app I work on to save people's lives. We have no issue pivoting and delivering, we have an issue with a platform we pay, that's a monopoly, keeping us in the dark in a way that can literally have an impact on someone's life. They are now the weak link in us talking to our customers, it's not a good position to be in.
And we fixed our issues in a night, because we know what we're doing and have a plan but that's not the point. The point is that Apple knew this would happen and didn't care to alleviate it, probably because they hope to do it all themselves one day anyway.