I’ve been Web-centric for a long time, and generally thought of what programmers build as “sites”. Then I was in Android and what everyone developed was “apps”. Now I’m in a generalist role and, uh, a little unclear as to how to refer, generally, to what software builders build.
It’s a real problem if you do a lot of advocacy, like me. I often want to start a sentence “Suppose you’re building an X and you need to...” What’s X? I’ve found myself forced into klunky constructions such as “site or service” or “app and back-end”.
Because it’s like this: Anyone who sets out to build a nontrivial piece of software these days is building some back-end server-side stuff and some browser-focused JS stuff and probably two mobile apps, iOS and Android.
I think I’m going to start using the term “app” to mean “all the pieces you need to build to have a deliverable piece of software.” Because three-letter words are good, and anyhow that’s what the actual people out there who use what we build are starting to say.
That OK with everyone?