Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

Billy Boo Bob

macrumors 6502
Original poster
Jun 6, 2005
493
0
Dark Side Of The Moon
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.
 
A B2B app is most likely to be "viable":
https://developer.apple.com/programs/volume/b2b/


I find your use of the term "Cocoa app" to be confusing. I assume you mean the OS X app. "Cocoa app" is confusing because the API in iOS is called "Cocoa touch", but is still "Cocoa". Also, many of the Cocoa frameworks are identical, so one could write a Cocoa app, say a server, and it could be compiled for either iOS or OS X.
 
Maybe have your OS X app turn the Mac into a server that presents a web app when iOS clients navigate to the right URL?

Not totally sure about the details as I'm not terribly experienced with networking stuff, but I think I'd look into doing something like that if I had such strict requirements, rather than making a native iOS app.
 
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.

Even B2B apps are installed via iTunes. Apple provides no other means of getting apps onto iOS devices at this point.
 
Actually, enterprise accounts can distribute directly...

*That's* what I was thinking of. I knew I had read about that somewhere a while back. I guess Apple could stand to update their pages a bit there. They still show and talk about using Xcode 4. :)

Well, if this thing works out to where we need an iOS app to go along with it, that will mean that we've sold enough copies to where 300 bucks a year will be affordable. I'll look into it deeper when the time comes. Still have a LOT of work to do on the OS X app.

Thanks.
 
Well, if this thing works out to where we need an iOS app to go along with it, that will mean that we've sold enough copies to where 300 bucks a year will be affordable. I'll look into it deeper when the time comes. Still have a LOT of work to do on the OS X app.

The Enterprise developer program is only for apps being distributed within an organization. You can't sell apps that way, so if each of these dealers are a separate company, this isn't a viable option.
 
The Enterprise developer program is only for apps being distributed within an organization. You can't sell apps that way, so if each of these dealers are a separate company, this isn't a viable option.

I knew it sounded too good to be true. So it looks like web app, or App Store with tight security for logging into the OS X app. Ugh.
 
I knew it sounded too good to be true. So it looks like web app, or App Store with tight security for logging into the OS X app. Ugh.

It's a grey area too. I wrote an Enterprise App that was distributed by their own web server years ago. They were an international medical consultant company who sold bespoke software to hospital clinics worldwide. I passed all the code over to them when it was complete and I knew they were in talks with Apple directly on how they could do this. It wasn't B2B but some kind of Enterprise agreement they had. Obviously they could not agree to the normal "must be within the same organisation" part, being consultants.

I don't know how they got on as I left that company a few years ago to go solo.

I know in the early days they were thinking of offering the app for free on the app stores to make distribution less of a pain so it needed a subscription based login of some kind (like Netflix, Dropbox apps etc)

As for security, you can use OpenSSL with SQLCipher which allows for realtime encryption of all data and works great with SQLite. Keep in mind that you have to declare to Apple your app uses encryption.

Anim
 
Last edited:
Well, I'm not so worried about somebody intercepting data as it's being transmitted between iOS and OS X. I'm more concerned about a competitor driving near enough to the building to catch WiFi (which should be secured by password and the point would be moot, but we're talking general non-tech-savvy public here) and logging into the system to poke around.

There's plenty of ways to stop it, though. The aforementioned WiFi password, coupled with a password to connect to the server (OS X app), etc... I'll work it out. Have plenty of time for that.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.