Hacker News new | comments | show | ask | jobs | submit login
Try quickly typing 1+ 2 + 3 into the iOS 11 Calculator (reddit.com)
886 points by danso on Oct 24, 2017 | hide | past | web | favorite | 479 comments



People are talking about "lag" and performance, as if this was a "the system can't handle it!" issue. This is a misleading description. 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.

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


Your solutions are a little off the mark. Treating the animation as the problem is merely treating the symptoms.

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.


Exactly. This is a very general pattern of error in software design - the use of a non-causal pathway to model causality. It is an especially exasperating problem, as it is both more complicated and more prone to failure than doing it right.

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.

https://en.wikipedia.org/wiki/Turkish_Airlines_Flight_981#Ca...


My "lazy" solution was absolutely treating the symptoms, yes. Which is why I classified it as a lazy one, even.

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.)


Isn't 'never' an oversimplification? Sometimes there is a feedback loop between UI effects and user input, or the user input changes the way the UI registers hits, which means subsequent input depends on complete processing of prior inputs. On a static view like a calculator grid, you should default to non blocking animation, but sometimes blocking is the desired behavior.


What's a concrete example of this?


An example that comes to mind is a slider switch (iOS is famous for them)

You don’t want the switch activated until it’s all the way left or right.


An even simpler example is page-based navigation. Can't register UI hits while pages are animating in and out.


What if you want to quickly flick through pages? Having to wait for each page to render would be awful.


Slider controls might be a better example, I think. In that case, the position reached by the moveable element is the data, and it is appropriate to take the value from the UI element (of course, if it lags noticeably, that is a UI design issue.) With slider switches, you could argue it either way, so long as program and UI remain consistent, but again there is a problem if the UI response lags the gesture.


Video games use animations as easy to project information to a player. If your character is “stunned” and can’t move, the animation should play for the duration of the status effect.


Sure. But that’s an inherent feature of the animation. In this case the “never” rule doesn’t apply. If animations are a side effect, you want to treat them as such.


The never rule not applying what what I was giving an example of!


But should any buttons pressed during that time be queued? Command queueing and cancellation is an important part of game design.


Tetris


My professor likes to tell this story about keyboard buffers that I never quite understood. Basically, in this old time terminal setup he would start typing the password before the prompt showed up or something and when it did, it would just sail through. Sort of like how I can apt upgrade while apt update is still running but fancier and a couple of decades before...


The computers at my old job working as a cashier did that. It made working with produce so much faster because as soon as I heard the beep, I could move on to the next item, even if the screen hasn’t updated yet.


That "old time" hurts a bit.. I haven't tried this recently, but I distinctly remember doing this in the early versions of Ubuntu.


That's what happens when you read from a keyboard buffer. Since the buffer is not being read (and not cleared) until a prompt is in the screen, you can type whether you want and it'll get dumped and processed whenever needed. Not that long ago really, that's how it worked in DOS and most other terminals.


It still works. I can ssh into a machine and start typing commands before the shell prompt appears. The commands will appear in the terminal once the connection is established and the shell is ready.


Isn't the keyboard buffer a part of the physical keyboard circuitry and interface? Hitting enter triggers an IRQ to flush the buffer, so if the CPU is too busy to handle the IRQ then things queue up until the CPU can get around to handling it. If that's the case, for this "feature" not to work would require a very low level architectural change to keyboards. (it's been many years since i've thought about this though)


Keyboard buffers are decidedly not on the physical keyboard. The keyboard might have a very small one, but the IRQ is triggered on every input.

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.


ah, the more you know :) I would have been shocked if i remembered all that correctly


For some reason my brain still finds it important to remember that the BIOS keyboard buffer is 15 bytes by default, but that you could load tiny little devices drivers in CONFIG.SYS in MS-DOS to make it a whole 31 bytes.


You can still do this in at least some shells. PowerShell buffers input if the running program doesn't capture it. If I have a build and execute commands in the history, I can hit up-up-enter twice in a row to start the build and queue the execution command.


I remember people doing that on an AS/400 ramming keystrokes for 5 seconds and then waiting 15 seconds for the system to arrive in the right screen, sometimes even already filling the fields from muscle memory. The first five lines of address data were already entered before the screen loaded.


When I was in high school I had a job after school where they still had a PDP/11 w/real DEC VT-100 terminals. The kid next to me used to do data entry and would get far ahead of the input screen. Except when he made a mistake, and he often did, it would beep. But because he was so far ahead when he made a mistake it would beep for 2 minutes straight. Every time. Max-volume.

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..


Oh wow. That is awesome.


> Sort of like how I can apt upgrade while apt update is still running but fancier

You can link two commands together with the "AND IF" operator

    sudo apt update && sudo apt upgrade
Furthermore, you also have `||` which is the logical or, and also `;` which is just a separator which doesn't care what happend to the command before.


I see that buffer effect all the time still.


It is not as easy as that. UI and logic should run in parallel , yes, but they should also be able to synchronise.


This shows how important UX really is. UI can be all glam and shiny, but the software with the most accessible of UX wins, more often than not.

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.


A really important element of WhatsApp's global success is that they had a Java ME app for featurephones.

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.


> cryptic UI, teen-oriented

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.


I hated it at first, but I've come to really appreciate being able to swipe around through almost all the screens, vs. having to stretch across my phone to hit menus on the far corners in other apps


Agreed. They still need to put in more subtle cues to do things though. Most people don't know you can use multiple filters/stickers or touch a location to change it.


> Similar thing for AMP pages: It just works and it is blazing fast.

It is already blazing fast with only HTML and CSS, as the Web was designed to be.

EDIT: typo


Add some async JavaScript to onclick, onchange, etc. events.


WhatsApp also won because it did what most tech companies seem to consider antithetical to their purpose: put international customers on equal footing to US customers. So many companies either don't serve or completely gimp their product outside the US, often for no good reason.


Unfortunately AMP pages don't just work. I've had problems with them, especially with the top menu that is hard to bring back when scrolling up sometimes. Also sometimes the page doesn't load and I have to go back and reopen the page. No consistency on functionality... (Some sites are missing links to important things like comments)


> cross platform

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.


Not to mention you get banned from trying to use any unofficial client if your device/OS happen to not be supported.


> People are talking about "lag" and performance, as if this was a "the system can't handle it!" issue. This is a misleading description.

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.


Well everything nowadays is slowed down by the 20 abstraction layers, so I wouldn't be that surprised if someone managed to make one slower than a 35 year old calculator.


Maybe we should start worrying about "animation creep" as much as we do feature creep or other kinds of unnecessary complexity.


One of the main reasons I don't use iOS or macOS anymore is because of the animations. Even very, very short animations make the whole experience excruciating for me. It feels slow and unresponsive.


One reason I moved from Android to Windows phone was because of the massively unpredictable performance (lag due to background stuff happening).

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.


So what do you use instead? FYI you can reduce animation in the accessibility menu of both iOS and OSX


When I had a choice, I used Fedora + XFCE for a long time, then Xubuntu. I've been on Windows 10 since it came out, and it's been incredibly liberating not to constantly have to think about my OS and Google my way through its quirks and bugs.

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.


Every day I experience lag typing something into glitzy web apps because someone made the text box wait for something it doesn't really need to. It's definitely slower than word processors I've used twenty years ago.


True, there are so many layers things aren't up to par. Maybe get back down to basics with languages like Rust and rewrite a few things? But then we'll end up with 20 layers or so of abstraction after 20 more years...


I could seriously think that. A pocket calculator has a ~200KHz processor and an LCD with an update time of maybe 10ms. A single digit calculator operation like addition would be a few clock cycles, so say a total time of 15ms with output buffering. A 60Hz monitor refresh rate is already worse than that without considering the framework stack.


Do you have a source on that clock speed? I've been trying to dig up info on pocket calculators for a while.

(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.)


An even easier fix would be to drop the "Animate all the things!!!" mentality.


I think animations are pretty useful in this context. It reassures you that your sausage fingers didn't hit the wrong number.


I agree with you. Why not be more utilitarian and build things for function and not for looks.


I commented to the same effect on reddit: This doesn't ring true to me at all.

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.


>Conveniently, this should be a trivial fix

trivial to fix the bug in the calculator app. not trivial to deploy that fix. this would be a full system update, right?


Yeah, it'd have to be a proper OS update, because it's one of the core apps.

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...


Since iOS 10 the system apps have been on the App Store, and as far as I know, they can now be updated that way, too.


They‘re listed on the App Store but they‘re fake listings. Removing a core app from the home screen does not remove it from the device. Installing it from the App Store restores that link.

That means updates still need to be a part of a system update.


In iOS 10, reinstalling the News or Calculator apps was instant. In iOS 11, the App Store list sizes for these apps, and reinstalling them takes a few seconds (on my phone and connection).

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.


How this works in Android for system apps: One can only disable a system app. This disable button replaces the uninstall button. It deletes any updates to the app from your phone, since it will obviously still have the original version baked into the ROM, and removes it from the app list. It might also disable any service registrations for the app... Unsure on whether that's true.

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.


That's interesting! I hadn't noticed the change. As you say, it's probably not relevant until Apple can actually release a single-app update through that channel, but it might be a glimpse at a future where that's an option.


Like IE in Win XP


You are probably correct. Maybe if the developers decided that their precious prefab apps didn't need to come prebaked into every release of android and iOS and instead let the consumer pick, the market would be a bit less full of app bloat.


Does iOS runtime not use evented I/O? Coming from web, I would expect tap events to queue up while the thread is busy with an animation.


CoreAnimation runs animations on a background thread using state snapshots.

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).


Correction—CA animations process and render in a render server process. This is why even when the main thread is blocked, animations can continue.


While the button is animating, it simply doesn't respond to touches. There's no thread that's stuck. 1 + 2 - 3 consistently produces the correct result because + and - are different buttons.


It’s a simpler matter of not passing “allowuserinteraction” to the UIView animation options.


> People are talking about "lag" and performance, as if this was a "the system can't handle it!" issue.

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).


For the layman the "system" in this context is the calculator, which can't, indeed, handle it.


> tap an operand, tap a number, then tap the operand

The numbers are the operands.


Heh, yes, you're quite right. "Operator" is what I should have said. Total brain fart. :D


So it looks like this is a case of "operator error."


No, just don't block input during animations.

I can't come up with a good UX reason for that restriction, so either it's an oversight or a technical limitation.


Apple does not seem to test a lot these days...


or they test, find bugs and decide they're not worth fixing...


[flagged]


Would you please stop posting unsubstantive comments to Hacker News? We're trying for a somewhat higher level of quality here.

https://news.ycombinator.com/newsguidelines.html


Apple ships several 10s of millions of lines of code across a billion devices.

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.


Speaking of lag, I wish turning on/off cellular data didnt have that 2 second lag. why cant it be instant?


My thoughts exactly.. You are correct


Just checked the Android calculator implementations from Google and Samsung on my phone. They correctly handle button press animation asynchronously. Look like Apple doesn't dog-food their software anymore after Jobs.


Let's just be frank: If Jobs was in charge, everyone that remotely touched that app would pulled into a room, berated and told how fucking dumb they are, and told to pack their shit and find another job. Remember, he was obsessive about the first calculator app and hand-tuned it to his liking, so it's not hyperbole to suggest that he would be fucking livvid. [1]

Asshole, but perfection requires assholes. Apple is regressing. Their products are too expensive to tolerate regression.

[1] http://www.businessinsider.com/macintosh-calculator-2011-10


>Let's just be frank: If Jobs was in charge, everyone that remotely touched that app would pulled into a room, berated and told how fucking dumb they are, and told to pack their shit and find another job.

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.


TIL some people think berating your employees when they do a mistake is a good way to run a company.

WOW!

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...


Grandparent isn't trying to condone the practice of berating employees but to demonstrate how Apple under Steve Jobs would've been much more likely to catch these kinds of screwups before production and much less likely to tolerate them once they occurred. The means of correction are less important than the standard of quality which was effectively enforced.


I don't think that's what he's saying, but c'mon; it's a pretty dumb mistake. QA should be hauled in as well.


So against we have Brian Goldman, MD. And for, we have Steve Jobs, Bill Gates, and pretty much every other tech/entrepreneur darling of the 20th century. I'm pretty sure the results speak for themselves here.


I don't think firing people is berating.


This is pretty unforgivable. It's like ok great, I'm paying 50 people to make an app and NONE OF THEM EVEN USED IT?!


He is not condoning it just mentioning how under Jobs this would have been a big deal.


I don't think Job's way was a good way, but it's certainly better than whatever the hell they are doing now.


Didn't the iphone 4 antenna issue happen under Jobs? With him claiming you're holding the phone wrong or something like that.


You mean the iPhone 4 antenna non-issue?

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.


A relative's phone calls got disconnected very regularly until she covered the antenna with tape. If nobody in the real world had any issues with it nobody would have discovered it in the first place.


>If nobody in the real world had any issues with it nobody would have discovered it in the first place.

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...


No it definitely existed. I got a 4, and it was not uncommon to go from a perfectly fine phone call, to a dropped phone call until I got a case.


And it was such a perfect phone to use without case.


Considering they gave away free bumpers, I have to disagree.


That link is an incomplete version of the the original story here:

https://www.folklore.org/StoryView.py?project=Macintosh&stor...


Are you a programmer? If so, is not getting yelled at what motivates you to write good software?


I am a programmer. And if I shipped a crap like this, I would agree that I deserve to be yelled at.

But the problem is probably not at developer level, it's higher ups who don't care about quality control, which permeate downwards.


You didn’t answer the question, but I’ll go ahead and suggest that you are motivated to create good software, not by a fear of being yelled at, but rather something else. Maybe you think the product you are making is of actual value, and are proud of it. Maybe you want to impress your boss with the quality so you can get a raise. Maybe you don’t want to be fired.

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.


A rhetorical question that has only one answer doesn't really require an answer.

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.


If I'm at the sort of job where I get yelled at for doing my job as I saw fit, I will be motivated in the future to find a better manager.

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.


Would getting yelled at make you perform better?


Define "getting yelled at".

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.


Apple software has been buggy since they invented the freaking bomb icon.


> perfection requires assholes?

Wait, wat? How?


To get the shit out, I presume.


Its a miss on qa end. so if the qa in my company is good they are assholes ?


QA found it. Management decided not to fix it and ship. Who's the asshole?


Design demanded that it look nice even if that meant not working for power users. The Apple way since 1978


To enforce critical assessment of one's work with people who are not inclined to do that on their own.


Dude, it's Apple. Hold your tongue. ;)


Does nobody have a sense of humour or the ability to literally hold their tongue and say Apple?


Steve left Forstall in place to fill that role. Guess he made the wrong people cry. Maybe he’ll make a grand return someday.


If Jobs was in charge this wouldn't have happened


Antenna-gate (the iPhone antenna not working well enough if you held the phone) happened while Jobs was in charge.


Not the best example.

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.


Seems you are cutting and pasting, but Apple gave away free bumpers with the 4, so yes, it was an issue.


You also seem to be repeating your reply.

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.


>Seems you are cutting and pasting

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.


>Which few really used in the wild, so no, it wasn't. Are you saying the average iPhone user doesn't have a case?


If Jobs was in charge, he would still be living and people are worried about calculator.


Or he might berate the users, like he did with the antenna.


Steve Jobs died in 2011. Let it go.


As soon as I upgraded my 6s to 11, I saw performance seriously degrade. It takes -seconds- to bring up the iMessage editor.

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!


> 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.

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.

and

> 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.


What is debunked? That the CPU has not changed during the upgrade? No shit sherlock. Synthetic benchmarks tell nothing of the end-user experience.

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.


> What is debunked?

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...


Tired of people bringing up that "article" and the sensationalist media headlines. All that articles shows is that the CPU, given 100% utilization, does the same result as it did on iOS 10. Really surprising for sure. So what was the point of you posting that article? People saying "Apple is slowing my device" don't actually mean "the CPU has become slower". There goes the entire premise that benchmark. The CPU is the same—the software is less optimized for older hardware. The net effect? The software runs slower (and in some cases much slower) than older versions of the OS.

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.


>Tired of people bringing up that "article" and the sensationalist media headlines. All that articles shows is that the CPU, given 100% utilization, does the same result as it did on iOS 10

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.


No—even at face value, "sprinkling wait()" does not slow the CPU, it slows the software running on the CPU; if you then manage to obtain 100% for your thread, that does not disprove that Apple has not added `wait()` anywhere in their code. In their code—software.


Technically the 6s is now [latest - 2] hardware. X/8/8+ have the A11 Bionic; 7/7+ have the A10 Fusion; 6s has the A9.


Exactly what I said. It runs "fine" on 7, while it runs slow(er) on 6S.


iOS 11 runs fine and just as fast as iOS 10 on my SE. It sounds like you are experiencing a bug.


Aren't there, like... 3rd-party chat or emoji apps or something now? I don't use any of that stuff, but if only some people on 6-series iPhones are experiencing a multi-second delay opening the iMessage editor, my first guess would be they have some of those installed and one or more of them have shit the bed.


Ah, my mistake, I was taking the scare quotes to mean you were complaining about it on your hardware.


>>As soon as I upgraded my 6s to 11, I saw performance seriously degrade. It takes -seconds- to bring up the iMessage editor.

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?


Just googled, found this...

"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."

https://www.macrumors.com/2017/09/25/ios-11-app-slowdowns-pe...


I did a backup and complete restore. It went from completely unusable to annoyingly usable. Still considering downgrading to 10.3


Signing window has closed on 10.x.


Not for 6S. It has some issues and Apple still lets users downgrade.


not to mention you can't restore a backup of 11 on 10.x...


is it possible to downgrade to 10.3 ? I thought you can't do that anymore once you upgrade. I upgraded my old iPad to 10 and the experience is horrible. I wanted to downgrade back to iOS 9 but I can't find a way to do it.


I can confirm. Tried the same - wipe and reinstall. Phone is slightly better but still lags for Camera, forwarding images to WhatsApp and to open iMessage.

And this when I have yet to restore from iCloud or restore an entire 25GB Music cache!

What's happening, Apple?


Same problem, tried this and did not work. The only solution for me was to downgrade to 10.


You can disable animations in Accessibility settings along with other things. Check it out!

EDIT: Should probably mention it's called Reduce Motion.


On iOS 10, it does not disable animations but replaces them with fade-ins/fade-outs. I don't know the behaviour on iOS 11, but I suspect it is going to be the same.


It is, but it does feel a bit speedier. Interestingly I’ve had Reduce Motions on for quite some time and just turned it off. Feels kinda newish now, but I guess I sometimes just like change for changes sake.


I had it off. Just turned it on — feels no change on iPhone 5s.

Resetting all settings seems to have done the trick. But I am not 100% sure.


I uninstalled my 3rd party keyboards because the lag to bring it up got much worse with iOS 11.


So why do you update to the latest version? iPhone 6 is quite old by now, and the updates have historically caused reduced performance. I didn't put Windows 7 on my old 1GB Windows XP machine because it's dumb, you should think about the same when updating your phone.


If Apple says you should update then it must be knowing what will work in that hardware.


>>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...

The typing on iOS 11 in all apps is absolutely abysmal. What the hell is going on?


On an iPhone 6, if you type quickly, AUTOCApitalization lags and doesn't switch off until after 4-5 characters, which is absolutely mindboggling. The system obviously knows you've typed more than one char, is this thing multithreaded in the extreme?!


> 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.


For .0 releases they’re furiously coding against a daunting fixed deadline. For .0.1 warranty releases, lingering showstoppers. The .1 releases get all the care. If I were smart, I’d wait around for dot-ones and eat my broccoli.


The giant is pulling apart at the seams.

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.


This is revisionist drivel.

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.


Do we even have sales figures for the apple watch. All I see is made up numbers and guesses.


I never noticed anyone anywhere wearing an apple watch.

Not that I spend any time looking at people's wrists, but you'd think if it was a massive success everyone would notice.


Interesting. Where do you live? Here in London they are really commonplace - you see them on people on the tube all the time and I notice them being used fairly regularly by all ages and sexes for contactless payments, running, etc. In fact they seem so widely adopted that it’s not uncommon to see even people with them who you would not necessarily expect to be wearing them.


They are given out for free to anyone signed up to Vitality health care (and stay 'active'). A lot of companies in the city use them as the health care perk.

I wonder how much that has bolstered the amount of people using one.


They're pretty rare in my UK city; I expect being able to use them for the Tube provides a useful rationalisation for the purchase - the are a lot more richer people in the greater London area too.


Plural of anecdote isn't data.


I think they were referring to "I never noticed anyone anywhere wearing an apple watch."


They are very common here in Austin. The woman working at the counter in the Post Office wears one and the last couple of doctors I've visited wear them. How common are they? I'm not sure. The fact that they have a distinctive appearance makes them much easier to identify than other watches since the other watch companies make so many models.

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.


I travel to a good number of middle America small towns and consistently see small business / middle manager upper middle class men wearing them. No women, fwiw.

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.


> The people wearing them aren't techie types at all

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.)


I shouldn't have implied adoption is necessarily low in tech circles. What I meant is that I've seen a surprising adoption by non-tech people, making the proportion of the adoption out of the ordinary and harder to jduge using past experience with tech devices.


I think it's one of those things you notice once you're looking for them. I certainly see them fairly regularly, in my smallish MidWestern city.

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.


Apple claims that sales are up 50% since last year with an estimate total of 33 million watches sold. Apple is even calling itself the "nr 1 watchmaker in the world", even though technically I believe Swatch Group is still larger if you include all of its brands.


The last wristwatch I wore regularly was a Swatch. That was back around 1994. After that, I either used stationary clocks, the time display on the computer I was using, or a cheapo toy-quality digital timepiece thrown into a pocket of my backpack--the sort of thing you might get in a cereal box or a Happy Meal.

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.


Apple said they're bigger than Rolex in revenue.


My iPhone 7 - the latest iPhone at the time iOS 11 came out, and with the fastest single threaded mobile CPU for some time - can no longer play locally downloaded audio and be used at the same time without stuttering constantly. Everything is broken on iOS 11. Extremely frustrating. I will buy a new phone, but not an iPhone.


I have an iPhone 7 and I do not experience this at all.


On the other anecdotal hand, I have an iPhone 7 and do experience this - normally through Overcast but sometimes Music will stutter and jank.

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.


I'm on the 6, two years older than that, and experience lag but never a single stutter on anything audio related.

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 worst thing for me is the Camera. If I want to take a photo of something that's just happening I don't even bother anymore since I can expect it to take 10 seconds to wake the phone, get into the camera, and have the shutter button respond and have it actually take a photo (sometimes it looks like it took a photo but it actually didn't save!).


Interesting. Bored before bed so ran a quick test using my iphone7 and Ios 11.x, Google's stopwatch.

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.


If I try it several times in a row it's quick, since presumably everything is cached in memory. If I've been doing other stuff and pick my phone up hours later (exactly when I want that split-second shot of my kid or the license plate of the car that almost ran over me), that's when the phone and camera take ages to get ready.


I really miss Samsung's 'double-click home button to use camera' on the Galaxy S6 and S7. Probably the most convenient implementation of a camera shortcut I've seen.


I like the Motorola double twist for camera gesture, you can start the gesture just as you take it out of your pocket.


I miss my Sony Ericsson that had an actual shutter button you could hold down to activate the camera from sleep.


OnePlus (five here) uses double power button for that and it feels quite fast/is very reliable.


Double-power on the Nexus 6P on Oreo - it's very nice.


Yes! Especially if what I'm wanting to do is take a video of my kid. By the time I get the photo app to respond well enough to swipe over to video and let it readjust itself, I have missed the moment by seconds.


This is one of the major pains that tore me away from Android (where I had several ‘flagship’ phones and kept them free of crap). If iOS keeps heading this way, what’s left?

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?


This. My 6 Plus is barely usable now, to the point where it is annoying the hell out of me. On iOS 10 i was fine with the 6 Plus and thought i could easily use it another year, but right now it's barely usable. I compared loading a banking app on my 6 and my colleagues 7 (closed it before) and the difference is astounding (2-3 seconds slower). Also everything is just laggy including typing and taking photos.


I have the 6 and benefited from uninstalling 3rd party keyboards and doing a settings reset. Might have also done a fresh install.

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.)


Odd, I have a 6s Plus and I haven't had any issues after upgrading. Sounds like it's hit and miss. I wonder if they changed the hardware during the production lifetime.


6S has the A9 processor, the 6 has the A8, maybe that makes enough of a difference for it to not be that bad. I will also try the complete reset though.


It takes 14 sec to open maps and load a screen of tiles, 4 sec to open messenger on a my 6 plus. I’d love to see timings for this on the newer models.

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.


5s for maps, 11s for messenger (3s for messages). But, this is on a plain 5, no "S" or any of that fancy stuff new stuff.

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.


Opening iMessage on a 6s Plus running iOS 11.0.3: Two seconds


This kind of thread generally piles up on rants of frustrated users, so here's another data (counter-)point: both are <1s for sure, possibly even less than 0.5s on my 6S w/ iOS 11, from a cold start. Everything is snappy and responsive, enough that I'd have to film this on slow mo and time it to be sure of any delay metric. Overall iOS 11 has been a solid performer for me ever since the second public beta.


I wasn't complaining at all. I love iOS 11. Just wanted to give some input.


Sorry for the misunderstanding, this wasn't aimed at you at all, I just responded to yours because you mentioned timings on a same gen device as mine and it seems mine is significantly faster. As for the rest, it's just that the sarcastic, conspiracist, passive-aggressive tone of many of the sibling comments is unnerving.


What exactly my tone should be?

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.


Unfortunately, this is a sad but regular scenario now. It doesn't matter whether Apple does it on purpose or simply doesn't care, but new versions of iOS degrade the performance of older devices (an in this case "older" doesn't necessarily mean "very old"). Some people simply choose not to upgrade, but this may have security implications - and in any case sooner or later you'll come across an app you need that doesn't work on an older version of iOS. You will upgrade, the performace will be degraded, and your previously "good enough" device will suddenly feel sluggish and old.


Is there any definitive evidence for this? Has anyone benchmarked devices before and after upgrades to prove it?

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's difficult to achieve because one cannot downgrade a device to some older version. So when 3GS became insanely slow with updates, no one could at random get a device with an old OS version.


This is a weak argument.

It takes literally zero planning to do a test now and then do another after the update.

I've found a few examples here:

https://www.youtube.com/user/kabriolett

These don't support the argument that devices are slower after updates.


Android (along with most Android applications) is profiled and tested on lower spec devices in a given year. If you buy a high-spec device this year, you could reasonably expect the system to become faster with updates rather than slower.


My biggest gripe is the flashlight delay - swipe up for control center, tap flashlight, and the actual light takes easily a third of a second to turn on. I suspect that's also waiting for the stupid animation to complete.

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).


The flashlight behaviour is odd, I just tried it and I got the same delay the first time I turned it on, but no delay after turning it on multiple times. It's almost as if the code was swapped out to a slow disk and you have to wait for it to be swapped back in before the first use. There's still no good reason why it should take such a noticeable time, though.


There's no swapping on iOS. The delay is probably caused by iOS lazily waking up some hardware. The same happens when you use haptic feedbacks:

>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.

https://developer.apple.com/documentation/uikit/uifeedbackge...


More annoying than performance is the ever increasing nagging for apple paid services, apple pay, apple icloud, etc. The platform is literally becoming a junk adware platform. It feels like an infected PC that pop ups ads randomly.


This is precisely why I will not buy an iPhone again. Every single time I open my photos to show someone something I have to wait through two popups that are extremely slow to close. Also now I'm getting nagged to upgrade to ios 11 whenever I just want to use the phone. Abysmal.


What's the alternative? Android, especially Samsung infested bloatware, is substantially worse. The touchwiz upgrade prompts are WAY more annoying than ios ones. Plus the constant Samsung login junk. And then there is the heavy google integration that requires a google account for almost everything.


Except it isn't worse. Not anymore anyway. Any and all notifications just go up top and don't prevent you from using the phone -- even if someone calls you. My 3 year old Sony Xperia Z1C that I only use to for testing lets me jump into whatever app I want as soon as it starts immediately even though I can see there's like 50 notifications to go through. But I can do that when it's convenient for me.

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.


Samsung OS is always slick until a year later when they drop all support for it, and the force installed apps start to install adware. This has happened on every Samsung I’ve owned.


All of those have a free tier and/or no paid levels. I've never not had Apple pay setup, so I don't know what the nags look like though.

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.


Same here. I had bought my 6s after my 6 got stolen, so it was my first time using iOS 11. My two-day old phone was absolutely unusable, freezing for over a minute every once in a while. Apps wouldn't open at all! I couldn't change the volume while the phone was locked. I couldn't listen to musics, or use the lock screen music handler, while the phone was locked.

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.


I was using a 6 Plus up until a few weeks ago. Every upgrade caused serious performance decreases and I avoided iOS11 entirely (anticipating an upgrade to a new device). My partner upgrades yearly and I gave up all phone tasks to him when we were out together as my performance was so bad. Unlock? slow. Open chrome? 2-3 seconds. Open safari? 2-3 seconds. Fancy webpage? Forget it. We use google keep a lot, it basically didn't work on the 6 Plus. Sometimes the app would load quickly, sometimes it would take minutes or not load (or maybe if I kept waiting, it would eventually?). Scrolling in the app hardly worked. Screen touches became more hit or miss. Reflexively, I built in a 2-3 tap routine for most screen touches as it took that many for them to register. Scrolling any sort of content was difficult, stutter-y, and inconvenient. Siri didn't work - but I'm not sure if it does now either. I also had all animations off in an attempt to squeeze some performance.

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.


iOS releases typically get a nice performance boost on the x.1 release. I wish it wasn’t that way (I’d like better optimization at launch), but this has been true since at least iOS 4.

Edit: to respond to another comment elsewhere in this thread, Apple also tests on all of the supported hardware when prepping iOS.


Strange, I see little to no difference on my 6S. I was considering getting an X, but since my phone still handles iOS 11 perfectly, I don't see any reason to upgrade.

I'd try restoring my phone if I were you - that fixes these issues for a lot of people.


My first smartphone, an iPhone, slowed to a crawl after some OS update about 2 years in. It's the last piece of Apple hardware I ever bought. The 3 non-Apple smartphones I've bought since then were all perfectly usable after 2 years.


My Samsung started dying unexpectedly at about 10% battery left. I bought another battery, popped the back cover and replaced it. For $10 it's as good as new.


It's unfortunate Samsung removed that option.


You can still buy Galaxy Note 4s. They are pretty good phones.


True - wouldn't the same hold true of the iPhone 6s and SE WRT headphone jack arguments?


> 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.

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.


I probably own more Apple devices than most people here (even considering this is HN we're talking about) because I do a lot of iOS programming and I have to use them as test devices. I also own the latest devices.

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.


Was going to upgrade to an iPhone X. After this iOS 11 nonsense, I'm honestly considering going back to Android. It's absolutely unforgivable how terrible my iPhone 6S has been running since the update. Same as you: constant crashes, random freezes and reboots, abysmal battery life, not to mention an insane bug where when someone calls you (or you call them), they can't hear you and you can't hear them. This bug persists until you reboot your phone. Like, wtf?

This feels like Apple has crossed the Rubicon. The Steve Jobs era is officially over.


Just for your information, take it for what you will, but I recently purchased a Pixel 2 to try out.

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.


+1 on the silent call bug (and the others 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.


Same here. My 6S quite often freezes. I also sometimes have a network problem that I never had before, no internet connection at all even when I have a full 4G signal, and I have to reboot the phone. Does anyone else experience this issue?


I have a 6S. I suggest doing a DFU and set up as new.


I'm in this boat, was excited about the X but after 11 and the confusing 8 vs X lineup, I'm just not sure what do anymore. At this point, it's a wait and see game


>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.

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.


"on maybe the most popular mobile OS on earth"

You can't be the most popular if your competitor's market share is ~85%.

https://www.idc.com/promo/smartphone-market-share/os


You can if you mean "most popular" in terms of customer satisfaction - http://www.theacsi.org/index.php?option=com_content&view=art...


In the USA, which is a pretty small part of the Earth, and where iOS has 45% of the market, compared to 15% worldwide.


Sure, it was just an example of how "most popular" might have nothing to do with market share at all.


I’ve been having the same experience with iOS 11. I often open the phone app to call someone I recently talked to, see their name at the top, click it to call them, only for the phone to call someone else. What’s happening is that someone else had called me in the meantime and iOS showed me the cached image of the screen but registered my touch on the “real”/live view of the screen. Safari does the same thing on both iOS and OSX when you swipe back and interact with the page, and I’m sad to be seeing that behavior leak elsewhere. Super frustrating.

Also, the amount of lag when loading basic apps has increased significantly with this update (I have an iPhone 6s).


Safari on the desktop is very, very bad about doing this. The browser benchmark tests really should include this metric: the average time to ready after navigating back. Showing a cached image but registering a click on a different image just seems like such an obvious thing to avoid.


Having exactly the same issues on my iPhone 6S. Camera randomly takes forever to load, and sometimes doesn't load at all (black screen). Since iOS 11 it's a 50/50 chance that accepting an incoming call works. I press the green button but it keeps ringing until the other person hangs up. Even physical home button becomes unresponsive, many times a day I have to do a forced restart (home button + sleep wake button pressed). This is infuriating!!


> I have the latest iOS installed

If you mean one of the developer betas then that's the cause of ... > [apps take a long time to load]


No, i have tried all versions and currently have the public version. I have given up on developer betas already, I don't trust them anymore. But I expected public OS to work as expected.

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.


With iOS 11 at this moment the developer betas are better than the released alphas.


Many of your problems are not the common ones that people are having with iOS 11. And even ones like 2. which many people are having sounds more extreme for you.

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.


Come on man, you don't have to go that far. just read rest of the thread and you'll see tons of people complaining about the same thing.

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?


The 50% crash rate on your apps is what made me feel like your experience is the exception not the rule.

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.


Well, I have iOS 11 on multiple devices and have friends with iOS 11 and I’m seeing (and hearing about) launch lag and the calculator button problem but not your other issues. So this isn’t simply an iOS 11 problem you can do nothing about besides complain on the internet.

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.


I've been getting the camera black screen at least since ios9 on 5s and 6s.

More

Guidelines | FAQ | Support | API | Security | Lists | Bookmarklet | Legal | Apply to YC | Contact

Search: