A user story for updating a rich client application could be "As a user, I want to be able to update my application from the internet".
But let's now assume that this update process is completely transparent. For example, the rich client could automatically connect to an update server and "refresh itself" without any user interaction".
In that case, how would the user story be written ?
According to the various articles I've read, it looks like what used to be a user story is now a technical requirements which should not be part of the product backlog but I may be wrong...
How about "As a user I want that my application updates itself so I have always the latest version and I don't have to take care of it myself".
To me it's a totally legitimate user story as there is user value. The fact that the user doesn't have to perform any action doesn't invalidate the story. Lots of features are about "automatic" stuff.