Re:Ask Us Anything: Y Combinator Hardware Companies Crowdfun...
by louprado on Tuesday March 15, 2016 @05:48PM
(#11293267)
Random IP lawsuits aside, there are known agencies/certifications/requirements, etc that may eventually require compliance. Here's the ones I know:
RoHS, CEC?, UL, FCC, Wifi Alliance, Bluetooth SIG, please add if anyone else knows.
I get that the OP is about pre-release startups and the general advice is "don't worry certifications; just ship". But this became a problem just 90 days after our product launch. Had the timing been worse it could kill a new company.
Re:Ask Us Anything: Y Combinator Hardware Companies Crowdfun...
by JonFish85 on Tuesday March 15, 2016 @06:03PM
(#11293363)
USB-IF, I2C (usually people will say "I2C-compatible", or Two-Wire Interface to avoid paying a royalty) are two others that come to mind immediately.
Edit: Basically any interface logos you use (stickers above ports) are probably owned by someone.
At least in my own work this has been something that pops up time & time again. Not only are there regulations that are tricky to nail down, there are things like intellectual property that you may not even be aware you're using. Build a blinking LED to detect activity on a data line? Wouldn't be surprised to receive a letter from a law firm. And unfortunately I don't know of any great ways to avoid the nasty surprise of receiving patent-backed threats. Personally I think this is why the big companies bulk up on patents, so that they can at least promise Mutually Assured Destruction against each other. For smaller companies & people selling products, you're probably infringing on some patent that they own without even realizing it.