You can run the back-end on any platform or device that supports Node.JS. And you can connect to it on any device that has a browser.
The editor can run both in the cloud (on a server) as well as on your local machine.
The editor has semantic coloring, and automatic code indentation.
When launched from desktop it starts your browser in "chromeless" mode. eg. without the browser bar.
When running as a cloud IDE (PWA) users get the option to add to home screen
You can setup the editor as a cloud IDE and let others connect to it. Where users share the same developer environment, but get their own isolated workspace.
You can invite others to your coding session, where you will see each other type.
And if you login to the editor on another device the editor automatically activates "collaboration mode".
The editor has support for small screens and touch devices.
You can see changes while you are coding, when for example editing a .css file
the editor will automatically refresh the stylesheets in the preview.
And the preview will automatically refresh when you save a .js file.
During live preview editing the editor also gives IntelliSense/auto-complete for third party scripts! As well as dynamically generated code.
Do you debug using console.log ? You are not alone. When running node.js scripts, or developing web apps with live preview, the console.log messages will show up inside the editor! So you might not even need to open the browser dev tools.
Commit and manage source control from within the editor.
Speed up web development using the built-in static site generator which also supports live/preview and WYSIWYG editing.
"What you see is what you get" allows editing web pages in a sanitized "contenteditable" mode which allows people to edit web sites without knowing HTML.
You can see HTML source code and the live page side by side and can make changes in either the code or the page itself, and it will automatically sync.
Maybe you have a proprietary application that run natively? Users can run these apps from their browser using a "remote desktop" (VNC) view built into the editor.
One of the goals of the editor is that you should not need to use a terminal. But it has one built in just in case.
If the editor for is for example missing some feature in source control management (SCM) you can type in the commands manually in the terminal.
It's possible to edit files on FTP and SFTP servers. Or mount a Google Drive account.
It's also possible to open up files in the editor when SSH:ed into another machine, so that you don't have to rely on whatever editor is installed on the machine you SSH into.
The editor has different modes. The default mode is the CUA/Window's standard GUI key-bindings (Ctrl+C to copy), but you can also use "vi/vim" command and insert mode. Or add your own modes.
The goal with WebIDE is to be the best editor for developing progressive web apps (PWA)
This will be achieved by having:
No containers. The workflow with WebIDE is very simple: