# Cross-Platform Software

> What a software platform is, and why one program ships as many builds. Then how tools like Electron let one set of code serve them all.

**Course:** [Operating Systems and Files](https://learn.benibix.com/learn/development-platforms)  
**Time:** 11 min

**After this lesson you can:**

- Name the two parts of a software platform
- Explain why each platform needs its own build
- Weigh what Electron saves against what it costs

## Why one program comes in many downloads

A software platform is the base a program runs on. Most often it is a system plus a chip family. Windows on x86-64 is one platform. macOS on ARM is another. A popular desktop app may ship six builds or more: Windows, macOS and Linux, each one for x86-64 and for ARM.

Each build is needed because both halves differ. The chip decides the machine code. The system decides how a program opens a window, saves a file or uses the network, because each one has its own system calls and libraries. Change either half, and the program has to be built again.

Cross-platform software is written once and runs on several platforms. There are two ways to get there. Some tools take the same code and build a separate copy for each platform. Others run the code inside a layer that hides the system, such as a web browser or the Java runtime.

Electron is the best-known layer for desktop apps. You write the app in HTML, CSS and JavaScript, the same as a web page. Electron packs it with the browser engine from Chrome and with Node.js. The result runs on Windows, macOS and Linux. Visual Studio Code and Slack are both built this way.

The cost is size. Every Electron app carries its own copy of the browser engine, so even a small one is a download of tens of megabytes. Run three of them, and you run three browsers. An app built straight for each system is smaller and quicker, but the team writes and tests more code.

Cross-platform never means test once. Small gaps still show up between systems. A file name that works on Linux may be banned on Windows. A shortcut uses Ctrl on Windows and Cmd on a Mac. A team ships one codebase, but it still needs a test run on every platform it promises.

People often think a web app and a desktop app built this way are the same thing. A web app runs inside the browser you already have. It needs no install. An Electron app brings its own browser and installs like any program. So it can read your files and work offline.

![One box on the left, One codebase, has three arrows to three boxes on the right: Windows on x86-64, macOS on ARM and Linux on x86-64, each marked its own build. A note under it says an Electron app packs a browser engine and Node.js into every one of these builds.](https://learn.benibix.com/diagrams/dev-platform-targets.svg)

### Example: A notes app meets Windows

Emma and Jack write a notes app in Electron. One set of code gives them builds for Windows, macOS and Linux in one afternoon.

The first Windows user reports a crash on a note called To do: Friday. A colon is not allowed in a Windows file name, so they add a check and ship a fix the same day.

**Words in this lesson:** [Software Platform](https://learn.benibix.com/term/development/software-platform), [Cross-Platform](https://learn.benibix.com/term/development/cross-platform), [Electron](https://learn.benibix.com/term/development/electron)

**Question:** What is packed inside every Electron app?

**Answer:** Its own copy of a browser engine and Node.js. Electron packs a browser engine and Node.js into every app. That is what lets one set of code run on every system. It is also why each app is a big download.

---

Source: https://learn.benibix.com/learn/development-platforms/cross-platform-software
Author: Behnia Zarei (a developer in Vienna, Austria, who builds and teaches data, AI and business intelligence at BENIBIX)
Publisher: BENIBIX Learn (https://learn.benibix.com/)
Last updated: 2026-11-19
Licence: CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/). Quote freely with attribution.
