I need an iPhone app built and at the moment it's looking like it would be best if a few developers worked on it. Is this possible with an iPhone app/what would be the best way for everyone to work vaguely together so that it can be all put together at the end?
Cheers!
EDIT-People will be spread out, maybe over the world, or at least around the country. At the moment, it's in very early stages, so no, I don't know who they will be-I won't know them personally either when it comes to it.
XCode supports use of version control - CVS, SVN, and Perforce
I will say though, from personal experience though the CVS support is really, really shitty. But for a new project you should be using SVN instead of CVS anyway.
It's possible, I suggest you use a free web-based source control provider, such as xp-dev.com (for Subversion).
Since you will be working with a widely spread team, have a look at google code
Working with a team on an iPhone App will be much the same as any other distributed development project. It'll be easier if everyone is a registered iPhone developer, so they can test and debug on actual hardware.
Other than that, you'll need the usual stuff - a public code server, a mailing list, and an issue-tracking database. Don't forget a set of specifications for the interfaces between code modules - that's probably the most critical component to allow concurrent development.
I have found that these tools and apps have helped me and my team with collaboration with iPhone development and other software projects.
Having the right tools and knowing how to use those tools effectively can make or break a team, and define whether or not the application is successful or not.
Version Control
First, the utmost tool/application that should be used is Source Control. I can't stress Source Control enough. Use some form of Source Control even if you're a one-man team or the only person working on the project.
I would highly recommend http://subversion.tigris.org/ it is platform independent and is highly customizable and flexible.
Defect/Bug Tracking
Second, your team is going to need some formal way of logging defects and tracking bugs/software issues. Having a bug tracking system in place allows your team members to be on the same page as to what is known as issues within the application. It also allows better management and assignment of defects/bugs which results in a higher level of productivity.
If you're a small team and don't want alot of overhead for a bug tracking system. I would recommend using http://www.mantisbt.org/
Standardize Documentation & Software
Third, having your team come to an agreement of what type of documentation and software creation tools you decide to use is a major issue that should be addressed before any type of work is invested into the project. I would suggest to always go with an open-source, open-format that is available across different platform O/S's.
Word Processing, Data Sheet, Graphs
Graphic design
Animation design
Hope this list helps... as always you should always use tools and software that best suites your needs. These suggestions don't apply to everyone. But as a startup company keeping costs as low as possible, and using software that results in a more productive environment is always important.
Good luck !!!