Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

We are not talking about a small number of users though, millions of their users use third-party screens.

They should have a test to make sure they don't get left in a dust with an update.



Is the onus on Apple to ensure the third-party screens work, or is it on the third-party screens to ensure they're compatible?


I don't believe the onus is on Apple to /test/ for all possible permutations since they own and control every component of their hardware, but the onus should be on them to fix any phones rendered inoperable by another iOS update unless its to prevent a bigger issue, 3rd party batteries exploding, etc.

This is also another good reminder to postpone the iOS updates as long as possible; I think it's been since v10 when the updates have had a less than stellar record.


> but the onus should be on them to fix any phones rendered inoperable by another iOS update

How is it their responsibility to support third party hardware? And, where's the line for support?

If I make a very poor knock off screen with a design issue that is made apparent with an iOS update (say, incorrect implementation of a required spec, interface, timing, etc), why should Apple have to support a flawed design?

What if Apple included a feature in the hardware that but the software wasn't ready at release, but would be made available as a standard feature in an upcoming iOS update? Should Apple have to continuously fragment their codebase, resulting in some tree of hacks to support each new half-baked chipset?

To someone in the hardware and software world, this perspective is absurd.


I find this stance very odd. How do you imagine them achieving this? Do they have someone constantly ordering screen from the hundreds of vendors on Alibaba, in some attempt to make sure they "find them all"?

If you could give one example of a company with a custom and proprietary system and chipset supporting third party knock offs I would be very interested. I've never witnessed this during my time in the hardware industry.




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

Search: