xcode - Should I being using one project with multiple targets? -

i building several different video poker apps. 1 app jacks or better version of video poker. others include deuces wild, royal aces, 10's or better, etc. i've built royal aces version , want make 10's or better version. should using royal aces project , setting different targets other poker versions? since reusing 95% of of code, want simple way of doing this.

if should using different target each type of video poker app, i'm assuming each target can have it's own: bundle id, app name, etc. way can archive each video poker target separately , upload each separate binary.

am correctly understanding how can use different targets? correct way , efficient way of accomplishing task?

first note apple tend frown on having many versions of appears same app, , may start rejecting apps after awhile (which can frustrating once you've started down route). may have smoother sailing if bundle game differences data (rather code), , sell them in-app purchases rather individual apps (or focus on ad revenue instead, , use number of games differentiator rather sales revenue).

that said, it's app, let's question.

multiple targets fine, , convenient kind of setup. things you'll want do, though:

• first, recommend shared xcconfig file don't have duplicate build settings between projects. see:
  • how can use .xcconfig files in xcode 4?
  • http://respectthecode.tumblr.com/post/16167385557/xcode-4-and-xcconfig-files
  • i have older (and dated) tutorial: http://robnapier.net/blog/build-system-1-build-panel-360
• you may want build shared code static library , link against app-specific code. save lot of compile time when build packages, particularly if there many of them.
• i think lot testability of core on. testing every version of game every time make change royal pain. automated testing of shared code huge win.