Ask HN: Is there any science to naming products?
I've been growing as a developer for the last couple months, using deliberate practice. Now, I'd like to release a mini product I've built for myself into the market, and am curious about what are the best practices (if any) for naming products.
I read the PG essay on changing your name: http://www.paulgraham.com/name.html and it seems I don't have the naming skills he talks about haha
Any advice would be super welcome :)
8 comments
[ 3.7 ms ] story [ 26.1 ms ] threadThere is a great deal of literature out there on product naming, but I think that it's all very squishy and it's easy to overthink the whole deal.
What I do with my products is to avoid getting too imaginative or fancy. I name my products in a straightforward way such that you know what the product fundamentally does by the name alone. For example, instead of naming a shopping list program "The Shopinator" or something, I'd be more likely to name it something like "<DBA> Shopping List Manager". Doing that also helps to keep you from accidentally stomping on someone's trademark.
It's worked well for me, but I have no idea if it would work well for anybody else.
[1] My business attorney insists on also doing a trademark search.
Peter Shallard "The Shrink for Entrepreneurs" didn't come up with that title. That's what his best clients were calling him.