Just a question, I had a guy to do an Iphone app, now he tells me, as he is finishing that the codes has changed, and wants to charge me another $700 dollars. How true is that? I always think as a coder, you must code so that past versions do not come fully obsolete. Please let me know how true that may be.
I suppose the developer doesn’t have to code for past versions etc, there is no written law, however it’s just good practice and is what makes a good developer better from the rest. Was there any final contract you signed that can stop you from paying this charge such as a final list of requirements. Or was this just a random project?
This guy is writing the app from scratch. It has taken him about two months to finish it, but now that is almost finished (he has to test it, and we bought a developer account with Apple), now he says that Apple changed the codex, therefore he must charge more to make sure it works fully. We gave him a list of requirements, which did not change, and we only pay him half for the app, once he finishes he gets the rest, but now he wants more to finish it. How does that sound?
It depends on your contract. If you agreed that it would work under a certain version of the IOS then that’s all he is required to do.
Look at it this way.
You app works with IOS x.0 and he finishes the work and you sign off.
If he delivers the app fully functional is IOS x.0 he’s fulfilled the contract.
The next day, Apple releases IOS x.5 and your app no longer works….is that the developers fault?
Nope, you would have to pay someone to re-do the app.
If you didn’t anticipate Apple releasing a new IOS and didn’t build it into your agreement…that’s your problem.
Paulie, you are right. We ask of him to get the app working with Iphone, we did not say to make sure it works with future Iphones, we did not say that in the contract. Usually when I code a website, I do not sign off a website that will work with IE14 (which does not exist yet). BUT I code valid code so that in theory it should work to the best of our abilities.
We began the project about 2 months ago, there is not new Iphone yet, so in theory it should work in every Iphone for today. Right?
The question though, did something change from two months ago to today that requires us to pay him more to roll it out? Or is he BS-ing us?
I’m with where Paulie is going with this. It sounds like the much bigger problem isn’t a contract issue; it’s a trust issue. If you don’t trust what the developer is saying, this is going to go sour very quickly and can’t end good. So far I’m not reading anything shady in what you are describing, but then again there is only so much that can be conveyed on a message board. If this person gives you any reasonable doubt as to their integrity or if they are taking you for a ride, I would quickly work to validate those fears and either get over it (assuming you find nothing wrong with their work or intent), or find another developer. You can’t succeed without having communication and trust between the team of people working on a project.
I’d be pissed off if a developer slapped me with a $700 tax at the end of a project. To be honest, it doesn’t sound particularly good to me, but I have no idea how the project has gone thus far, what the contract looks like (if there even is one) and what the developer’s new constraints are.
You must be logged in to reply to this topic.