How to learn to write a GUI interface in web applications that is not inferior to the familiar desktop world?

Question

User interface

I want to learn how to write WEB applications with a GUI, but in such a way that the interface is in no way inferior to the interface made in desktop applications. Ultimately, the applications I develop should be no less convenient than the usual desktop applications.
As an example, let's take the Windows calculator, the executable file calc.exe. Let's run. What do we see? Buttons, checkboxes, edits, radio buttons, menus, menu items, additional screens (windows) that appear when you click on any of the menu items. At the same time, the application is quite responsive and interactive. I want the WEB-applications I develop to have all these characteristics and to make it as convenient for users to use them as they are when using ordinary desktop applications.
What do I need to study for this?
So far, I have studied the holes in my knowledge and made a plan for self-development as follows:
1. HTML - In progress. Reading the book "E. Freeman, E. Freeman - Learning HTML, XHTML and CSS" and trying to do things on my own manually typing in Sublime Text 3
2. CSS
3. JavaScript
4. For testing, study google-driver for Chrome in conjunction with Selenium .
Is everything right?
Please share your experience

Answer 1

Web and desktop will always be conceptually different. What do you want to achieve? to make the Web work like a desktop app? Good luck, so far I have not seen anything worthwhile in this area. The difference is in storing application state. The web works on a "request/response" basis, with the web server not aware that one request is somehow related to another. The desktop spins constantly in RAM and always stores its state. What to read? Materials on the development of web statefull-applications. Add some server-side (or is it Node.js?) to your list of skills

Answer 2

SPA - Single Page Application
For example, emberjs.com
UPD: I stumbled upon this by accident: tutorialzine.com/2015/02/single-page-app-without-a...

Answer 3

The question is basically clear.
But - why not just write a desktop application?

Answer 4

The web will always be an order of magnitude slower than native applications. Their appearance is also neither fish nor meat, which does not please the eyes of users. This has always been the case and I see no reason why it will change in the future. There are no problems with interactivity, with functionality and the presence of all sorts of UI elements (jQuery UI) - too, except that everything is noticeably larger, because it can be opened on devices without a mouse, where there is only a finger, only hardcore.

Answer 5

Web and desktop applications are completely different things. You must first understand this, and then decide what you want to do. You can make both the site and the program mediocre, but it’s difficult to make it good. But comparing these things is like comparing windows 95 and pentium 2
PS
As programmers get into the frontend, all sorts of angular.js are obtained, in which there are no links to static pages, inline styles are anathema, there are attacks on the cascading of style sheets, etc.