9 {{ upvoteCount | shortNum }}
9 {{ upvoteCount | shortNum }}

How to Get a Software Application Built

by BigFrank Banned
7 replies
Greetings,

I need help understand the legal and ethical challenges that one encounters when attempting to develop a piece of software from scratch. I use a desktop application that most users probably utilize at around 20% of what is built into the app. For argument's sake, let's say that software package has two distinct but interrelated functions, but that the majority of the users only use one of them.

I would like to have a piece of software built that contains the 20% of what most users use the app for as well as add some features that I feel are overlooked in the current product that I use.

So - these are my questions:

1. Ethically, is it wrong to show a potential developer the product that I am currently using, while explaining what I want and don't want in my product?

Or, should it all be written out in longhand?

2. Since I can't tell the difference between a line of code and a line from the Dead Sea scrolls, how can I be assured that the coder has not used any of the code in the product that I showed him/her? I don't want any legal issues cropping up, later on.

Getting answers to these two questions will help me form more questions going forward so that I can pursue this with a reasonable amount of precaution.

Any help you can offer will be greatly appreciated.

Cheers. - Frank
#application #built #software
  • Profile picture of the author BrianJM85
    1) All requirements should be written in a clear and concise manner. Provide as many details as you can so that there is no confusion. If you do not have the requirements in writing, you cannot guarantee the results of the project - you have not way to prove who was as fault. The biggest mistake you can make in software development is not having well defined requirements.

    2) You have 2 options I can think of:
    • Don't show him/her the code. Why are you doing this anyways?
    • Hire a developer you can trust.
    {{ DiscussionBoard.errors[9749244].message }}
    • Profile picture of the author BigFrank
      Banned
      Originally Posted by BrianJM85 View Post

      1) All requirements should be written in a clear and concise manner. Provide as many details as you can so that there is no confusion. If you do not have the requirements in writing, you cannot guarantee the results of the project - you have not way to prove who was as fault. The biggest mistake you can make in software development is not having well defined requirements.
      Understood. Thank you.

      2) You have 2 options I can think of:
      Don't show him/her the code. Why are you doing this anyways?
      My intention was to not show the code, but the actual product I use. Having a first-hand view of what I'm after would be very hard for me to just put into words. It's an audio project and I'm not even well versed in much of the terminology.

      Hire a developer you can trust.
      A lofty goal, but when you're new at this, it's a crap-shoot.

      Thanks, again.

      Cheers. - Frank
      {{ DiscussionBoard.errors[9749269].message }}
  • Profile picture of the author BDazzler
    Start with an NDA. There's nothing wrong with explaining what you do and do not want and comparing it to another, competing program.

    If the programmer in question was involved in the development of the competing program, you could have an issue. If you use screens and trademarks from the competing program, you could have an issue. If you violate a patent of the competing program you could have an issue.

    It really depends on the license of the software you are considering competing against.
    {{ DiscussionBoard.errors[9749551].message }}
    • Profile picture of the author BigFrank
      Banned
      Originally Posted by BDazzler View Post

      Start with an NDA. There's nothing wrong with explaining what you do and do not want and comparing it to another, competing program.
      Makes sense.
      If the programmer in question was involved in the development of the competing program, you could have an issue.
      I doubt that would be the case as the current owner and seller is the coder.
      If you use screens and trademarks from the competing program, you could have an issue. If you violate a patent of the competing program you could have an issue.
      Not really my style. :-)
      It really depends on the license of the software you are considering competing against.
      I'm sure that the current software would never be considered competition. Theirs is a Jaguar and I'm looking to build a VW Beetle, which would meet the needs of most of those forced to purchase hundreds of features that they have absolutely no use for.

      Don't think of it as trying to build a better mousetrap, more like a simpler, much less expensive one. :-)

      Cheers. - Frank
      {{ DiscussionBoard.errors[9749602].message }}
  • Profile picture of the author mydream247
    Hi Frank, I saw this WSO about developing plugins, maybe can help you. No I am not an affiliate. Just sounded useful based on all the reviews.

    Good Luck to you,
    {{ DiscussionBoard.errors[9749574].message }}
  • Profile picture of the author BDazzler
    I bought that WSO ... it won't address the specific issues that Frank asked about.
    {{ DiscussionBoard.errors[9749578].message }}
  • Profile picture of the author javrsmith
    There are a lot of examples where code was written to emulate other products. The operating system Linux comes to mind. They wrote it to do exactly what the commercial product did and never looked at a line of code. The requirements were to duplicate function, not the design.
    You should be OK, but get the non-disclosure agreement set up.
    {{ DiscussionBoard.errors[9761298].message }}

Trending Topics