Approaches to naming products

Last edited May 2021
Backlinks: Naming principles, Perpetual interests

There are four ways of naming products:

You can name the product based on its function. For example: editor, presenter, reviewer. These names tend to be agent nouns.

You can name the product based on its high-level object type. For example: tracks service, playlists service, retweets service. I found that this approach works well for microservices, where each service encapsulates a domain.

You can name the product based on its intended audience. For example: creator app, curator app.

You can use a codename for the product. For example: koala, rhyolite (Okay, maybe not “rhyolite”. Who will remember how to spell that), neptune. This is particularly useful for products that are not yet stable and well-established, which might well be the case for all products that are in active development.