Just installed it myself and runs very smoothly. Also the changes in Safari are good especially interactive form validation.
Apple releases iOS 10.3
41–50 of 103 posts
Re: Apple releases iOS 10.3
#42Just updated all my devices and I must admit that things feel snappier, even the 5.
Re: Apple releases iOS 10.3
#43Earlier quoted context omitted.
That's untrue. You can upgrade to a newer release version if there is one. (source: just did this today with 10.3) You only need to restore if you want to downgrade to a release version when you are on a later beta.
I have a device that I unregistered from the beta's and it never picked up a newer version, I had to manually restore it.
I upgraded to beta 7 then it let me upgrade to 10.3. Since I was initially in the beta, I probably couldn't make the jump to the GM directly.
Re: Apple releases iOS 10.3
#44Earlier quoted context omitted.
>ratings reset after every app update. What's the reasoning behind this? On Android, reviews for prior versions have a "This review was left for a previous version." banner at the top of them, but the star aggregates are all still there. How do apps keep reviews if they're wiped out every time an app updates?
There are two views when looking at ratings in the iOS App Store: Current version All versions It defaults to "Current version"
This is true, and also, when searching the app store the star ratings displayed next to each app are based on the "current version", so if an app is recently released it might say "0 reviews" even though it previously had thousands.
Re: Apple releases iOS 10.3
#45Earlier quoted context omitted.
Rolling it out first on iOS at all doesn't seem like the right approach. If I were somehow in charge of it, I imagine I'd want to do it like: 1) ship it as officially supported on the Mac, but off by default. 2) a year or two later, ship it as officially supported on the Mac, on by default, but still allow HFS+ as an option. 3) A year or two after that, if all has gone well, then introduce it into iOS (where presumab…
> If I were somehow in charge of it, I imagine I'd want to do it like: 1) ship it as officially supported on the Mac, but off by default. 2) a year or two later, ship it as officially supported on the Mac, on by default, but still allow HFS+ as an option. 3) A year or two after that, if all has gone well, then introduce it into iOS (where presumably it's not reasonable to make it optional The plan doesn't make much s…
3-5 years seems to be pretty typical for a filesystem to go from merely available to being battle tested enough to use without thinking about it. Bugs could destroy people's data (and the cloud won't necessarily help if the bugs corrupt data rather than erase it). What's the hurry?
Re: Apple releases iOS 10.3
#46Earlier quoted context omitted.
Initially, I was thinking the same thing. Given how fast the average Apple consumer updates to major iOS releases, I imagine that rolling it out over a point release is actually part of the plan. Presumably, if something does go wrong on the individual level, the support burden on the genius bars will be lower (since major iOS releases have traditionally come alongside hardware releases), and if a major bug is found,…
Rolling it out first on iOS at all doesn't seem like the right approach. If I were somehow in charge of it, I imagine I'd want to do it like: 1) ship it as officially supported on the Mac, but off by default. 2) a year or two later, ship it as officially supported on the Mac, on by default, but still allow HFS+ as an option. 3) A year or two after that, if all has gone well, then introduce it into iOS (where presumab…
iOS has always used case-sensitive HFS, while macs usually need case-insensitive HFS. Since it looks like APFS will drop support for the case-insensitive file system mode, it makes sense to do the forced upgrade on the system that already uses a case-sensitive file system (= iOS).
Plus, it's more straightforward recovering from a broken FS upgrade on iOS since many customers will have iCloud backups enabled, or at least their data stored on iCloud drive, while a mac filled to the brim with all sorts of strange applications and files spread all over the filesystem, likely never been backed up properly, is a tougher call.
Re: Apple releases iOS 10.3
#47Changing filesystem for billions of phones in a point release? That doesn't sound fun.
Why would doing it at the same time as major changes to every other part of the software be better?
Seriously, for a major change in the underlying system, surely it's better to do that along with as few other fundamental changes as possible?
Re: Apple releases iOS 10.3
#48Earlier quoted context omitted.
That deals with responding to reviews of your app, not an ability to leave a review for iOS itself. Either way, I don't think the average consumer will understand that they've lost data because of a bug in a new filesystem. And if you are an app with appreciable market share and something goes wrong, I doubt one would be able to mitigate a crush of negative reviews.
If you're an app with a large marketshare, the responsible thing would be to do testing with the betas to search out potential bugs. Doesn't cover all instances, but should help with any MAJOR bugs that would come up.
You only get the level of engineering investment that somebody is willing to pay for.
Re: Apple releases iOS 10.3
#49Earlier quoted context omitted.
There are two views when looking at ratings in the iOS App Store: Current version All versions It defaults to "Current version"
This is true, and also, when searching the app store the star ratings displayed next to each app are based on the "current version", so if an app is recently released it might say "0 reviews" even though it previously had thousands.
I guess as a developer this approach is useful if your first version is bug ridden, gets terrible reviews and you quickly push an update that fixes them all. Your product is doomed. Maybe after 5 updates or something to an app it should show the 'all ratings' as defaults but before that show 'current version'.
Re: Apple releases iOS 10.3
#50Earlier quoted context omitted.
That's untrue. You can upgrade to a newer release version if there is one. (source: just did this today with 10.3) You only need to restore if you want to downgrade to a release version when you are on a later beta.
I have a device that I unregistered from the beta's and it never picked up a newer version, I had to manually restore it.
I had the same issue but a manual reinstall wasn't necessary. I believe the problem was that in the developer > profiles menu there is a certificate for beta updates that needs removed. Something along those lines.