{"canonical_url":"https://engineer.company/glossary/app/","content_markdown":"# App\n\n## What it is\n\nAn app is a program made for a person to open and work in directly: it has an icon to start it, a\nscreen or window of its own, and a job its user would recognise, such as sending a message, checking\na timetable or filing an expense. \"App\" is the clipped form of application, and the two mean the\nsame thing. The long form survives in formal writing and in compounds such as web application and\ndesktop application, and engineers often say client for an app that is the visible end of a service\nrunning somewhere else.\n\nAn app is application software, as opposed to the system software that keeps the machine itself\nrunning. The NIST glossary collects several definitions and notes that \"the terms application and\nsoftware application are often used synonymously\"; one of them counts payroll and accounting systems\nas applications too. A library sits on the other side of the line: code that other programs call and\nthat no person ever opens.\n\nApps come in three broad families:\n\n- **Native apps** are written for one platform in that platform's own language and toolkit, Swift\n  and SwiftUI on a Mac for instance, and installed from a store or from a signed download.\n- **Web apps** run in a browser and are reached by a link. A web application manifest, a small JSON\n  file giving the browser the app's name, icons, start URL and preferred display mode, lets one be\n  installed to a home screen or dock and open in a window of its own. A service worker, a script the\n  browser runs between the page and the network, is what lets it keep working offline. The pair\n  together is usually called a progressive web app, or PWA.\n- **Cross-platform shells** wrap one codebase for several operating systems, often by packaging a\n  browser engine inside the app.\n\n## Why it matters\n\nThe question behind most app projects is which family to build, and it is mostly a question about\nusers and distribution rather than about code.\n\nA web app costs one codebase and reaches anyone with a browser through a link. An update ships when\nthe server does: the next reload picks it up, with no store review standing between a fix and the\npeople waiting for it. The price is depth. A browser exposes less of the device than the operating\nsystem does, and every browser presents installation differently. On iOS, installation never appears\nas a suggestion, so a team that wants its web app on home screens has to tell people how.\n\nA native app gets the platform's own controls, keyboard behaviour, accessibility support and\nperformance, and access to whatever the system offers. It costs a codebase per platform, people who\nknow each one, and a distribution process: store review or, outside a store, code signing and, on\nmacOS, notarisation, which Apple requires for software distributed with a Developer ID since macOS\n10.15. Someone also has to run the update channel for as long as the app exists.\n\nA cross-platform shell sits between the two: one codebase and an installable app, paid for with a\nbundled runtime and an interface that resembles the platform without quite behaving like it.\n\nWhat usually settles it is where the users will be when they open the app. Someone at a desk with a\nwired connection forgives a lot. Someone on a phone with a weak signal forgives very little, and for\nthem offline behaviour is a requirement rather than polish. The other deciding question is who will\nship updates in the third year, because the cheapest app to build can be the most expensive to keep\nalive.\n\n## What it looks like in practice\n\nOn one platform many of the users are seafarers and field staff working from phones, often with no\nsignal at all. The answer there was a web app made installable:\n[full Progressive Web App support](/portfolio/delivered-full-progressive-web-app-support/)\ngives it home-screen icons in the sizes the platforms ask for, a splash screen and theme colours.\nIts service worker is set up through the next-pwa plugin, Workbox runtime caching serves fonts,\nimages, audio, video and CDN assets cache-first alongside HTTP cache-control headers, and the\ninstall and offline behaviour were tested over HTTPS on real devices. People can install it, keep\nusing it with the network gone, and get repeat visits from the cache.\n\nA messaging protocol whose macOS desktop client was a cross-platform shell took the opposite route,\nwith a\n[native macOS client in Swift 6 and SwiftUI](/portfolio/built-a-native-macos-client-in-swift-6/)\nthat runs to 11,141 lines across 53 files, with the protocol's Rust core linked in as a static\narchive built from a pinned revision. It starts as a Mac application, uses the platform's own\ncontrols and carries no embedded browser. The page names where it stops as well: it is not a shipped\nrelease, with neither a notarised build nor an update channel, and its interface speaks one\nlanguage.\n\nThis site can be installed as an app too, and the [install page](/install/)\nwalks through it browser by browser: no store, no account, no separate app package to download,\njust an icon and a window of its own. Safari on an iPhone offers it under Share.\nFirefox on Windows can add sites to their own web-app windows from version 143,\nor version 150 for Microsoft Store installations; Mozilla does not offer this\nfeature on macOS or Linux. The page also states the limit: offline use needs a\nservice worker, the site ships no executable JavaScript and registers no service\nworker, and so the installed app needs a connection exactly like a browser tab\ndoes.\n\n## Where it goes wrong\n\n### The screen goes white when the signal drops\n\nField users report a blank window or the browser's own offline page. The app was designed and tested\non the building's own fast connection, and every screen fetches what it needs as it opens. Decide\nwhich screens have to work offline, cache them and their assets with a service worker, and test on\nreal devices with the network switched off rather than in a desktop browser's simulation.\n\n### Users install a web app and expect an offline copy\n\nSomeone adds the site to a home screen, opens it on a train and meets the same error a browser tab\nwould show. A manifest makes a site installable; offline behaviour comes only from a service worker,\nand the two are separate decisions. Either ship the worker, or say plainly in the install\ninstructions that the installed app needs a connection.\n\n### A release goes out and users keep the old one\n\nAfter a deploy, some people run last week's code for days. The service worker serves the app's pages\ncache-first with nothing marking a new version, or a new worker sits waiting until every tab\ncontrolled by the old one has closed. Keep cache-first for assets that do not change per request,\nsuch as fonts, media and files with a version in their name, fetch documents from the network first,\nand show a reload prompt when a new version is ready.\n\n### The shell feels foreign on the desktop\n\nMac users complain about menus, shortcuts and text selection, and the app uses memory like a browser\nbecause it contains one. A bundled runtime is imitating the platform instead of using it. Where the\ndesktop experience is the product, compare a native client with the shell, and keep the shared logic\nin a core library that every client calls through a stable interface.\n\n### Distribution is left until the end\n\nThe app works on every developer's machine, and the first customer on macOS meets a Gatekeeper\nwarning instead of the app. A fix ships, and half the users keep the broken version. Signing,\nnotarisation and updates were treated as packaging chores for the last week. Put signing and\nnotarisation into the build from the first release, and decide how updates reach people before\nanyone installs version one.\n\n## Further reading\n\n- [NIST CSRC Glossary: application](https://csrc.nist.gov/glossary/term/application) — the\n  definitions NIST publications use, from any system built to meet a set of requirements to payroll\n  and accounting systems.\n- [W3C Web Application Manifest](https://www.w3.org/TR/appmanifest/) — the JSON file that names a\n  web app, lists its icons and start URL, and sets the display mode it opens in.\n- [W3C Service Workers](https://www.w3.org/TR/service-workers/) — the script that sits between a web\n  app and the network, with the cache and fetch events that make offline use possible.\n- [Apple Developer: Notarizing macOS software before distribution](https://developer.apple.com/documentation/security/notarizing-macos-software-before-distribution)\n  — what the notary service checks and when software distributed outside the Mac App Store must pass\n  it.\n\n\u003chttps://engineer.company/glossary/app/\u003e\n","date_modified":"2026-11-12T05:34:23Z","description":"What an app is, how native, web and cross-platform apps differ, which one fits your users, and what goes wrong between building it and shipping it.","formats":{"gemtext":"https://engineer.company/glossary/app/index.gmi","gopher":"https://engineer.company/glossary/app/gophermap","html":"https://engineer.company/glossary/app/","json":"https://engineer.company/glossary/app/index.json","markdown":"https://engineer.company/glossary/app/index.md","pdf":"https://engineer.company/glossary/app/index.pdf"},"kind":"page","language":"en","title":"What is an app?","url":"https://engineer.company/glossary/app/","version":1}