The desktop metaphor has held for four decades because it was honest about what a computer was: a place to keep documents. The pressure on it now comes from a different expectation. People increasingly arrive at a machine with a task rather than a file.
The shift behind the interface
Three things are moving at once. Local processing is strong enough to run useful models on the device. Operating systems are exposing more of what a person is doing to the software layer above. And the interface is starting to accept plain language as a first-class input rather than a novelty.
Why software builders should care
For anyone building software, the surface you design for is becoming less stable. A product that assumes it owns the window may find itself one step inside a longer task the system is coordinating.
The useful question is not what the machine can now do, but where the person expects the work to start.
The unanswered question
Whether people want a computer that anticipates them is still an open question. Anticipation is helpful when it is right and intrusive when it is wrong, and the tolerance for being wrong is low on a device that holds someone's work.
Signals worth watching
The signals worth following are mundane: how settings are structured, whether a person can see and correct what the system inferred, and how much of this runs without a network connection.
