2 similar iOS apps - what's the best way to manage them?

I currently have one iPad app, but now it needs to become two. The second will be more or less the same as the first, only with the addition of the login screen and the removal of some information on the main screen (and other minor adjustments). The vast majority of both applications will remain the same. The application as a whole is quite large and complex.

So ... My question is the best way to handle this? Are we discussing several goals in a project? Tracked branch in git? Perhaps an Xcode workspace with multiple projects?

The goal is to minimize cases where I have to change / add the same code in both applications in the future and still make it simple for any developer to create any version of the application.

Any help would be greatly appreciated, thanks.

+5
source share
2 answers

This is a very similar issue with this common one , where you have a version of the Full and Lite application that shares most of their code.

I will also post a link to this tutorial , which I did not see, related to another question I referred to, The tutorial is for Xcode 3, but it is not too difficult to use the same concept in Xcode 4.

Yes, I would use two targets in one Xcode project.

+4

, , , , , , . 2 . , , !

+1

All Articles