3 ms·
99.9% of regular people think website = .com. All of the other TLDs are functionally equivalent to ThingApp.com (not Thing.app) or ThingIo.com (not Thing.io.)
by keiferski 6y ago
99.9% of regular people think website = .com. All of the other TLDs are functionally equivalent to ThingApp.com (not Thing.app) or ThingIo.com (not Thing.io.)
Choose whichever name works with a .com domain.
- gregoriol 6y agoAny non-direct name will work if your website is not your main entry point, something that people have to remember (for example if people should find you through app stores, ...); otherwise they will end up on some other site most of the time and you'll loose them.
- keiferski 6y agoYep, and in that case I recommend GetName.com, NameApp.com, or NameHQ.com more than a .app TLD.
- nerder92 6y agoThis is a very good feedback, as coming from a tech background myself I totally didn't think about that
- karmakaze 6y agoDo this, and don't worry about Thing.app or Thing.com. Make your company and domain bigger faster than similar domains and you will be able to afford it later. They might not even enjoy having a domain that's always confused with your product.
- vmception 6y agoas a corollary, nobody is typing in domain names, they click and tap on whatever was shared to them your entire service's web presence can live on an instagram account, it does not matter so although I am a proponent of using prefixes and suffixes, I'm also a proponent of obscure tld's or just not even bothering, and just hosting on github pages, you can even give direct links to cloudfront if you want focus on things that do matter which is revenue, this debate doesn't even matter