> Second, if a client is going to withhold final payment based on Apple acceptance, there is no way I would work for them
But that was the requirement of the project, which the developer agreed to.
What enraged me is the behaviour of the developer.
But that was the requirement of the project, which the developer agreed to.
What enraged me is the behaviour of the developer.
Paying upon approval is ridiculous. I can request a developer write me an app with a buy button that takes the user to my website instead of using Apple's In-App Purchasing. That app would never get approved even though the developer wrote exactly what I asked them to. So I shouldn't pay the developer because Apple denied the app? And no, you shouldn't expect the developer to vet your design before starting development and alerting you of such problems unless you are paying for it. For $800, you are definitely not paying for it.
Well that's developer's problem, isn't it?
> I can request a developer write me an app with a buy button that takes the user to my website instead of using Apple's In-App Purchasing. That app would never get approved even though the developer wrote exactly what I asked them to. So I shouldn't pay the developer because Apple denied the app?
Yes, that's how contracts work. Welcome to the real world.
How is it your problem that the developer agreed to an impossible task?
Obviously not as the developer got full payment. It's both the developer's and client's problem.
"Yes, that's how contracts work. Welcome to the real world. How is it your problem that the developer agreed to an impossible task?"
Did you miss the part where the client wasn't going to get the app/code unless he paid? As soon as the dev said he needed payment or else the submission was a no-go, it became the client's problem. The "contract", if you could even call it that - good luck to the client trying to seek legal recourse with it, was poorly thought out. "Welcome to the real world."
https://www.inkling.com/read/wolters-kluwer-mbe-bar-prep/mbe...
That's just... not how business works. Milestones are organised such that the client can get the things he values with a reasonable probability. Even setting the milestones up as he did is risky, since the dev could just have decided to take 3/4, ship crappy code, and disappear into the interwebs. I guess in this case the client was relying on the reputation system of e-lance and the relatively small amount of money involved, but still.... when I read that he'd agreed to the final payment on such a flimsy acceptance clause I was ready to read a really bad end to this.
Not sure why people are emphasising the money so much. For a dev in NYC $800 is very little. For a guy in China that's a much better deal. Kind of the whole point of using e-lance, no?
So, all of my clients do.
It is the only way iOS development can possibly work.
Next time I buy some bananas at the supermarket, I'm going to tell the cashier that if my clients don't like them, they won't get paid and that they have to come with me to convince my clients that the bananas are perfectly fine.
If you don't think it's reasonable, why agree to the project?
> Next time I buy some bananas at the supermarket, I'm going to tell the cashier that if my clients don't like them, they won't get paid
That's a red herring fallacy, it has nothing to do with the situation we're discussing. The cashier has no contract with you, and didn't agree to anything.