Do you really need a smart client?

A classmate's company is planning to implement smart client on a new project, but the goal is confusing to me: Just to give desktop applications ProgramProvides the automatic update capability. In my understanding, the features of Smart Client can be summarized as "automatic update", "offline availability", "Rich User Experience", and "quick user response ", the automatic update function is only a part of the features of the Smart Client. From this perspective, clickonce may be a better solution.
The smart client uses Microsoft application update block to automatically update applications. However, it is not easy to use. On the contrary, clickonce puts almost no pressure on developers. Looking back at the evolution from the C/S to the B/S architecture, it is inevitable that some components will be regressed. The response speed and user experience of degraded Users lead to discounts on user efficiency. Although applications become more accessible and deployment costs are greatly reduced, user efficiency becomes a major problem. The B/S architecture greatly limits the possibility of developers creating efficient user interfaces. smartclient can solve these problems, but if it only focuses on the main contradiction, so I think the original c/s highlights two problems: Deployment update and execution security. Clickonce solves these two problems well. It can be used both to implement automatic update through IIS and to implement constraints on the program running permissions through. Net security policy. It can be said that it is a very affordable solution.