0

I have a number of apps (about 16 at the moment and growing) which have pretty much identical code. That is the code that drives them is the same.

There are a few things that change between apps, they are:

  • A PDF file (inside the bundle)
  • The icon
  • The name
  • 4 Storyboard screens

As you can imagine it would be a nightmare to maintain 16 independent projects, my main concerns is that Features/Bug fixes in the main code will have to be applied 16+ times. The other thing is actually building and pushing 16 different binaries to the app store.

At the present time (Jan 2014) I want to know if there is a way to do this easily so that I only have to make a code change in one place and the 16+ other projects are updated and pushed to the store.

I have thought about git, or just having 16 projects and writing a bash script to do it for me but that seems dodgy. What is the most elegant solution to this problem that will reduce my overhead?

p.s. I don't want one app with 16 different icons/pdf due to size reasons

p.s.s. Please don't make as a duplicated, I want to know what solutions are there today, not a link to a slashdot question from 2010 :P

ddoor
  • 5,819
  • 9
  • 34
  • 41

2 Answers2

2

You could create a project for each app (so you won't have to change the project settings, e.g. name, icons, bundle identifier, ...) where you add the different PDF files and setup the storyboard screens.

Then you would create the classes in one project and drag & drop the files to the other project but uncheck the Copy items into destination group's folder option. That way you can change the code in any of the projects and it will be updated in all of them. You still have to build and submit each project on its own.

Hannes
  • 3,752
  • 2
  • 37
  • 47
  • Yes I wouldn't have bothered asking if that was the solution. I want to do it without doing it manually. This is prone to error etc. – ddoor Jan 06 '14 at 03:04
  • 1
    Why is it prone to error? If you change the code in any of the projects it will be updated in all of them. Or do you think so because you have to build/submit each project? – Hannes Jan 06 '14 at 03:06
  • Its prone to error because its manual, so its easy for me to miss one. The less human-factor involved the better. When you run a business, simply copy and pasting 16 sets of files can be risky, because if the phone rings then I lose track etc. It still seems very time consuming, I could just put the cp into a bash script though i suppose – ddoor Jan 06 '14 at 03:13
  • Just re-read that is actually a really good idea. Sorry about that. would +1 but the site won't let me :( – ddoor Jan 06 '14 at 03:30
1

You can create one Xcode project file, with multiple targets. Each target in the project can have its own plist, icon, PDF and etc. Everything else will be shared and in one place.

hotpaw2
  • 70,107
  • 14
  • 90
  • 153