Skip to content
Permalink
main
Switch branches/tags
Go to file
 
 
Cannot retrieve contributors at this time
---
title: How to name software products
last_reviewed_on: 2021-03-16
review_in: 6 months
---
# <%= current_page.data.title %>
Read this guide when you need to name components for your software product, for example applications, software libraries, plugins or frameworks. Your users should understand what something does from its name.
## Your product name should be self-descriptive
Avoid using puns or branding for names as this makes it difficult for others to understand what it does.
Make sure you use the same name consistently whenever you're referring to the same product. For example the name of the Signon application’s GitHub repository is [alphagov/signon](https://github.com/alphagov/signon).
These GDS product names clearly communicate their purpose:
- [Signon](https://github.com/alphagov/signon)
- [Manuals Publisher](https://github.com/alphagov/manuals-publisher)
- [Smart Answers](https://github.com/alphagov/smart-answers)
- [Digital Marketplace Admin Frontend](https://github.com/alphagov/digitalmarketplace-admin-frontend)
- [Notifications PaaS Autoscaler](https://github.com/alphagov/notifications-paas-autoscaler)
These GDS product names are ambiguous and possibly confusing:
- [Panopticon](https://github.com/gds-attic/panopticon)
- [Whitehall](https://github.com/alphagov/whitehall)
- [Maslow](https://github.com/alphagov/maslow)
- [Magna Charta](https://github.com/alphagov/magna-charta)
## Further reading
The Service Manual has [guidance on naming
services](https://www.gov.uk/service-manual/design/naming-your-service), and this will be relevant when naming applications or packages.