I have a background as a developer and product manager. I'm looking to build the middleware and backend for my startup project and considering hiring an offshore dev for the iOS work. I've heard both horror and success stories and I'm hoping, so long as there isn't outright fraud, that tight technical specs and eyes on the code base will mitigate a lot of the risk. I'm hoping to get feedback from other technical folks in a similar situation.
Keep in mind that time zones will also play a large part in your development process. Do you have someone who can do a regular eyes-on code review, to ensure that it's being built properly? If so, why aren't they building it?<p>In my experience, things go really well in the beginning, during the honeymoon period, but as bugs start to crop up and the deadlines creep closer, things start to fall apart when you can't get hold of the people building it because they're asleep in their part of the world, or they refuse to fix something because their interpretation of those tight specs wasn't your interpretation of those tight specs. Make sure you are dealing with someone who speaks perfect English, too. If you can't really understand them in either spoken or written communication, or they can't understand you, don't write just it off, it'll come back to bite you when you have to explain something intricate.<p>caveat emptor.
I think you're coming at it from the right angle. The offshore devs I've worked with have always built <i>exactly</i> what I spec'd. That's been a good thing when my spec was thorough, and a terrible thing when I was expecting them to 'take this idea and run with it'.<p>So these days I articulate every detail I can think of and chop tasks down to their smallest bite size before shipping them overseas. It's more work up front, but saves to headache later on.