Take the 2-minute tour ×
Programmers Stack Exchange is a question and answer site for professional programmers interested in conceptual questions about software development. It's 100% free, no registration required.

I am just a developer and don't understand legal terms. Don't even know where can I go look for such answers. The problem is:

  • I want to implement some tools which are mentioned in a published book
  • I saw someone already has implemented it, and its priced at some X dollars
  • I think it should be available for free, and I want to make that available on Android as well

Please, suggest me what should I do, should I be seeking permission from the author of the book who invented the tools or the app writer who implemented already, or both?

share|improve this question
how do I move it? –  Gollum May 6 '11 at 19:16
add comment

migrated from stackoverflow.com May 7 '11 at 11:48

This question came from our site for professional and enthusiast programmers.

5 Answers

There are two legal issues you need to be aware of..

One is copyright law. The other is patent law. Both cover software.

copyright law means that people can't copy your direct output. So for software, the SOURCE CODE and IMPLEMENTATION is covered by copyright law. If the book you wrote included source code along with it, then the book owner is most likely the source code owner. When you take somebody else's efforts and use them for yourself, you may be violating copyright laws. You can use somebody else's source code IF they have given permission. Often that permission may come with strings attached (like attribution, or only for non-commercial use, etc). Those issues are dealt with by copyright law. Copyright usually lasts a LONG TIME! (till death+80 years?). Copyright is "automatic". You don't HAVE to register anything to get covered by copyright law. Just proof you wrote it and when you wrote it, and you are covered.

Patent law is different. Software can OCCASIONALLY also be covered by patent laws. US Patent law covers "processes", although I don't think the EU and other countries has the same level of patent coverage for software. A Patent owner has a limited monopoly. This is often for less time (7-20 years?) depending on where and what type of patent it is. Patent law covers the actual process USED, not the source code itself. Hence a patent is much stronger, because it covers all "embodiments". You can't just re-write the source to get around a patent.

Although patent laws are a mess. Software patents are even worse. They are expensive to get. And often by the time they approved (3-4 years?) the idea has already been replaced. For example: Amazon has a patent on their "One Click" checkout. No other website can implement it without paying a royalty, unless they come up with a whole new novel and non-infringing method. Or they can wait till the patent expires.

Mostly I tell people, don't worry about patents too much, unless you are already a major corporation (and then just listen to your patent attorneys). People only sue you for patent infringement after you are widely successful. Mostly because they don't get approved until the product is already in the market for YEARS. Heck, when you do get sued for patent infringement, congratulate yourself, cause it means you are some sort of business success.

share|improve this answer
that was a perfect answer :) . 10/10 –  Gollum May 6 '11 at 19:18
add comment

If the idea isn't patented, go ahead and develop your own app.

share|improve this answer
add comment

You can recreate anything you like. Issue arise when you start copying ideas directly. Although it is uncommonly know (so it appears), you can NOT copyright a 'idea', only a process or physical application of some sort (e.g. schematics, systems(highly detailed), etc). Meaning, you can create those tools to your hearts desire. You can not however, take the source code from said book and use it as your own (if you intend to sell.) Feel free to program whatever you like. As long as you created the source code from scratch, and have the original files to prove it. Then you will avoid most legality issues.

share|improve this answer
add comment

go ahead and implement. you should not copy the code directly... use the concept/idea and code it yourself. If you still wanted to thanks the author then acknowledge it.

share|improve this answer
add comment

Don't copy the code directly or implement the solution exactly like the author did. Create your own special thing, maybe even make it better and then make it free.

share|improve this answer
add comment

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.