3 ms·

> being able to deploy same codebase on web and desktop Desktop UI and Web UI models are so different that in reality you cannot use the same codebase on 100%

• presentation 3y ago
  If you set the height of your body element to 100vh (100dvh in the case of iPhones), then the web acts like the desktop in this regard. They’re different since the tooling is different but not because they’re essentially different. > If you do need this then you can use Sciter's WebView that is a <frame> backed by system browser: iframes are very constrained in what you can do, if you’re targeting the web from the start you get the full power of using those libraries beyond the bounds of a single frame.
• The_Colonel 3y ago
  > Desktop UI and Web UI models are so different that in reality you cannot use the same codebase on 100% in both targets. I develop an Electron app and the CSS is 100% same on both web and desktop. It's not a "web page", it's an app, which doesn't use the "endless tape" model. > If you do need this then you can use Sciter's WebView that is a <frame> backed by system browser: At that point it seems easier to just use something like Tauri which uses the system browser for all rendering.