Software product teams working on large products need to give names to individual application components just so they can communicate effectively -- but that's not a good reason to force a user to learn names for different parts of something that, to them, is a single entity.
A common example: a Setup app is a little application that helps install a bigger application. The software team needs to keep straight which application they're talking about (in specs, bug reports, etc.), so they give the Setup app its own name. The user ends up having to bear the burden of figuring out who does what.
view post...
A common example: a Setup app is a little application that helps install a bigger application. The software team needs to keep straight which application they're talking about (in specs, bug reports, etc.), so they give the Setup app its own name. The user ends up having to bear the burden of figuring out who does what.
view post...
