Sorry… got a little too excited and carried away for a minute Also going through this feeling right now.
View attachment 2214826
What are your predictions for iOS 18?
Sorry… got a little too excited and carried away for a minute Also going through this feeling right now.
View attachment 2214826
Is it about time to create a topic - iOS 18 Speculation Thread?😂What are your predictions for iOS 18?
Is it about time to create a topic - iOS 18 Speculation Thread?😂
I am getting ready to start iOS 25 speculation thread, why stop at 18. 😄Is it about time to create a topic - iOS 18 Speculation Thread?😂
I am getting ready to start iOS 25 speculation thread, why stop at 18. 😄
macOS icons transitioning in iOS 18. Back to the drawing board! 🎨✍️What are your predictions for iOS 18?
I wouldn’t completely write-off the possibility of the macOS icons transitioning to iOS 17 and iPadOS 17. Obviously I have no idea of how likely or unlikely it might be, but Apple has changed some app icons mid-update cycle before, so perhaps they still could in a future update within 17. 🤷🏼♂️. I would probably write-off improved app icon customization though, because that would likely have been covered in the keynote or preview, unless it will be improvements that make using the Shortcuts app method better, which is fairly possible.macOS icons transitioning in iOS 18. Back to the drawing board! 🎨✍️
I prefer the iOS ones, over the MacOS ones.macOS icons transitioning in iOS 18. Back to the drawing board! 🎨✍️
where did you read this?It looks like Apple will be rolling out some pretty big updates to the Shortcuts app, so maybe these updates will make the Shortcuts app method of app icon customization better?
Here’s a link to an article about it:where did you read this?
I think that’s a combination of trying to make lemonade from the lemons and the fact that iOS 17 is probably not going to present too many problems to users during the beta phase.
I posted the same thoughts. I serious doubt most people are paying that much attention to this dev site alternative versus just having their configured Apple devices utilize Public Betas until it shows up. There is a certain percentage that prefer to wait no matter how it's argued also.I’m surprised you’re sticking with this. No way this was a mistake or temporary, at least in the short run. We’re all thinking why bother now with public beta. The thing is many are just assuming the public beta program is going to remain the same as it always has been. That’s a big assumption, we just don’t know all the facts. We’ll see in a couple weeks
It was assumed thats why Apple removed the profiles. Now its quite clear they had other plans.I don't quite understand why Apple removed the profiles. It was supposed to be an action to prevent anyone from entering the developer program, and now it's even easier to enter haha
I am one of those who have had a free developer account for years, and I had never seen the ipsw files of the betas to download. Today I was able to download the one from beta 1 without problems.
and not only that, to my surprise, with 3utools on windows I was able to update my system with it, because apple was signing it, at least this morning if it did, I don't know if it was a mistake on their part or not.
All that remains is for iTunes to be updated to support iOS 17, which I hope will not take long.
Let me know that 3utools has not yet been officially supported for ios 17. I did it to test, and the process ended without problems, but it does not follow the normal steps. This is one more rendering issue in my opinion. However, I recommend not using it until they release the update where they officially add support for ios 17 in the program. last year they did it more or less for the second beta of ios 16, let's hope this year is the same.
One reason could be that folks have a choice to wait until Apple deems it stable enough to be "public" so if your settings are set to the public option, then THATS when Apple will release it to that channel and public setting will offer it. Some folks may not be comfortable with dev stage firmware. Thats a easy way for Apple to provide the firmware based on users comfort level or abilities.If this is not a mistake, then there is another question (not to you, generally), does it make any sense more for them to distinguish public and developer betas? This is practically now the same thing.
I’m surprised you’re sticking with this. No way this was a mistake or temporary, at least in the short run. We’re all thinking why bother now with public beta. The thing is many are just assuming the public beta program is going to remain the same as it always has been. That’s a big assumption, we just don’t know all the facts. We’ll see in a couple weeks
I'm sticking with this because there's no explanation for the Appleseed invites otherwise. And I know the Appleseed invites were sent because I got one. If they were just chucking it all, they never have sent those…or kept the public beta.
More often than not, the simplest explanation is the correct explanation. Here, its that they messed up but decided it was no big deal given the low impact nature of the update.
Agreed, Apple changed their documentation as well, including Developer Beta versions of the OS’s as privileges of the free Developer Account. Clearly this would have to be a rather big accident with lots of coincidental mistakes all happening at once. Or maybe Apple knows what they’re doing, and it’s not what some people expected. I think it’s pretty clear that Apple wants people with the free Developer Account to have access to the betas, and the moves people previously freaked out about and labeled as “Apple gatekeeping the Developer Betas behind a $99 a year paywall” were actually to make this easier for more people to have access to the betas.Agreed, the simplest solution in this case is exactly what Apple said and they’ve created a new two tier developer program. Where’s the proof they messed up? Because they did something unexpected? Sending the Appleseed invite isn’t proof because the public beta was announced during the keynote. You’re hypothesizing they went to all the trouble to create the new developer program but couldn’t be bothered to edit out the public beta announcement? Clearly Apples plans remain to be seen.
Anyway just my two cents
Thanks. Interesting for sure.Here’s a link to an article about it:
Apple redesigns its Shortcuts app in iOS 17 to be easier to use | TechCrunch
Apple is making its Shortcuts app simpler to use with iOS 17. The app will receive an updated user interface, making it easier to find Shortcuts as well as the actions a given app can perform.techcrunch.com
My issue is the lack of any sort of communication around this. I have a developer account and pay $99 a year for that.
Not one email to that account address mentioning the change? Knowing that 99% of the accounts most likely renew JUST before WWDC?
That’s just shady…
Except the Appleseed Program isn’t new. I’ve been a part of it for well over a decade.Exactly. And then they “inadvertently” sent out the Appleseed invites as well, touting “advanced” access that would not be needed if everyone was being admitted.
The far easier explanation is that this was an error, they realized it and that they would not be able to “unring the bell”. So they just rolled with it. Took 20 minutes for a comms person to gin up the language for the “new” program and Presto! here we are.
Everyone isn’t being admitted, people who have a free developer account with Apple are. Think whatever you want, but allowing people with the free developer account to run developer betas is consistent with Apple’s moves to make installing the developer betas easier (instead of having to use the profile system). Clearly that wasn’t a mistake or accident. I highly doubt that this is the result of several coincidental mistakes that all happened to happen simultaneously, and then like a helpless bystander, Apple just changed all of their documentation accordingly… If it was a mistake, Apple would have removed the option for free developer accounts to install it, and wouldn’t have bothered with re-working their documentation. You can believe what you want, but I find that position far harder to substantiate with the available information than just recognizing that Apple decided to change their beta program a bit this year, and since they already laid the groundwork for the developer betas to be more accessible, expand access to those with a free developer account as well…Exactly. And then they “inadvertently” sent out the Appleseed invites as well, touting “advanced” access that would not be needed if everyone was being admitted.
The far easier explanation is that this was an error, they realized it and that they would not be able to “unring the bell”. So they just rolled with it. Took 20 minutes for a comms person to gin up the language for the “new” program and Presto! here we are.
I think that actually the Appleseed invite might be the accident. Part of old mechanism and not disabled after the changes.Exactly. And then they “inadvertently” sent out the Appleseed invites as well, touting “advanced” access that would not be needed if everyone was being admitted.
The far easier explanation is that this was an error, they realized it and that they would not be able to “unring the bell”. So they just rolled with it. Took 20 minutes for a comms person to gin up the language for the “new” program and Presto! here we are.
I’ve had a paid dev account for roughly 15 years and have been receiving Appleseed Invite emails every year.I think that actually the Appleseed invite might be the accident. Part of old mechanism and not disabled after the changes.
The general public that join the public beta might not be aware, or want to utilise, the newly free dev beta access.