Most probably than not, this programmer can work a year more on this project and still not "finish" it in real sence. Specially if there was no specific finishing point mentioned in the agreement.

Software rarely gets finished. All these might be the programmer's point of view, just wanted to mention.

- They don't know how to write a specification. It's like asking a non-architect to draw you blueprints to a house. You end up with things like "there should be an arch here that's... um... about this tall".

- They don't actually know what they want 80% of the time. They will tell you (and you will document if you're smart) how they want it built, and when they see exactly that they will turn around and want it another way.

- They have absolutely no appreciation for how much work you're actually putting in. "But it's just a button on a page!". It's often insulting to work with people like this.

The spec for my contract changed constantly, and in the end took twice as long as I had anticipated.

And I still haven't gotten paid.

Maybe you're thinking about it in the wrong way. If you were to commission somebody to create a painting, you wouldn't paint over his or her name, scribble your own over it, and try to take credit for the work, would you? Even if you bought an unsigned piece of artwork for investment, you wouldn't go around telling people you created it, would you?

Sometimes it all boils down to something as simple as respect or attribution. If this desktop app is the next big thing, the coder probably just wants to at the very least make sure that he gets some kind of acknowledgment for his work. For some, acknowledgment can be as simple as ensuring nobody rips off their code and reverse-engineers it, and stamps a different name on it. For others, it is about monetary compensation.

I don't know what this dude's deal is, but of all the factors in your little moneymaking scheme, having the ability to write working code is probably the most valuable. 10 percent doesn't seem like a very equitable exchange.

But this software was planned out very clearly, there were some minor changes, but nothing big.

Im not sure why 10 percent doesn't seem like a good deal for him, he quoted me 2500 dollars, which is all he should get. Out of desperation and a desire to get the project moving and actually get some results, I offered him 10 percent when it was several months late.

That is really going to limit your flexibility down the road, so it is probably easier to just develop from scratch. Perhaps you should let him know you're disappointed with how things have worked out and are thinking about getting something simpler developed by someone else. Be honest and don't come across as personally critical and the discussion may push him to finish things, or break him of the mindset that you are trying to take advantage of him.

I outsource design work on a per-project basis, by the way, and like to ask people to let me know how long they take completing the work, especially since most of the time it involves iterating a couple of times. This approach lets me figure out what their hourly take-home is when all is said and done. If it ends up being too low, I like to increase it a bit more to build good relationships. Having reliable go-to people who can take care of problems on short-notice at a low cost is a lot more valuable than losing $20 here and there over individual projects.

What, precisely, is your "job title"?

Very very few can truly afford to "outsource" design. When you start adding metrics, time worked, etc. it's hubris. Your post started off OK but ended up badly.

When you use the words "take-home" in the same sentence as the word "hourly", you're violating some serious syntax.