danielrhammond

Answer by Daniel Hammond:

Using log statements liberally in development is fine, but you really want to remove those from production, we use a log macro like:

1 2 3 4 5 6 7 8

#ifdef DEBUG

#   define DLog(FORMAT, ...) printf("%s %s ~ %s\n", [[[NSDate date] description] UTF8String], __PRETTY_FUNCTION__, [[NSString stringWithFormat:FORMAT, ##__VA_ARGS__] UTF8String])

#else

#   define DLog(...)

#endif

// ALog always displays output regardless of the DEBUG setting

#define ALog(FORMAT, ...) printf("%s %s ~ %s\n", [[[NSDate date] description] UTF8String], __PRETTY_FUNCTION__, [[NSString stringWithFormat:FORMAT, ##__VA_ARGS__] UTF8String])

spenrose/gist:4539571 A couple things here: 1. Uses printf which is faster than NSLog 2. Prints out a timestamp and description of the function where the log came from which helps you pinpoint problems 3. #ifdefs it to a no-op in non-debug builds to avoid cluttering up the system logs of your users with debug logs you'll never see (unless you use ALog intentionally) If you need even more control over your logging check out LibComponentLogging

Answer by Daniel Hammond:

Absolute easiest path to migration would be to use the Parse REST API (https://www.parse.com/docs/rest). You could build out the client to use a networking/object mapping tool like RestKit or roll your own. You would lose the benefits of the native Parse SDK like offline saving (although Restkit+Core Data could provide this) or a native querying objective-c interface, simplified file support, but it would make it incredibly simple to switch out Parse for some other REST based web service.