> Apple’s always done their best work when they’re the second mover.
> Apple’s always done their best work when they’re the second mover. People say Apple does its best work as a “second mover,” but that misses the actual pattern: Apple builds great products when leadership is solving their own problems. The Mac, iPod, iPhone, and iPad weren’t just refinements of existing products. They were devices Steve Jobs personally wanted to use and couldn’t find elsewhere. The man saw the GUI at Xerox and saw how anyone could use a computer without remembering arcane commands. So he drove the development of the Mac. He was using a shitty mobile phone, saw the opportunity and had the iPhone developed. Same with the early Apple Watch (first post-Jobs new product line), which reflected Jony Ive’s fashion ambitions; once he left, it evolved into what current leadership actually uses: a high-end fitness tracker. The stagnation we're seeing now isn’t about Apple losing its “second-mover magic.” It’s that leadership doesn’t feel an unmet need that demands a new device. None of Vision Pro, Siri, Apple Intelligence or even macOS itself anymore appear to be products the execs themselves rely on deeply, and it shows. Apple excels when it scratches its own itch and right now, it doesn’t seem to have one.
Posted by chartered_stack on Dec 8, 2025, 5:26 AM
Tags
Related issues
- The biggest problem with MOND is that it was hand-crafted with additional parameters simply to fit the data.
- (My comment is about detached houses).
- The biggest problem with this is that I can't run my company's own internal benchmarks against this API, because they will be trained int...
- > steer Claude away from over-engineering parts of the system in response to hypothetical concerns.
- Why is there no comparison with FLUX 3 Image?
- > our Git monorepo was developing an annoying problem Sentences like this are so common from people using monorepos that I am convinced ...
Raise real-world problems, find people facing the same issue, and discuss solutions.2,000 issues0 comments
hackernews (Other)
The biggest problem with MOND is that it was hand-crafted with additional parameters simply to fit the data.
(My comment is about detached houses).
The biggest problem with this is that I can't run my company's own internal benchmarks against this API, because they will be trained int...
> steer Claude away from over-engineering parts of the system in response to hypothetical concerns.
Why is there no comparison with FLUX 3 Image?
> our Git monorepo was developing an annoying problem Sentences like this are so common from people using monorepos that I am convinced ...
Why is there no contact form?
The biggest problem with plugging a generator into an outlet is you need a double ended cord.
> Apple’s always done their best work when they’re the second mover.
> Apple’s always done their best work when they’re the second mover. People say Apple does its best work as a “second mover,” but that misses the actual pattern: Apple builds great products when leadership is solving their own problems. The Mac, iPod, iPhone, and iPad weren’t just refinements of existing products. They were devices Steve Jobs personally wanted to use and couldn’t find elsewhere. The man saw the GUI at Xerox and saw how anyone could use a computer without remembering arcane commands. So he drove the development of the Mac. He was using a shitty mobile phone, saw the opportunity and had the iPhone developed. Same with the early Apple Watch (first post-Jobs new product line), which reflected Jony Ive’s fashion ambitions; once he left, it evolved into what current leadership actually uses: a high-end fitness tracker. The stagnation we're seeing now isn’t about Apple losing its “second-mover magic.” It’s that leadership doesn’t feel an unmet need that demands a new device. None of Vision Pro, Siri, Apple Intelligence or even macOS itself anymore appear to be products the execs themselves rely on deeply, and it shows. Apple excels when it scratches its own itch and right now, it doesn’t seem to have one.
Comments (0)
No comments yet. Start the discussion.