Frontend is in Java (and Kotlin), indeed, as it's a part of the IntelliJ platform. However, the backend that actually provides IDE features for C# is written in .NET. The backend is actually the same ReSharper logic that runs in Visual Studio but in headless mode.
"instead of reimplementing ReSharper’s features on the IntellIJ Platform, which runs on the JVM, we’re using ReSharper in a headless mode, out of process, and communicating with it via a very fast custom binary protocol. "
If you look at the underlying markup, you can see that the web site was designed to be responsive. The sad part however is that it's going to take a bit more time for mobile resolutions to be supported properly.
I tried it using Chrome Dev Tools and emulated several mobile devices (some apple, some android, etc...) and even after a refresh and dumping cache, it did not go into responsive mode. It only gets smaller so the entire page fits on-screen for the mobile.
This has nothing to do with supporting mobile resolutions. The site just doesn't do responsive... at all.
"Phoning home" is actually not new. We've introduced JetBrains Account as a way of authorizing a product instance (as an alternative to license keys) for a couple of years now.
Current student licenses work exactly the same way, as well as a part of classroom and OS licenses AFAIK. A lot of current personal and some commercial licenses are managed through a JetBrains Account as well.
With the new scheme, JetBrains Account will simply gain more usage than now, hard-coded license keys will eventually go away, but a license server option for environments that have restricted Internet connection will be provided the same as it is now.
Now, there might be certain additional steps we might need to take to ensure license delivery in certain scenarios but we'll be handling this as we receive specific problem reports.