5 ms·
You’re probably right, but seeing that Google Meet isn’t enforcing its trademark on extensions used by tens thousands of people (“Google Meet Grid View”, “Googl
by xingyzt 6y ago
You’re probably right, but seeing that Google Meet isn’t enforcing its trademark on extensions used by tens thousands of people (“Google Meet Grid View”, “Google Meet Enhancement Suite”, “Google Meet Push to Talk”, etc), I’ll just keep the name.
- skybrian 6y agoBesides trademark confusion, there is also just plain confusion. For someone who hasn't seen it before, things get confusing when when the same product has multiple names. What do I call it? Which name is the important one? You don't want people to have to think about that. Is "Mercator Studio" another name for your product? Why make people remember multiple names? Something like "Mercator Mini Studio for Google Meet" would make sense if you want people to remember "Mercator" and search for that.
- xingyzt 6y agoThe code can be readily adapted for other web services that use the MediaDevices API, so I didn’t want to tie the name down to Google Meet. On the other hand, having a unique name is counterproductive to an extension which is dependent on another service. People search for Google Meet; I’d have to try a lot harder to get them to remember Mercator. “Mercator Studio for Google Meet” sounds like a fair compromise though. I’ll think about that.
- seanwilson 6y agoI'd be careful. On August 27, they're getting stricter on spam https://developer.chrome.com/webstore/spam-faq https://developer.chrome.com/webstore/spam-faq so don't be surprised if they start cracking down on this as well. "...for Google Meet" will probably be okay. They have specific examples like that here: https://developer.chrome.com/webstore/branding https://developer.chrome.com/webstore/branding
- xingyzt 6y agoGot it. Thank you both for the warning :]