|
|
|
|
|
by t_hinman_esq
604 days ago
|
|
Hi! I am a startup attorney -- of course I can't give you specific legal advice here, but Mindcrime makes some excellent points! Many states have explicit laws that protect employees from having to assign IP that they have developed on their own time, with their own resources. If you live in CA, CA is a very employee-friendly state and any restriction on competition is generally against public policy. Without having seen any of your agreements, I would say that if you work on a project on your own time, with your own resources, it is unlikely that will run afoul of your employment restrictions. In addition, staying away from your employer's bread-and-butter revenue streams is also just generally good advice if you're trying not to draw attention or make people angry. ;) Happy to chat more if that's helpful! |
|
The app itself is similar to a module of a much larger product the company sells, but that product is far from being a money-maker for the company (may just break even). People are certainly not buying the whole product because of that module, it's a nice thing to have. There are several other companies that do sell stand-alone apps similar to mine though, there is a market for it.
The other concern was whether starting now the work based on the MIT open-sourced version of my app creates a clean slate for me, since the previous work was done in part during work hours on their PCs. Open-sourcing the app through my employer was the only way not to lose it completely in case I switch companies, and have a chance to try a startup based on it.
Some advice I've got was that forking the OSS version should be done by a friend (not in the company) and I should work on it in the background and officially join later, after I quit - that also feels sketchy.