So I'm working on this big Cocoa app to start with, but eventually there'll be an accompanying iOS app to tap into it. Due to NDA I can't get into details about this app, but a close parallel would be, say, used car lots. So going with that as the psudo-type of app Each used car dealer would have their own copy of the main Cocoa app. Each dealer also has their own garage where they service any incoming vehicles before resale. The Cocoa app is used to track progress of servicing, along with sales and customer info and other details about the car. The idea is to have an iOS app that will act as a front end to the database so someone could use it to enter/edit details about vehicles and customers while out and about in the lot or garage. Up until now I've only glanced through the steps about creating and deploying iOS apps, and in 99% of discussions it's always about submitting to the App Store. What I'm wondering, though, is if Apple provides an easy way for an iOS app to be distributed from within a Cocoa app so it can be tied down to that base installation. In this used car scenario, what I'm wanting is for not only the iOS app to be only available (loadable) from within the Cocoa app, but also hard wired, possibly, so that there is no way the iOS app can even connect to another copy of the Cocoa app at another dealer. It'll be some time before the iOS app will be made, so I'm not looking for any hard core details right now Just a big picture look at what I can plan for. This is a very vertical market so placing the iOS app on the App Store wouldn't make any sense (and for security reasons, I'd rather not have it publicly available). Does this sound like it's going to be viable? Thanks.