With how buggy iOS 11 is/was, it really does show where their focus has been.
Do you mean you think that the same people within Apple are working on both hardware and software, and are focusing more on hardware? Or that you think many people who write software have been re-educated, re-assigned, and are now working on hardware?
I assume that the size of Apple's teams working on iPhone are limited by more than resources, and the recruitment pools are totally separate, so it's not like they're spending too much on hardware engineers and can't afford enough software engineers, right?
I just don't really know how you can conceive of such a massive company as having an obviously zero-sum "focus" like a person has.
IMO it’s less “focus” and more having to rely on third party manufacturers who will push back due to liability.
iOS 11 is a beta quality product. One org that I’m familiar with has a 5x increase in help desk calls and replacements, mostly around the voice phone components failing.
But the fact is, you can ship glitchy software and fix it later, so they do. Hardware is much more expensive to do that with, so they don’t.
You really think that with unlimited money they couldn't have better software? They could, but they don't because it does not have enough of a return on investment. They 'focus' their resources on areas that will return them profit.
Ascribing the bugs to malice or carelessness rather than the fact that this shit is difficult is very unkind. Source: know many people who have spent last few months feverishly working nights and weekends.
[1] https://www.theregister.co.uk/2017/08/24/nodejs_forks_ayo_co...
I am a developer on a team, too, and I know that sometimes you can't do everything you want because you simply don't have enough time, money, and developers to get it done.
I know it is hard, that is why I was saying it is a company resource issue, not a 'bad developers' issue. Even the best developer in the world can't complete a huge project by themselves in a short amount of time. You need company support, which means ample developers, QA, support, and time.
Not sure where you ever got 'malice' or 'carelessness' from.
It felt insulting because people I know personally do deeply care, and do spend a lot of effort for things that do not necessarily have a lot of return on investment (just for one example, iOS accessibility features for visually and hearing impaired are designed deep into the system and still have no equal). Aside from that, fixing bugs and improving stability does offer return on investment by building customer loyalty (case in point, after each major release I still see people mentioning Snow Leopard, an OS release dedicated exclusively to stability and performance improvements).
I’m not saying that things couldn’t be better, they always could, but I don’t think that all problems are as easily solved as you think. To take a classic counter example, Microsoft employs at conservative estimate twice the number of engineers compared to Apple, but still has not yet made a product twice as good or with half the bugs, imho. At a certain point, the system complexity just gets too great, and we need better architectures, tools and processes to get beyond that level.
Again, I am not saying you were intending to insult anyone, and apologies if I misunderstood something in your post. It’s just how it came across to me.
This bug has been annoying me, my family and friends for several days now. Nearly everyone I️ know with an iPhone. And the suggestion is to break predictive text to fix it. I️ really wish I️ would have bought an Android.
But yes I'd agree with that this is what iOS 11.0 should've been.