Download (PDF, 329 KB)

Vungle Demo Ad in Where is that Place? Game – Vungle Selfpromo
Vungle Demo Ad in Where is that Place? Game – Ambiance App
Vungle Demo Ad in Where is that Place? Game – HOKM for Hustlers App

I already tried some facebook advertising my own and it was expensive and totally not successful. And I can tell you why: There are too many shady advertisers on facebook, which ruin the overall trust. And big brands can have exposure there whithout placing ads. So that will always be one revenue source, but Facebook doesn’t have users which search for information like Google.

I think given the widespread use of the Facebook Like Button, Facebook could establish a web-wide micropayment system. They already earn around 30% of their revenue with facebook credits. Advantage to Paypal would be, that I can pay together with friends, easily transfer funds to friends and that I am logged into Facebook anyway.

Brands could book coupons to facebook accounts for special promotions etc..

1. Clean Target, Clean Build Folder and delete Derived Data
2. Set Version to Release (especially if you have an Adhoc Build)
3. Use Static Analyzer to find obvious memory issues
4. Use Instruments to find less obvious memory issues
5. Use Release-safe versions of Apple-provided code templates. e.g. for persistentStoreCoordinator
6. Select a Release-Certficiate for code signing
7. When releasing for older devices: Build for armv6 and armv7
8. Check size is under 50MB (if possible) by exporting it as .ipa
9. Use your own version of NSLog, which is disabled for Release
10. Don’t use [[UIDevice currentDevice] uniqueDeviceIdentifier]. Also check third-party modules.
11. Check third-party modules for useful updates.
12. Enable Game Center, Leaderboards and Achievements in Itunesconnect
13. Send In App Purchases for review with your app
14. Make a copy of your development dir as a fallback solution, if some errors should occur in future updates
15. Don’t load too much in the AppDelegate, as startup time for an app is limited to around 20-25 seconds and you’ll get an “failed to launch in time” error. It only appears in Release and Adhoc Builds, not in debug Builds
16. For Push Notifications: Check if aps-environment is included in the mobileprovision file (just open with a text editor) and use the production certificate serverside. Create a new provisioning file, if not included.

This is work in progress and open for discussion. I will compile a nice PDF Version, if I think it is complete and I can find the time.

I included a nasty bug, which was caused by reliance to Apple provided standard methods and lack of cleaning derived data before archiving for the App Store. I use Core Data Model Versioning and somehow Migration didn’t work, so the around 1,000,000 users couldn’t use the app, when they updated. As I included ads for monetization I now had either users which couldn’t start the app or users which used the old version without ads.

I now cleaned up my persistentStoreCoordinator to support migration and have a fall back if that should fail for any reason. For reference this is the original method provided by Apple’s template in XCode.

- (NSPersistentStoreCoordinator *)persistentStoreCoordinator {
  if (__persistentStoreCoordinator != nil) {
    return __persistentStoreCoordinator;
  }
  NSURL *storeURL = [[self applicationDocumentsDirectory] URLByAppendingPathComponent:@"fbexclusive.sqlite"];
  NSError *error = nil;
  __persistentStoreCoordinator = [[NSPersistentStoreCoordinator alloc] initWithManagedObjectModel:[self managedObjectModel]];
  if (![__persistentStoreCoordinator addPersistentStoreWithType:NSSQLiteStoreType configuration:nil URL:storeURL options:nil error:&error]){
    /*
    Replace this implementation with code to handle the error appropriately.

    abort() causes the application to generate a crash log and terminate.
    You should not use this function in a shipping application, although it may be useful during development.
    If it is not possible to recover from the error, display an alert panel that instructs the user to quit the application
    by pressing the Home button.

    Typical reasons for an error here include:
    * The persistent store is not accessible;
    * The schema for the persistent store is incompatible with current managed object model.
    Check the error message to determine what the actual problem was.

    If the persistent store is not accessible, there is typically something wrong with the file path. Often, a file URL is
    pointing into the application's resources directory instead of a writeable directory.

    If you encounter schema incompatibility errors during development, you can reduce their frequency by:
    * Simply deleting the existing store:
    [[NSFileManager defaultManager] removeItemAtURL:storeURL error:nil]

    * Performing automatic lightweight migration by passing the following dictionary as the options parameter:
    [NSDictionary dictionaryWithObjectsAndKeys:[NSNumber numberWithBool:YES], NSMigratePersistentStoresAutomaticallyOption, [NSNumber numberWithBool:YES], NSInferMappingModelAutomaticallyOption, nil];

    Lightweight migration will only work for a limited set of schema changes; consult "Core Data Model Versioning and Data Migration Programming Guide" for details.

    */
    NSLog(@"Unresolved error %@, %@", error, [error userInfo]);
    abort();
  }

  return __persistentStoreCoordinator;
}

Even when using model versioning, it leads to this error, when you make changes to the model:

The model used to open the store is incompatible with the one used to create the store

So first thing is to include lightweight migration by providing the respective options NSDictionary:

NSDictionary *options = [NSDictionary dictionaryWithObjectsAndKeys:
[NSNumber numberWithBool:YES], NSMigratePersistentStoresAutomaticallyOption,
[NSNumber numberWithBool:YES], NSInferMappingModelAutomaticallyOption, nil];

if (![__persistentStoreCoordinator addPersistentStoreWithType:NSSQLiteStoreType configuration:nil URL:storeURL options:options error:&error]) {

I included that as soon as I turned on Model Versioning and it worked just fine in development, but somehow created a bug in the Release version, so I included a fallback, checking for errors:

      [[NSFileManager defaultManager] removeItemAtURL:storeURL error:nil];
      [__persistentStoreCoordinator release];
      __persistentStoreCoordinator = nil;
      return [self persistentStoreCoordinator];

This is the complete version of my method I am using now.

- (NSPersistentStoreCoordinator *)persistentStoreCoordinator{
  if (__persistentStoreCoordinator != nil) {
    return __persistentStoreCoordinator;
  }
  NSURL *storeURL = [[self applicationDocumentsDirectory] URLByAppendingPathComponent:@"jaysquared.sqlite"];
  NSError *error = nil;
  __persistentStoreCoordinator = [[NSPersistentStoreCoordinator alloc] initWithManagedObjectModel:[self managedObjectModel]];</code>

  NSDictionary *options = [NSDictionary dictionaryWithObjectsAndKeys:
  [NSNumber numberWithBool:YES], NSMigratePersistentStoresAutomaticallyOption,
  [NSNumber numberWithBool:YES], NSInferMappingModelAutomaticallyOption, nil];

  if (![__persistentStoreCoordinator addPersistentStoreWithType:NSSQLiteStoreType configuration:nil URL:storeURL options:options error:&amp;error]){

      [[NSFileManager defaultManager] removeItemAtURL:storeURL error:nil];
      [__persistentStoreCoordinator release];
      __persistentStoreCoordinator = nil;
      return [self persistentStoreCoordinator];
  }

  return __persistentStoreCoordinator;
}

I hope this is of any use for you and could save you some headaches. If you have further improvements I am more than happy to include them in the post.

Update: Now they published something on their site: http://www.youapp.cn/forum.php?mod=viewthread&tid=8990&highlight=bubbly

With Google Translator I can make a wild guess, but it doesn’t look that positive…