>If you go WPF, make sure you build the data access and business code as webservices, so you can re-use those whenever you add or move to web based UI. The idea is that the WPF UI calls the same services for business logic as the web app would do (or any other UI you would develop in the future).
>

I also think the reusing idea is underutilized today ;-)
Danger of (too simple) REST approaches is that they shift the app to the chatty side, which on Marshalling can be detrimental, but across HTTP crippling if many hops are needed/asked for. Typical pattern to combat that leads to specific REST points for data sets/queries and ballooning interfaces. GraphQL not mainstream enough probably, but the idea to query remote services not too often smells better to me