I'm developing an iOS app, it's just an app and two goals (app and test).
With the proximity to publication, I want to split this app into three applications and think about the many shared code and shared tests (the App Store and the prototype app for the free version and full version Which will not be published).
Will you set up multiple projects in Xcode (1 Library Project and 3Ap Projects) or will all put together projects and set up multiple targets only?
I think you have at least 3 options here:
-
Separate projects are more difficult to share codes in projects, but with the Xcode workspace it is quite feasible. If you have a lot of customization for each project, then this could mean
the same project, the more goals in the normal way is done. This is very easy because you have a very accurate overview of which files are in the target. If you are around, say, a dozen or so goals, it's really easy to handle.
Different gate branches I have worked with it in the past, the difference between apps (Info.plist, configuration files, data files) is just git Swaps in the branch It is practical if you have too much data and it is not necessary to be available at all times. However, the complexity of GIT is very important if you are not familiar with it. You can create git submodules to change the shared code parts at once.
No comments:
Post a Comment