Interesting, but not a very informative article. I'd be curious to hear more about the technologies behind the framework.
Is Airlock entirely server driven, or are there aspects of it (say, data storage or selecting which variation of a test to display) in the app code itself? Would it make sense to create a framework that lives entirely in Cocoa and only syncs with a server? Why or why not?
Is Airlock entirely server driven, or are there aspects of it (say, data storage or selecting which variation of a test to display) in the app code itself? Would it make sense to create a framework that lives entirely in Cocoa and only syncs with a server? Why or why not?