How to make an indie app to &quot;belong&quot; to the legal company? Lets say I have a created an app that I now want to start a company for. Company will be a 1-person company who's only product will be this app. What will define that from now on the app's intellectual property belongs to the company? Is it a license agreement, website, patent, trademark or anything else?
There are basically two kinds of things one could do. One could assign or transfer intellectual property rights and contracts related to the app to the entity, or one could license the intellectual property rights to the entity. Generally speaking, in a related party transaction, everything should be in a signed writing, and a notice of the transfer of an intellectual property right that has been registered or filed with a government agency should be provided to the government agency in question. Since there are potentially copyright, patent, trademark, publicity, and contractual rights that might be associated with the app, each aspect which exists should be transferred or licensed, as the case may be. While the forms to do this aren't particular long, the concepts involved and correct terminology are subtle, so this would not be a wise undertaking to attempt on a do it yourself basis.
Contracts are a relationship between two or more people Just as it is meaningless to speak of marrying yourself, it is equally meaningless to speak of a contract with yourself. Even if you were to draft such a thing, you would not have standing to sue because you can’t sue yourself. Your example probably isn’t a “one person contract” It’s a contract between the car owner (person 1) and the car yard (person 2) - probably a corporation. The fact that person 1 is representing both parties to the contract doesn’t make it a “one person contract”. There are potential conflicts of interest with this but they are not necessarily ones that can’t be overcome. However, if the car owner runs a business as a car dealer as a sole trader, then, no, they cannot make this kind of contract.
"There is a free mp3 app from a friend who asked me to publish it in my account, which I didnt check properly." You violated Google's policies by uploading an App that you did not have full control over and/or was not developed by you. As well, the App possibly violated Google's policies in terms of violating licensing for code libraries that were included, had code included in the App that was malicious or violated privacy, or was otherwise not compliant with Google's terms. Google's policies are legal contracts which you agree to when you open an account. You reserve the right to end the contract by deleting your account. They reserve the right to end the contract when their policies are not followed. See https://play.google.com/about/developer-content-policy/ "This sudden termination comes as a shock and Google's decision seem very rude to me." You may think it is rude, but Google is fully within its rights to terminate your account because you violated their terms. It matters little that you did not get the previous warning emails from Google; you are responsible for monitoring the account email for policy updates. If you’ve reviewed the policy and feel this termination may have been in error, please reach out to our policy support team. Try that; you might attempt to explain that it was honest error on your side.
If you have an agreement with a company that specifies &quot;you agree to give me something of value, in case I give you something of value&quot;, you have a contract. In order for there to be a contract, there has to be actual acceptance of the offer. You can put out on a web page some contract stating those terms, and if you get positive acceptance of the contract (hence the standard click-through technology), then as long as you have done the thing promised, you can bill them for doing the thing promised. It's not clear what thing of value you are offering on the web page, since it's not &quot;doing actual work&quot;. Them sending you an email isn't you doing something. One thing you could do is block all incoming emails, and for money you agree to unblock emails from registered subscribers. Just announcing that you will bill anyone for emailing you does not create a contract, because the emailer need not have even seen your announcement. This is why e-contracts need a click-through button. It's legal to request money, but there is no legal obligation for them to comply. That will be $10, please.
If you want to implement this or a similar feature, you'd look up the patents, and either get a license (unlikely that Microsoft would give you a license), or figure out how to implement the feature without violating the patent. An example how a company I worked for worked around a patent: In order to compress data. in the best possible way, the idea was to try eight different methods to compress the data and pick the best compressed data. There was a patent for that (even though to me, this was quite obvious). Workaround: The software tried eight different methods and reported a number from 1 to 8 indicating which method gave the best result (unlike the patent, which actually gave the best result). Then the data was compressed once using the best method. No patent violation. You'd probably want a patent lawyer to check if your idea how to implement the feature violates the patent or not, and how to get around it. It takes a specific mindset that you and I don't have. And even good lawyers who are not patent lawyers might not be able to help you there. Commercial vs. open source/free software makes no difference, except that Microsoft might not bother suing you if there is no money to be made. Unless the intent is to prevent you from implementing the feature, in which case the would sue companies without money as well.
You can't patent an algorithm, but I'll assume you are talking about the case where you have patented a machine or process that uses an algorithm, but that adds significantly more, and that the software being distributed implements much of this process. Courts might find an implied licence or promissory estoppel when distributing software under an open source licence that doesn't explicitly exclude patent licencing as part of its terms. It would be prudent to state your patent rights and explicitly exclude a patent licence if you intend to enforce your patent rights. As an example, this software implicates a patent , so they allow "permission to use, copy, modify, and distribute this software and its documentation for educational, research, and non-commercial" purposes. Users that want to use the software commercially need to contact the authors who also happen to be the patent owners, and I assume would negotiate a patent licence at that point.
With respect to the first question, discussing an idea in a non-encrypted email is not a publication that forfeits the right to patent an idea, even though it is not 100% secure. In the same way, talking about an idea for a patent with your patent lawyer in a secluded booth of a coffee shop in person does not constitute publication of the idea for this purpose, even if someone is secretly spying on you at the time. Since I am at the moment employed by a company, even though the idea originates from myself, it seems that I should quit my job first not to have my current company have any claim over my idea. It is possible that the contract makes even ideas that you come up with yourself while employed by the company the property of the company. If so, you are legally in the wrong and the idea belongs to the company. But, proving the reality that you are stealing the idea from the company is harder if there is nothing in writing. An email discussing an idea while you are employed would have to be disclosed in litigation with your employer over whether the patent applied for belongs to you or to your employer under an employment agreement. If you didn't put it in an email, it wouldn't exist to turn over in litigation.
The software being free and open source has no impact on whether it infringes any patents or violates any copyrights. Copyrights attach to fixed representations of creative work in a tangible medium (e.g., the actual code and graphical elements of the software in question). As long as you aren't copying the copyrighted work of someone else, you should be in the clear. So, if you write your own code from scratch, or rely on code that you're allowed to use (e.g., "free" software with a permissive license that allows it to be used freely), you should be fine. On the other hand, if you copy a chunk of code that you aren't allowed to use, and then change the variable names so that it's superficially different, you're likely violating someone's copyright. Patents are a much more difficult question. To determine whether you would infringe any patents, you would have to read the independent claims of every patent that might be related. If you perform all the steps of any one of those claims, then you are infringing that claim (and therefore, the patent in which it is found). Unfortunately, this is much easier said than done. First, it may be difficult to search for all the potentially relevant patents, and once you've found them, there may be far too many to read. Second, claims are written in a type of language that is specific to patents, and someone without experience in patent law may not understand them correctly. Finally, the terms in the claims may not take on their plain English meaning, but rather may have been defined by the language in the rest of that patent, so it's possible that you might incorrectly think you were in the clear based on a misunderstanding arising from that. All that said, it may be best to go ahead with implementing an idea and then waiting to see what happens. Chances are that the implementation will arguably infringe some patent in some way, no matter what's done. But chances are also high that there will never be any worrisome enforcement action taken against it by a patent owner, simply due to the difficulty and expense associated with enforcing patent rights.