[wislon]

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?

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.

caveat emptor.

[relaunched]

I can do some level of review, but I don't have stylistic preferences in a language I don't really write in, nor am I familiar with the nuances of the language / libraries to know what I don't know. For an MVP, I'm hoping that it serves the primary use case(s) without breaking too badly.

I'm sure this isn't a great way to do it, but I'm budget constrained and want to get something to market to start getting feedback.

[nsp]

Have you looked at any of the backends as a service? E.g. Firebase/parse or self hosted alternatives like hood.ie? As somebody who writes backends in my day job, I've found them to be a huge time saver on Mvps and reasonably capable.

Hit me up at [e-mail] if you want to discuss the space/your options