Hi Marcus,
The way you write it suggests that you seem to think it is necessary to wholly abandon .net in favor of developing โwebโ apps. It is entirely possible to build web applications in .net (ASP.net MVC), mix and match (say a javascript front end with a WebAPI or WCF backend) or drop .net all together and use completely different technology. However, I donโt think you specifically need to have web app experience in order to get remote dev work.
If I were to hazard a guess youโre looking at location independent job boards and seeing an abundance of โweb appโ roles, often requiring php or ruby on rails or angular and it makes it seem like its necessary to abandon .net entirely and focus on web developer technologies so you can be employable as a nomad.
Thereโs nothing wrong with switching to learn a different platform and tech (itโs always good to expose yourself to other approaches), however that doesnโt mean its necessary.
I think what it really would come down to is your skills are and how you can leverage them to the advantage of potential clients (or your own startup).
You say youโre a .net developer. .net is a very huge space and it can mean a very wide variety of things. Your experience could lie anywhere from working with big ball of mud style legacy windows forms apps or building out cutting edge microservice (coughโฆ SOA) based architectures with thin multi platform clients and everywhere in between. Within each of these you could have specialized experience depending on the size of applications youโve worked with. As trezibond suggeted (I donโt know where his comment went), he never does web because his specialization isnโt UI (at least from what I read), its in the backend development. Thereโs lots of room in the spectrum for remote work if it is based on the right architecture that allows you to modularize the code and the work. If not, it can make things a bit trickier, though not impossible.
A small app can rather easily be pulled together simply in something like Angular. Pure websites as well can be rather small projects. Once it gets to be something of size however you reach a point where you have a distinction between front end (UI) and the back end which can be composed of many tiers or services. A lot of the remote capable positions out there are with small shops and startups who are building things from the ground up with a very small team (possibly only you). Often times this can be throwing together an MVP with whatever technology is best suited to get things done quickly. Others are more established and specific in the technology space and specialization they require.
As an example, I work remotely (for my own company mind you) and I build out the entire stack for my application composed of a javascript frontend, Web API & WCF based services hosted in Azure powered by SQL Azure. I cover all elements from UI design, the service architecture, sql query performance management and design and Azure devops, let alone the business side of things. There will come a time when Iโll be looking to hire on or contract people who specialize in sub areas of this that I can hand things off to and it will likely be across the board, not specifically just web focused.
I think what youโll want to do is hunt to see if you can find opportunities that match your skillset and experience. Web experience wouldnโt be a bad option if you feel you need more experience, though Iโd look for ways to leverage the experience you already have vs. completely jumping ship into something else (unless youโre heavy into legacy stuff that is no longer useful). One of the key things about software is that it is still in its infancy and gradually there are more and more parallels in techniques used across technologies. For example, if you rely on MVVM for building WPF/Silverlight apps, that knowledge translates really well to Angularjs/Knockoutjs as many of the concepts are the same.
None the less, I think one of the keys to being able to work remotely for a company is whether their culture supports it and in parallel, their technology requirements and architecture supports it. Youโll likely have a very hard time finding companies that are willing to hire people to build and maintain legacy windows forms apps remotely. However, anything thats small (often web stuff) or anything that has been modularly designed will be perfectly capable of being remotely worked on. That is assuming the business heads put more focus on deliverables rather than face time in an office.