-The pitch line makes it sound like it assesses the 'quality' of the name rather than it's availability/similarity. I was expecting something that would 'rate' a name based on some kind of popularity or sentiment score.
-Im not really a fan of the name, which is a problem that stands out when your product is about good names. "Namegine" parses strangely, I think my brain's looking for another "n" to complete the word "engine" and keeps wanting to pronounce this word "Namm-Egg-Inn". Honestly, I think just NameEngine would be a better name. Obviously very subjective though.
> -Im not really a fan of the name, which is a problem that stands out when your product is about good names. "Namegine" parses strangely, I think my brain's looking for another "n" to complete the word "engine" and keeps wanting to pronounce this word "Namm-Egg-Inn". Honestly, I think just NameEngine would be a better name. Obviously very subjective though.
Absolutely, at the risk of bike shedding, for a German/English speaker this parses really strangely. The parent comment nailed the problems I have looking for another missing consonant.
> -Im not really a fan of the name, which is a problem that stands out when your product is about good names. "Namegine" parses strangely, I think my brain's looking for another "n" to complete the word "engine" and keeps wanting to pronounce this word "Namm-Egg-Inn". Honestly, I think just NameEngine would be a better name. Obviously very subjective though.
My mind jumped to pronouncing it as Name-Genie, thinking it was a reference to a genie in a bottle that would spit out a startup name for you.
> thinking it was a reference to a genie in a bottle that would spit out a startup name for you
I thought the exact same thing. I was surprised when it asked me to type in a name. Wary of what would happen next, I used the name of a competitor! :-)
Thanks, that was our intention indeed. Yet, the comments above yours made us realised that there is a long way ahead of us with building a great product.
I beliebe that idea is only a couple of % of the new venture. People and their ability to execute is the vast majority of any business success. You know, no one would pith in front of the investors if they were afraid of being robbed by investors. Eventually our mission is to protect our users IP, not steal it from them...
It's nice to meet competitors. We have run the name against trademarks databases. The product was not ready when we registered our domain, but that's valuable feedback, to look out for similar domains.
And to echo another question in the comments, how is the name pronounced exactly? On reading it, it seems "gine" is likely pronounced "jin" or "gin" as in "engine".
Slightly related, I made this name generator that will make up words so you are unlikely to run into something that already exists: https://github.com/kristiandupont/conkyte
It uses a couple of different techniques, I'd love to add more if you have any!
Very cool, I want to dig a little deeper into that when I'm not on mobile. That was spitting out some of the best generated names I've seen, they weren't all good but they were all pronouncable for an English speaker.
Thanks for the comment. Sorry to disapoint you but the names you see in the first section of our tool are not generated names. These are the names of similar names already registered as a trademark with United Stated Patent & Trademark Office. So you can check if there are any conflicting trade names (trademarks) to the one you are searching.
In the few seconds I used it, it was pretty frustrating trying to copy a 'word' as it scrolled up rapidly. Consider implementing a way to pause (or delay) generating new words.
We run it on Heroku on production quality dynos. Heroku came out to be a bottle neck. Moving things to lambda is an option we will seriously consider. Checking for, Twitter as well.
What happened then? It was able to serve the site but not do API calls, so no mem-cache in front of your database? The Redis mem-cache didn't flush itself when full?
The site is served via AWS CloudFront. It is SPA app hosted on S3. The API is on Heroku. No mem-cache anywhere. To search we use ElasticSearch hosted on AWS. We bump up the specs to speed it up but that was not the core problem.
I suspect Heroku Postgres DB. We didn't used some Hobby version and I think it is the real bottle neck + some unnecessary middleware for the API that also requires DB.
DB's have limited connections and are often billed as such, the mem-cache might help if there are any repeatable things. It might not be useful for your solution though since everyone searches for their own things all the time.
I tried it on my mac ( looked good) but as you/your teammate reported, it is having issues getting data back from the API, every call is returning a 502
Not my area of expertise but it would be functional if I could just resize it. It seems locked on this zoom level. But I’m of the opinion that desktop UI on mobile is just fine because I know how to zoom, if I’m allowed.
I'm not sure what facebook availability means - the term I searched for says "available" but the account name is taken. Does it mean something else (page name? I'm not very familiar with facebook..)
Idea: once you have a steady stream of users, automate some domain name squatting. Buy the cheap ones (.xyz, .website, etc.) for every name, then threaten submitters with libel blogs unless they pay up.
Although I am sure your intentions are pure, he raises a valid point. I think you'd benefit from making it apparent that "we won't steal or squat you name" somewhere on the landing page.
I think it's a fantastic idea, keep up the good work.
You forgot to add the Access-Control-Allow-Origin header to your api:
Failed to load https://api.namegine.com/api/v1/*: No 'Access-Control-Allow-Origin' header is present on the requested resource. Origin 'https://namegine.com' is therefore not allowed access. The response had HTTP status code 503.
We had API cached by ClodFront. In the process of troubleshooting we turned it off and we attached frontend directly to API. There should be CORS headers though. The problem was more scalability problem. It's too soon to say for sure, but getting rid of some middleware and scaling Heroku Dynos helped.
I love the idea! Everybody has projects (for fun, hobby, or serious projects) and you see it all the time were the name is already used by [insert other large library/project] or it translates poorly in another language [becomes the word "poop" or something].
This worked perfectly for me with a couple of project names I've got. Was glad to see no one trademarked it and the words mean about the same thing in most languages. So thanks!
FYI: div.contactUs panel that says "Interested in Trademark Registration" is covered by the namesearch-Hintcontainer with its z-index of 500. It also gets especially screwy on narrow screen width, and obscures the footer text. So I hope you can make some quick CSS adjustments there.
I love this. With the excessive use of dictionary words it's nice that there is now a way to search so that hopefully people will stop naming projects "Hydrogen" since there are 376 pages worth of results for it. lol
Tried from Firefox this time. This is what I got →
"Secure Connection Failed
An error occurred during a connection to namegine.com. SSL received a record that exceeded the maximum permissible length. Error code: SSL_ERROR_RX_RECORD_TOO_LONG
The page you are trying to view cannot be shown because the authenticity of the received data could not be verified.
Please contact the website owners to inform them of this problem."
Same, completely broken in both android Firefox and brave. Worked in brave desktop mode, unusable entirely in Firefox. Plus, it didn't seem to offer much utility over a Google search for the name under consideration.
-The pitch line makes it sound like it assesses the 'quality' of the name rather than it's availability/similarity. I was expecting something that would 'rate' a name based on some kind of popularity or sentiment score.
-Im not really a fan of the name, which is a problem that stands out when your product is about good names. "Namegine" parses strangely, I think my brain's looking for another "n" to complete the word "engine" and keeps wanting to pronounce this word "Namm-Egg-Inn". Honestly, I think just NameEngine would be a better name. Obviously very subjective though.