Non-devs posting opinions in this thread === non-taxpaying voters.
Well they can only submit their apps once the golden master is released, which was yesterday, and things don’t always go so smoothly with the final build. Sometimes changes in the iOS code break the app and they have to fix it before release. Usually they’d have 7-10 days to make these changes between the golden master and public release, but now they have less than 24 hours. Sure they can wait an extra week before submitting it, but apps that release their updates on the same day as iOS usually have more publicity, have their apps featured on the App Store homepage, etc.
/s I assume? If so ignore the rest of my post, if not just know that's not how it works. Developers can test reliably only against the GM seed which literally dropped yesterday. Also Apples approval process isn't instant, so many apps won't work on day one.
Ok, so I read more of the thread and it's a timing issue in terms of releasing updates via various builds. I still want someone to explain why we have a Beta process in the first place. The whole point of Beta is to test the IOS program for bugs, provide feedback, and start working on app updates while the beta process is in motion. Apple even says don't download this on your main phone because it might do damage to the main phone. Basically, from the day WWDC happened to now, developers had some sort of program for the new IOS update. I would think it's like writing a semester long paper for school. You get the assignment on day one, the teachers tells you when it's due, and unless you procrastinate, you are working on that paper the entire semester and the good students would try to get it done early so they don't need to worry about rushing it with a day or two left.
Not necessarily. I work IT in a school district. We hold back on iPadOS upgrades (even point releases) a few weeks to make sure they work with our systems. Yes, there are betas, but betas aren't always the same as the released versions. Plus, there may be serious bugs with the release.Customers will be installing on day 1, right?
Which is fine if your app is a free fart machine.Seems like you still aren't understanding it. If I set up iOS14 beta 1 and my phone and found that it crashes my app, I had the whole summer to fix that issue - you're right about that part.
But lets say I fixed the issue two days after discovering it, I can't do anything with that new app version. I can just put it in a box and let it sit there until I'm allowed to submit iOS 14 apps. So even though I instantly fixed the problem, Apple wasn't accepting my new app until yesterday. With the approval process, it likely wont be in the store for an extended time. So anyone who updates to iOS 14 within the next couple days will still get the broken version of my app because I wasn't allowed to upload the fixed version until just now (regardless of the fact that I actually made the fixes 2 months ago).
Gotcha. Honestly, sounds like a change in deadline that many employees face at their jobs (not just developers). It sucks but it happens. I'm sure many devs will have to or have pulled overnighters. I know it has happened to me many times in my field (real estate). Doesn't mean what Apple did was right though.
You haven't read anything in this thread, have you?Who gives a toss. If your app can’t work after 8 betas worth of development when the GM was practically imminent, the app is probably garbage.
What Apple did was wrong, but still, what can you do with your garbage app in seven days that you can’t do in 24 hours when your app was garbage from the get go?
So what were all those betas for?
Who gives a toss. If your app can’t work after 8 betas worth of development when the GM was practically imminent, the app is probably garbage.
What Apple did was wrong, but still, what can you do with your garbage app in seven days that you can’t do in 24 hours when your app was garbage from the get go?
Like I said, customers will be installing on day 1, right?Not necessarily. I work IT in a school district. We hold back on iPadOS upgrades (even point releases) a few weeks to make sure they work with our systems. Yes, there are betas, but betas aren't always the same as the released versions. Plus, there may be serious bugs with the release.
As for apps, many, if not most, aren't work critical. Sure it's nice to have access to all the latest features, but they're not always necessary
Two of our apps at work broke between the last beta and yesterdays GMs, so it's not accurate to claim that people have had a week.
Playing Devil’s Advocate... I’d genuinely like to know.You know what was garbage? Your post....
Why do you feel the need to attack developers?
Gotcha. Honestly, sounds like a change in deadline that many employees face at their jobs (not just developers). It sucks but it happens. I'm sure many devs will have to or have pulled overnighters. I know it has happened to me many times in my field (real estate). Doesn't mean what Apple did was right though. All signs and info from Devs suggest their should have been a longer period before the release of the GM to the public.
To this point, my fiancee installed iOS 13 on release day last year, Blackberry Work had not been updated to support it. She had to go 4 days before it was updated. Created a pretty big headache.Like I said, customers will be installing on day 1, right?
What you may or may not do at your school isn’t particularly relevant. There are over a billion iPhones and another 300+ million iPads in the installed base.
Isn’t app development the reason they have beta testing periods?
Well, that is indeed unfortunate for developers and I deeply appreciate their hard workings in this process. However, as a consumer, I have a right to use and enjoy all the features the latest public release of system software (iOS/iPadOS 14 in this case) can offer. And at the same time, developers also have to make sure their applications to be optimized and work as expected under the most recent public release. I sympathize with developers for testing apps in such a short time frame and understand that Apple should take some or major responsibilities in this.Except it doesn't work that way. We always had a week to 10 days to test our apps with the final build.
You also can't be submitting to the store with beta builds of Xcode. We only got the final version of Xcode yesterday and when this happens review times always go way up. So if our app does not work on iOS 14 it could be days to over a week before we can submit a build with iOS 14 that corrects those issues.
Playing Devil’s Advocate... I’d genuinely like to know.