Why offline matters in electrical design
Electrical work is rarely done at a desk with reliable Wi-Fi. You check a board in a plant room, a basement or an unheated shell where mobile signal drops to nothing. If the design tool needs a live connection to work, that is exactly where it stops being useful.
A desktop package solves this by living on one machine, but then the project is tied to that machine and nothing else. A browser-based tool has to solve it differently, and the technology it uses is a progressive web app, or PWA.
What a PWA actually is
A PWA is a website that installs like an app. It runs in a normal browser, but it registers a service worker: a small script that sits between the page and the network and decides what can be served from a local store instead of a request.
From the user's side there is no separate application to install and no licence to activate. You open the editor, and the same browser app can be added to the device so it behaves like a native program, complete with an icon and its own window.
What keeps working without a network
Once the app has been loaded and cached, the core of the editing workflow continues without a connection. You can open the editor, work on a project and use the interface as usual while the network is down.
The point is that a dropped connection stops being a hard stop. On site you can keep reviewing a board, adjusting a circuit or reading the drawing, instead of putting the work away until you are back in range.
| Action | Online | Offline |
|---|---|---|
| Open the editor | Yes | Yes, from cache |
| Edit the current project | Yes | Yes, kept locally |
| Server-side tasks | Yes | Waits for connection |
| Sync changes | Immediate | On reconnect |
Working offline on site, on any device
Because the app lives in the browser, offline work is not tied to a particular computer. A phone, a tablet or a laptop can all open the same installed app, so the device you happen to have in a plant room is good enough to keep the design moving.
A tablet is often the practical choice on site: large enough to read a single-line diagram, light enough to hold while you look at the board itself. With the app cached on the device, no signal is needed to open the project you brought with you.
The result is a continuous workflow. You draw at the desk, review the same project on site offline, and the account brings the two sessions back together, rather than the file living on one machine that must travel with you.
How caching works
The service worker caches the app shell: the pages, styles, scripts and the interface needed to run the editor. When you request the app afterwards, those pieces are served from the local store, so it opens without waiting on the network.
Work you do offline is held locally rather than lost. Because the store sits between the page and the server, the app does not have to care whether each request reaches the network: it answers from cache and queues what has to go out later.
Versioning the cached app
When the app is updated, the cache is refreshed so you do not keep running an old copy. This is why an offline-first app updates itself in the background rather than asking you to download a new version.
Caching is selective, not a full copy of everything. The shell and the resources needed to run the editor are kept so the tool opens without a network; the data that has to be current is still fetched when you are online, which keeps the offline store small and predictable.
How your work syncs when you reconnect
Offline is a delay, not a separate mode. Changes made without a connection are stored locally and sent to the account when the connection returns, so the project continues from where you left it.
This matters when a job moves between places. You can start a design at the office, review it on site with no signal, and have the two states come back together without moving files by hand on a USB stick.
Limits to plan around
Offline support is strong for editing, but it is not the absence of a network by design. Some tasks depend on the server and simply wait until you are back online.
- Heavier server-side jobs, such as generating a large document set, run once the connection returns.
- The very first load of the app needs a network so the shell can be cached; after that it opens offline.
- A long offline session is safest when you sync before you rely on the project elsewhere.
- Clearing the browser's site data removes the local cache, so the app needs a connection to set itself up again.
Getting the most from offline mode
Treat offline work as part of the normal flow rather than an emergency measure. Load the app while you have a connection, so the shell is cached and ready before you go somewhere with a weak signal.
Because the tool is the same in the browser and in the installed app, there is nothing new to learn on site. The workflow you set up at the desk carries over, and the project follows the person rather than a particular computer.
A few habits make offline mode dependable: open the app once while you have a strong connection, sync any finished work before you leave, and avoid clearing the site data while a project is still local. Together they mean the editor is ready whenever you are, network or not.
Try it in the browser — start free →
FAQ
Can I design with no internet connection?
Once the app is loaded and cached, yes. The editor keeps working offline and your changes are stored locally until you reconnect.
Do I have to install a separate app?
No. It runs in the browser, and as a PWA it can be added to the device so it opens like a normal application.
What happens to work done offline?
It is kept on the device and sent to your account when the connection returns, so the project continues from where you left it.
Does everything work offline?
Editing does, but some server-side tasks such as building a large document set wait until you are back online.