2

I want to provide two versions of my iOS app: paid and free with ads. My goal is to keep the code base the same and change only a flag to indicate which version I want to build.

I've prepared two build targets for my app to support this separation, as described here. These targets differs in Bundle ID.

Now, I'd like to change the flag based on given Bundle ID. I've tried to read main bundle identifier and it worked perfectly. And here my question starts.

Is it possible to change the main bundle ID after downloading the free app to get an unauthorized access to paid version? I found here, here and here that it isn't.

But... what about jailbroken phones? I've read in some comments, it is.

If so, how can I protect my app?

I was also thinking about defining preprocessor directive like #define FREE_APP. Then I'd check:

#ifdef FREE_APP
    //show ads
#endif

But this solution can't be totally automatized just by selecting build - I'd still need to change this value manually - so it isn't the best. Will be grateful for suggestions.

Community
  • 1
  • 1
Marcin Świerczyński
  • 2,302
  • 22
  • 32

1 Answers1

3

To directly answer your question, almost certainly yes. But I would argue that it doesn't matter.

The people who want to pirate your app would probably just wait until someone bought and cracked your paid app; I doubt they'd go through the hassle of hacking your free version.

Personally, I have two targets in my project. The two apps have different Info.plists and the free version has a #define in the build settings. In my code I have lots of #ifdefs as you suggest. It is possible to automate (but it can get a bit messy at times).

Of course, your other option would be a single app with an InAppPurchase to upgrade to the full version. Just be careful of patent-trolls.

Stephen Darlington
  • 51,577
  • 12
  • 107
  • 152
  • You're probably right - it'd be easier to wait. I just don't want to make creating a crack ridiculously easy :) Just one more question - what do you mean by "free version has a #define in the build settings"? How did you put the define inside build settings? – Marcin Świerczyński Jun 07 '11 at 14:32