How to organize the collective development of an application for iOS?

Ilya Reznik2012-07-09 21:33:18

iOS

Ilya Reznik, 2012-07-09 21:33:18

We decided to start developing one not a simple application for iOS. But since never done this before - new to us. And one question arose: how to connect the work of two or three iOS programmers on one application?
Share your experience, please, who knows how to properly organize application development.
By the way, there is a vacancy for an iOS programmer. Worthy pay :)

Answer the question

In order to leave comments, you need to log in

8 answer(s)

Ivan, 2012-07-09
@cohe4ko

Use a git server. xCode is very friendly with him. And it's very convenient. The main thing is to stipulate the rules of commits in the team. And do them regularly, then when conflicts arise, it is easier to resolve them.
Implementation options:
1. Linux (CentOS 6.2, Debian, etc.) + GIT + gitolite + gitlab get an analogue of github, only everything is at your disposal.
2. use services like github.com, unfuddle.com
SVN is a thing of the past.
I myself used the 2nd option at first, later switched to the 1st, because there were a lot of projects, and a paid account became more expensive than buying a computer and setting everything up fine.

Dmitry, 2012-07-09
@DedalX

That's right - set up SVN on your server, and everyone can work with it and do the work in a modular way (each its own module).
But as you know, there is not always time for the right thing, especially when the work is on fire, so they often used DropBox to exchange changed files, while everyone did their part of the work (different people worked with different classes, after making important changes they exchanged .m and . h class files).
In both cases, they worked remotely. And if everyone is in the same office, then right there you can deploy SVN on one of the computers and it will be easier to work.

Andrey K, 2012-07-10
@Coder89

Our bundle: Skype + Git + Basecamp + DropBox + TimeDoctor = Happy!

zoo, 2012-07-11
@zoo

bitbucket + Skype conf + dropbox

Sergey Lerg, 2012-07-10
@Lerg

We use bitbucket - everything is fine. Mercurial + MacHG. Basically, make the application as modular as possible so that each programmer can solve the problem within the framework of his module.
There, on bitbucket, use the Issue Tracker or maintain your own.
And of course, everyone should be able to quickly test on the final device.

Krypt, 2012-07-10
@Krypt

Likewise, Mercurial (own) + Mac HG. It is desirable that the edits be in different files (we use MVC, so there are no special problems with this) - it eliminates the puzzle over merge.

Ivan Ushakov, 2012-07-12
@ulmolot

Skype + git(github) + trello + Basecamp

strobegen, 2013-12-29
@strobegen

git is by itself (bitbucket is the most obvious solution here), and there is also an osx server (right now they are giving it away for free to participants in the ios dev program) in which there is a native tool for continuous integration of xcode projects - accordingly, if you start a dev server, you can set up an automatic build project from git repository