What's happening is: the operator buttons have an animation on them, and they don't register inputs while the animation is running. The animation is pretty long, so it's quite easy to tap an operator, tap a number, then tap the operator again and have your input be missed.
Conveniently, this should be a trivial fix. Just abort the animation when a second input is received while it's still running and register the touch. (Or, lazily, make the animations a lot faster.)
Edit: I got operator/operand mixed up while writing this. :P
What needs to happen here is pressing the button needs to immediately register the press elsewhere in the code. The UI animations and the button tap should be decoupled entirely.
Then the user can tap away as fast as their heart desires and only the animations are going to continue on. That’s an easy problem to solve... by doing as you say and aborting them or shortening them.
But you should NEVER have UI animations and effects block your logic path. They should be parallel operations not serial.
This goes well beyond UI design, and there are even physical analogs - for example, the crash of Turkish Airlines flight 981 in Paris could have been prevented if the device to prevent the cabin being pressurized if the cargo door was not properly closed had been operated by the door locking pins sliding home all the way, rather than by a side-linkage off the linkage that was supposed to drive in the pins.
But I feel my first suggestion was exactly what you're suggesting -- immediately register the input and apply the operator -- I just phrased it in terms of what happens to the animation.
Also! I certainly feel there are times when letting an animation block your logic is valid. That would be any time when an animation has the UI in a potentially confusing state, such that the meaning of an input is ambiguous. (You should avoid these states as much as possible, of course. And this sort of button-flash comes nowhere even near that category.)
You don’t want the switch activated until it’s all the way left or right.
The buffer in question is, for a tty, a driver-level buffer that holds on to the data until something reads it. If a command doesn't read it (which things like apt-get update don't) then it'll get read as the next command.
Of course, most terminals these days are ptys accessed via emulators, so the buffer is actually part of the emulator, but the same idea applies.
Soo.. When he left his desk, I went in and hit SHIFT-SETUP, turned the audible BEL off in the VT-100 setup menu and enjoyed the silence.
When I came back in the office the next day, there was a technician from Digital with the terminal in what looked like 100 pieces on the desk trying to "fix" it. He was pretty upset when he realized it wasn't the speaker and the setting was just turned off (why he didn't check that first, I'll never know). Needless to say as a teenager, I kept quiet about the whole thing.. until now..
You can link two commands together with the "AND IF" operator
sudo apt update && sudo apt upgrade
I always come back to the example of WhatsApp and how it took on SMS, IM, and emails and won. People claiming WhatsApp went in mobile first are getting it only partially right. WhatsApp defined itself as a replacement for SMS: No login passwords, no chat history, cross platform and that led to them being cheaper, better, faster, frictionless. Later added MMS-esque capabilities like media and then email-esque features like Groups with super nice execution on the UX front.
Similar thing for AMP pages: It just works and it is blazing fast.
US-centric competitors would only support iOS and Android, whereas WhatsApp was running on the hundreds of millions of 2003-2010 vintage Nokia/Samsung featurephones that were in daily use in India, Indonesia, Nigeria, etc.
That is also part of UX. When it comes to messaging apps, Snapchat is one extreme of the spectrum -- iPhone-focused, cryptic UI, teen-oriented, majority of users in USA -- and WhatsApp is the very opposite. Both are successful examples of UX focus.
These things go hand-in-hand by the way. And that's not a complaint, it's just funny how "only teens bother to figure this out" can be an honest-to-goodness feature under specific circumstances. Especially if you (basically) need to be "introduced" to a program and all of its quirks through your friends.
It is already blazing fast with only HTML and CSS, as the Web was designed to be.
Only mobile, the web version is shitty because it hosts a web server on your phone which is unreliable. And even with that you can only access the web version from one computer and it does not work well on tablets.
Lag doesn't necessarily have anything to do with performance. I really don't think people are talking about performance at all. No one would seriously think that a modern smartphone could be dwarfed by a 35 year old calculator in terms of raw performance.
One reason I moved from Windows phone was the massive delay in switching apps.
Now on iPhone the animations are annoying, yes, but they are at least consistent in length, meaning I expect them and know how long to take a (tiny) pause. I know some work is happening that’s being disguised and that’s why they can’t (all) be turned off.
It also takes about 20 seconds to disable all animations in Windows, which makes it feel as snappy as XFCE (even on my 5-year-old machine).
For what I do now (Office, email, programming using IDE hooked into Docker containers), it really doesn't hinder me to be on a non-*nix OS.
(The last time I brushed-but-didn't-quite-hit some interesting info was in https://news.ycombinator.com/item?id=15136939, which I quoted (very tangentially, as a footnote) in https://news.ycombinator.com/item?id=15153262.)
The numbers have the same animation, but it's both shorter and interruptible, so the people who built the app seem perfectly aware of the problem and how to "fix it".
This seems deliberate, as if somebody figured that, while it's a legitimate use case to rapidly tap digits to input a longer number, tapping an operator multiple times is likelier to be an input error, so they purposefully block it. Clearly a mis-feature, but a feature nonetheless, rather than a bug.
trivial to fix the bug in the calculator app. not trivial to deploy that fix. this would be a full system update, right?
But, also conveniently, iOS 11.1 is in beta at the moment. They just released beta 5 today, so it's not like they couldn't slip a fix for this in before the final release if they wanted to.
Whether they will or not, well...
That means updates still need to be a part of a system update.
I haven’t measured data usage, but I suspect this means that removing Calculator’s icon actually removes its code from the system. If that is true, it is potentially upgradeable independent of the iOS system, at least from a technical perspective.
I suspect Apple’s QA and release processes cannot take advantage of this, though.
Re-enabling the app will basically restore the ROM version. You can then install updates from the store, which I think is basically a full install and the ROM version is ignored again, based on the consumed space of such apps.
The event loop is processing events during the animation. It is up to the programmer to decide if events are ignored or processed during animations because what that means depends on what you want to happen: is the animation interactive and reversible? Does tapping reset the animation or does it start animating to the new state from its existing state?
CoreAnimation does the work based on the policies you select (eg: interpolating between a half-complete animation and the new desired end state).
No they're not. The linked thread is literally discussing what you describe as "the actual issue".
> The actual issue is that some developer at Apple screwed up their animation configuration when implementing the calculator redesign, and nobody tested adding more than two numbers together quickly. Multiple failures, none involving system performance.
Unless you were talking about the discussion here on HN? I haven't read most of the discussion here yet. I just wanted to point out that the Redditors get it right just fine, since there's a lot of unheeded shitting on Reddit on HN (has always been the case and I think it's sad. HN has got its own community smells, but at least I hardly ever see Reddit dumping on HN and when they do it's in good natured fun poking and not vitriol like here) (btw your remark wasn't vitriolic, but others are very much so).
The numbers are the operands.
I can't come up with a good UX reason for that restriction, so either it's an oversight or a technical limitation.
If they really didn't test at any statistically significant extent, people would really notice it.
Thing is, bugs happen, and no amount of tests will ever squash them completely.
Especially for some small insignificant part of the OS, assigned to 1 or 2 people at most like the calculator.
Asshole, but perfection requires assholes. Apple is regressing. Their products are too expensive to tolerate regression.
Let's just be frank: there were TONS of BS issues like that under Jobs all the time, regardless of whether he was obsessive about this or that particular app.
It's just so wrong at so many levels, I don't even know where to start.
I'll leave a link to this video: https://www.ted.com/talks/brian_goldman_doctors_make_mistake...
Lots of bugs and issues happened under Jobs, but this was the usual press BS.
The iPhone 4 went on to sell 50 millions of devices or so with that antenna and nobody in the real world had much of an issue with it.
If only media worked that way and never discovered problems where they don't exist or are totally marginal...
By the same logic, if nobody listened any difference with $1000 "hi-fi cables" they wouldn't be buying them...
But the problem is probably not at developer level, it's higher ups who don't care about quality control, which permeate downwards.
In any case, I would be shocked if there was anyone, anywhere that thought: “you know, I would have put in the effort, but I knew even if I screwed up, no one would verbally abuse me, so why bother?”
Just my opinion, but I would reckon no software has ever been made better by verbal abuse. Jobs succeeded in spite of it, not because of it. Going on a tirade is something egomaniacs do when they can’t control their temper, not an effective motivational strategy.
Do you seriously think anyone would answer "yes i love getting yelled at"? If yes, then I'm done here. If no, then ask yourself why you asked that question. it's a rhetorical question to control your narrative, which has nothing to do with what GP said. GP never said it's a good thing to yell at others, and neither did I. You're the one who turned it into this narrative for the sake of your argument.
But then again, I'd never block user input to play an unnecessary animation on my own initiative, so I must have been doing that because my manager told me to do it, or because I wasn't given enough time to do the job properly. So if I got yelled at in that situation, I'd wait to see if I was fired, and quit if I was not. Management by loud, abrasive, dominance-displaying histrionics is not something I can work with, ever.
Every company gets one freebie, where I go above and beyond the call of duty to make the kind of software that I am proud to stand behind. If that effort is not rewarded or recognized, and explicitly encouraged to continue, I fall back into line and do exactly as I am told thenceforth--no more, no less. I won't offer my opinion unless it is requested, and I won't go looking for extra things to do to improve the code base. If that freebie is actually punished or reprimanded, I start looking for other jobs. What I have found is that few companies are interested in doing anything well, or even technically correct. They desire extremely consistent mediocrity. They don't want a hand-crafted hamburger made from fresh-ground chuck and crisp, juicy vegetables; they want a McDonald's hamburger with exactly two pickle slices and one pinch of minced onion.
Anyone that yells at a grill cook for making a gourmet burger instead of the McDonald's standard probably shouldn't be hiring trained chefs and assigning them to the grill. But worse, anyone that yells at their grill cook because they put a third pickle slice on the burger--an extra pickle that was asked for, or even demanded--probably should not be in charge of anything, much less a bunch of grill cooks.
Fear of getting yelled at is actually fear of having to navigate the awful interview process all over again, while pretending to care about my current job long enough for an offer to come in. I avoid doing my work badly mostly because I don't want to be a person who does bad work. If I ever do bad work, it's because I was told to do it that way--or maybe yelled at to do it that way--and I hate every shortcut and kludge, even as I am typing them into existence. At that point, I am already mentally out the door, only sticking around until that paycheck can be replaced by a check from somewhere else. Yelling is bad management, and bad management motivates me to leave.
Nobody is defending management which abuses employees for failing to meet quality standards. But yelling at employees is not the only way to indicate disapproval of work which does not meet quality standards, and the fact that Apple has not been maintaining quality standards is a black stain on current management that Steve Jobs never would have allowed in his company.
Apple shouldn't model Jobs's management style and go back to yelling at workers, but its entire corporate ethos depends on keeping Jobs's quality standards. If those standards are gone then Apple's brand will surely die.
Wait, wat? How?
And the bumpers aren't proof of anything except perhaps marketing; they could have just decided that the cost of giving everybody free bumpers was cheaper than any brand damage they might otherwise have sustained.
You wanted a totally original rephrase for a response to the exact same topic on a different subthread?
>Apple gave away free bumpers with the 4, so yes, it was an issue
Which few really used in the wild, so no, it wasn't.
My immediate thought was that Apple had liberally sprinkled wait() into the iOS 11 code base so that I'd feel like my ole A9 CPU just wasn't cutting it any more and I'd realize, as they do, it's time to upgrade.
Or... maybe they are running every key stroke through the new Azure-enabled Cray computers to better predict what I am going to type so that overall, my typing is more efficient and I'm actually spending less time typing...
Yeah. Yeah, that's it!
That was actually recently debunked by Futuremark https://www.futuremark.com/pressreleases/is-it-true-that-iph....
Important excerpts found at the bottom of the page:
> Our benchmarking data shows that, rather than intentionally degrading the performance of older models, Apple actually does a good job of supporting its older devices with regular updates that maintain a consistent level of performance across iOS versions.
> That said, there are some factors that might affect people's perception of performance after updating an older device with a newer version of iOS. An update might add new features that use more resources or require more processing power. New apps developed for the latest models might not run as smoothly on older devices. Conversely, apps designed for an earlier version of iOS might not take full advantage of optimizations in the latest version. And then there is always the psychological effect of knowing that there is a new and improved model available, which can make your own device seem outdated.
Does Apple sprinkle wait()? No. Does the system become more and more complex and Apple taking less time to optimize because it runs “fine” on the [latest - 1] hardware? Yes.
I'll help you a bit.
> > [...] Apple had liberally sprinkled wait() into the iOS 11 code base so that I'd feel like my ole A9 CPU just wasn't cutting it any more
From the article
> Are older iPhones being deliberately slowed? [...] maintain a consistent level of performance across iOS versions
Sure, as you snarkily remark, your CPU/GPU hasn't changed, but neither has the iOS version inherently made your phone slower. Apps on the other hand might be assuming more power nowadays, but that is a whole other question... Or, you could also just have read the end of my comment...
The real rebuttal of "slow" claims should be to look at the added features and security and discuss whether such trade-offs are worth the reduction in performance. For example, to make the user's data much more secure, Apple puts a lot of mechanisms behind XPC, which is inherently slower than mere API calls. These slow the system. Are they worth it, for the security benefit? That's the productive discussion we should be having.
But that is LITERALLY what people were accusing Apple of doing, actually slowing their devices to make them buy newer models. There might have been less conspiracy-esque claims, but jesting they were "sprinkling wait() calls in the code to make me upgrade" is not in that category - so I disagree with your claim that people weren't meaning that.
Anyways, this discussion has derailed, so I'm just gonna leave it at that.
THIS! My exact experience and sentiment. The lag frustrates me every time I open almost any app (and then I get frustrated with myself for letting myself succumb to such a first-world-problem)
Is there any recourse? Can we disable some animations or other unnecessary features in settings?
Can we expect 11.0.4 or 11.1 to fix?
"Some reddit users claim that resetting their settings (Settings --> General ---> Reset --> Reset All Settings) fixed all of the app issues, while others have restored their devices and set it up as new to solve the problem. Others have backed up and restored and had better results."
And this when I have yet to restore from iCloud or restore an entire 25GB Music cache!
What's happening, Apple?
EDIT: Should probably mention it's called Reduce Motion.
Resetting all settings seems to have done the trick. But I am not 100% sure.
The typing on iOS 11 in all apps is absolutely abysmal. What the hell is going on?
The same that has happened for every iOS .0 release for YEARS.
They focus on showstoppers (P1) only then focus on usability (P2) during the next year's worth of point releases. Then iOS 12 will come along and the process repeats.
It would take an obsessive, aggressive, near manic product personality to stay on top of something that large and keep it running at an extremely high level of quality. Tim Cook isn't that leader (which pretty much everybody understood on day one).
Apple is seeing very serious problems across numerous aspects of their business, from product decisions to supply chain.
Every year it's always "Apple is dying" as they continue to siphon money from every industry they touch. They are about to push a tonne of users into a higher price point with the iPhone X. The Apple Watch is an unquestionable success. We are on the precipice of seeing an ARM based MacBook based on their incredible work with A-series chips. They are also strategically very well placed with their Health and AR initiatives.
Anyway look forward to your position in a few weeks when iOS 11.1 is released given the betas are looking pretty good.
Not that I spend any time looking at people's wrists, but you'd think if it was a massive success everyone would notice.
I wonder how much that has bolstered the amount of people using one.
It would be interesting to see the geographic distribution; I was in Delaware a two years ago and used mine to pay for my purchases at a Bookstore and everyone was quite surprised--they were unaware of the active Apple Pay feature on their own point of sales terminals.
The people wearing them aren't techie types at all which is why I'd guess the sentiment in tech circles is so negative on the watch's success. I think we're used to seeing our colleagues being the earlier adopters of gadgets like these, but the Apple watch early adopters include a diverse set of non-tech people.
Most of the Apple-using techie types I'm friends with have a Watch.
Although as a counterpoint, at $WORK, most of the techie types don't (but also don't use other Apple stuff.)
As a random example, yesterday I bought fast-food fried chicken for lunch. The woman who took my order was wearing an Apple Watch. The barista at my regular coffee shop wears one.
They're definitely showing up on non-tech people. I've also never seen a woman wearing a smartwatch that isn't an Apple Watch.
Starting around 2001, that last one got replaced by my mobile phone.
I'm not really seeing the use case for smart watches. But then again, I was never a fan of purses or fanny packs or any kind of jewelry either, and never understood fashion, so I'm probably never going to see the point of smart watches either. If I'm going to strap anything to my body all day, it has to be clearly useful for the entire duration, to overcome the discomfort and inconvenience. I'm just not seeing that yet in any of the available options. In every case, I'd rather put a wrist strap on my phone.
HOWEVER I am running the developer preview betas which are notorious for being UX janky and logging insane amounts of crap on every action the OS takes. Which probably explains it for me at least.
It sounds like an issue that a reset or reinstall may fix.
I'd be similarly pissed off like you if even my much older phone did that.
The time from wake to photo was ~2seconds (using the lockscreen short cut).
The time from wake to home screen photo app to photo was ~5 seconds.
I had to start the timer myself then go back to using the phone so I believe I could cut ~500ms.
Since I have Live Photo enabled, the 2-second shots actually have a few frames that are sub 2 seconds.
Going to the homescreen was accidental. In each attempt, I attempted to use the lock-screen camera shortcut.
As a whole, the experience using the iphone is too unpredictable to be reliable for quick reaction shots (< 3 seconds). A number of times I either: bypassed the lock screen, didnt get passed the lock screen, unlocked my phone to a different app, and on one occasion, the camera app paused for a few seconds before focusing.
Back in the 90s I decided we needed a real-time UX - hard real-time guarantees. I had no idea how to even start with this, especially as the only OSes I knew well were UNIX-like, none of which did real-time. There was QNX(?) but I didn’t have access to play with it.
So do we need an effort to make a new real-time phone OS? Kinda like the Firefox phone OS project but built on an OS that allows guarantees?
For a 3 year old phone, it's frustrating but still miles ahead of the last Android phone I kept for 18 months. It's still frustrating that the iOS update is basically forced on us instead of being an optional upgrade like on desktop. (Of course it's technically optionally, but the constant nag annoyance makes it effectively forced, imo.)
Also, I swear the rear-facing camera has lower color saturation and higher sensoe noise after the upgrade. I’d love to see A-B camera tests for iOS 10 and 11 on old hardware.
My latest annoyance is when I'm using the keyboard and it just visually freezes for several seconds. It appears locked-up, but it's really not. It's silently recording every button you press in anger, and finishes with the throwing of the entire buffer contents at you all at once, which, to add insult to injury, you now have to also delete.
I bought a very expensive phone that was unable to launch apps (50% of the time, when it did, it took several seconds) and unable to make calls (the receiving end would be mute and would not hear what I was saying).
The phone was bought on an official apple store and had one day of use. Problems persisted for over a week. Tried all the possible solutions. The only one that worked was downgrading to 10.
Edit: I don't mean CPU benchmarking which has been discussed elsewhere in this thread. More like usability testing, sequences of actions not invoking new OS features where possible, and also a second set of tests using new OS features because that's what most people's experience would be.
It takes literally zero planning to do a test now and then do another after the update.
I've found a few examples here:
These don't support the argument that devices are slower after updates.
Honestly I feel like the people in charge of iOS have stopped using the devices personally. I have no other explanation for so much annoying crap slipping through (ok, other than some idiot exec being in love with the animations, and shutting down any attempt to correct this behaviour, like what happened with Forstall's obsession with skeuomorphism).
>Calling the generator’s prepare() method puts the Taptic Engine in a prepared state. To preserve power, the Taptic Engine stays in this state for only a short period of time (on the order of seconds), or until you next trigger feedback.
My main problem is that if I simply want to do something on any iOS now as soon as I unlock it I'm blocked by pop ups for things like making a back up and buying more iCloud storage and upgrading to iOS 11 -- things I never intend to do. There's no way to switch these off either. And they happen constantly, multiple times a day.
Last time I used my iPad I dismissed a popup, opened up an app and the same pop up came a few minutes later completely interrupting me. I have no tolerance for these annoyances.
Samsung phones were complete trash back in the day with their bloated interface but I've since switched to a Note 8 and the experience has been very good. UI is very clean and the performance/features on the phone are outstanding.
The iPhone is a rather one size fits most device. If you don't want to go along with Apple's idea of how to use the device, you will be unhappy with it.
Right now I'm fighting the practically forced upgrading of a particular app for which the update will remove functionality. But in order to not update one app, I'm forced to manually update every other app individually. Which is about 40-50 updates a week that I have to approve.
Using the phone forces me to realize the extent to which I don't really own it. I'm just sort of renting services from it with an all-or-nothing set of features.
You have something really wrong when your smartphone can't open apps...
After one week I got tired of this shit and downgraded to iOS 10, which for now is working as expected. I really hope apple won't force me to update to iOS 11. (So here's what I did: I intentionally filled my phone space. Good luck fitting iOS' 1GB here).
Frustrated disappointed and utterly angry at Apple. This is definitely the last iPhone I'll own.
Anyway, whatever apple did or didn't do, worked. I upgraded to an 8 Plus and couldn't be happier.
I run in to others who have version 6 phones and have no problem, so I don't know why I'm an outlier. Part of it is probably my storage habits, I was almost always within 5-10% of capacity. Now I have 256gb version and am hoping I don't get near the limit so that this phone will last me 3 years.
Edit: to respond to another comment elsewhere in this thread, Apple also tests on all of the supported hardware when prepping iOS.
I'd try restoring my phone if I were you - that fixes these issues for a lot of people.
Which would affect the 2017 iPad also. Why introduce a new iPad with the A9 if you're going to limit the performance. Is it to get people to buy... what exactly? An iPad Pro? Why not simply ONLY make iPad Pros?
This line of reasoning is immature and beneath the type of discourse that should occur on any tech leaning site.
I really hope you're just being sarcastic and mocking everyone who really thinks this.
Edit: I, personally, have a 6S and it's fine. Of course I DFU and set up as new for new OSs. It's even better on 11.1 beta 5.
But this problem is not some stupid complaint coming from uninformed people. This calculator thing was a perfect symbolism for all this bullshit that's been going on since iOS 11 release because the bug is so easy to replicate, but there's much more going on than just this calculator bug.
Before I go on, note that I have the latest iOS installed, and I do iOS development. I'm not a clueless newbie.
Anyway here are some examples:
1. my iPhone apps crash 50% of the times when I bring them back from sleep.
2. Even the ones that DO load, takes around 8 seconds on average to start up. This includes Email and iMessage. Yes, I have to wait 8 seconds for my mail app and messages app to "boot up" before being able to check a message I just received. This is ridiculous. I have talked to several of my friends who have been experiencing the same thing.
3. I had to turn off animations. Otherwise I couldn't my screen will freeze when i try to type into imessage, etc. Remember, all of the above are happening WITHOUT the animation turned on.
4. I started getting emails from "No Sender" with empty content, couple of times a day. I'm just assuming this has something to do with some fucked internal clock (I have double checked and my iCal and preferences are correctly set) but who knows.
5. Yesterday I was trying to take a picture and opened the camera. And YES, I mean the native camera app that ships with iOS. I saw the camera UI launch, but there was no "camera". It was just a black screen. I've become accustomed to this type of lag in app loading so i waited for my camera to "boot up". It never did. The camera app was open and there were all the UI components, but it wasn't capturing anything. I have never seen anything like this before.
Please stop saying "haha it's funny how these idiots think some calculator problem means Apple's future is doomed" because last time something like this happened was when I switched from Windows to Mac.
This feels like Apple has crossed the Rubicon. The Steve Jobs era is officially over.
I think Android 8 has some flaws atm that are really kneecapping things. I had constant app crashes. Loading problems. All sorts of little things that seemed to be super buggy. Windows appearing behind other windows, adds not properly being put into their space. I went back to my iPhone 6s.
That said, you might have a better experience, those things might get fixed. I am sure they will be fixed both on iOS and Android. I am just saying, the latest and greatest on Android kind of sucks too.
Apple managed to make a smartphone unable to launch apps and make calls. Not sure if incompetence or malice. Regardless, I'm never looking back.
On iOS 10, I noticed, if I swipe the lock screen left and right really fast where it brings in the camera, it eventually gets stuck. Like half the screen is now black and nothing happens until I hit the reset button. This is reproducible. It seemed to me like a really weird little bug to have on maybe the most popular mobile OS on earth but brushed it off as me being anal about something not even Apple considers a problem. This calculator story is a bit of a waking call that Apple UX quality genuinely did get worse in recent years. It's little things that add up. It's the little annoyances with Android that keep me coming back to iOS but now it seems like they're introducing all kinds of new issues with iOS. Ugly.
You can't be the most popular if your competitor's market share is ~85%.
Also, the amount of lag when loading basic apps has increased significantly with this update (I have an iPhone 6s).
If you mean one of the developer betas then that's the cause of ...
> [apps take a long time to load]
So no, the developer beta is not the cause. It happens to me and a lot of my "normal" friends who just upgraded their iOS because it kept bothering them with push notification to upgrade.
I think you might want to debug this like a problem rather than assume it’s all due to Apple errors. With all that’s going on I’d probably just jump all the way to a full restore.
As I mentioned I have multiple devices and I observe these problems everywhere. And I have heard the same from friends too. And all these people on this thread are complaining about it.
Now where is your source on how my problem is just some extreme case and my own fault?
On my iPhone 6 I see maybe a crash rate of 2-5% (one in 20-50). There are apps with higher crash rates from time to time that usually get fixed with updates. I don't try to run the latest demanding 3d games and such on the phone, since I don't expect them to be usable on a 3-year-old device.
Maybe you're pushing your devices harder than I do or something but I second the parent's sentiment that your experience is out of the ordinary. But that doesn't mean it's your fault at all, just unusual.
All that being said, I'm overall less happy with iOS 11 than 10 on my phone. But love it on the iPad.
I mean, if that’s what you prefer to do, be my guest. I don’t mind at all. I’m just pointing out you might be able to do something about some of the problems.
Also, I didn’t say it was your fault. I get that you’re frustrated, but it doesn’t help to get angry, especially with people who are trying to help you.