>>>>Right now, I can do more things with the user interface with C#/Winform than I can with a browser app, so if mobility is not a requirement, I might opt for C#/Winform over the browser.
>>>>For example, the reporting tools for PHP/MySQL are limited, where the SSRS features available with C# are almost limitless.
>>>>That's changing though.
>>>>Every day there are new web tools becoming available.
>>>
>>>... and is there a specific reason why you did not opt for ASP c#?
>>
>>I've done three or four ASP.NET based sites but now tend to move more of the work to the client. Settling on Angular and Typescript works for me - the server is now confined to providing static HTML pages and data. Generally ASP.NET meant a lot more round tripping between client and server - now I have apps that, once downloaded, can be run entirely offline.
>
>Hi Viv. Many thanks for your contribution. I think I'm ready to go WPF but haven't got anything in production at this stage. It would be my preference (partly given the time it has taken to master the concepts :) ). I need to develop a user interface for what I guess you would call a backend application that was developed as a console application, mobility is really not an issue. I just need someone to tell me I'm not completely crazy to go ahead with WPF.

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).

Markus Egger wrote a great framework for WPF using that strategy. https://codeframework.io/