aggie.beep
New member
US - Illinois
I have a client who wants me to develop a software application that will be utilized in a legal gambling situation for a casino and in some bar room situations. It amounts to an application that effectively becomes the ping pong ball chooser in a lotto game. (it's not that, but best way to describe it)
The application doesn't take wagers or pay out winnings etc. It's simply an application that generates a random symbol used for people to fill out bingo-ish type cards.
I'd like to license the software or receive a royalty for each location the software ends up being used.
Should the client ever have issues with the legality of their gambling situation, does this present a problem for me?
For example, does the fact that I'd be getting a royalty or license fee per installation mean that I am also liable due to it being a gambling related application in usage and my income was derived from sales of that application to a venue?
Also, is there a better way I might approach this, rather than royalty/license that would avoid this kind of risk entirely?
I have a client who wants me to develop a software application that will be utilized in a legal gambling situation for a casino and in some bar room situations. It amounts to an application that effectively becomes the ping pong ball chooser in a lotto game. (it's not that, but best way to describe it)
The application doesn't take wagers or pay out winnings etc. It's simply an application that generates a random symbol used for people to fill out bingo-ish type cards.
I'd like to license the software or receive a royalty for each location the software ends up being used.
Should the client ever have issues with the legality of their gambling situation, does this present a problem for me?
For example, does the fact that I'd be getting a royalty or license fee per installation mean that I am also liable due to it being a gambling related application in usage and my income was derived from sales of that application to a venue?
Also, is there a better way I might approach this, rather than royalty/license that would avoid this kind of risk entirely?
Last edited: