I coming to believe it's possible to embed an BTv1.4 app into either a BTv1.5 app or a BTv2.0 app. My understanding is that BTv1.4 is similar to PhoneGap only that it's wapping a webapp into a native app. That's why you need internet connectivity for a BTv1.4 app to function. With some help in understanding the interworking of BTv1.4, I think we could accomplish this. Fred

Post here or email me. Fred

v1.4 is not a wrapper in all cases. It is in cases where it's using only html files as content but lots and lots of the screens added in v1.4 apps run native code. The design of 1.4 was not ideal in that is forced the app to constantly contact the server on a screen-by-screen basis which wasn't good. This is the biggest difference between v1.4 and v1.5 - is not the actual screens and how they work but instead where the data comes from. Embedding one app into another app is something I've experimented with and done on many occasions. In fact, it's the core concept behind many situations where you need dozens (or hundreds) of individual app 'instances' inside one parent app. Consider this: If an insurance company (pick your favorite national brand) needs one 'parent app' in the market, but also needs to allow individual agents to manage their instances of their own 'mini apps' inside the parent, it makes sense that they could it do it using the control panel. Agent's create apps that are auto-magically included in the parent. Super common. Apple generally hates this approach but has approved many of these types of apps. If done professionally, it can be very VERY successful, fun, and flexible when helping folks solve larger corporate type problem that surface when they try to figure out their brands app strategy. How it works depends on lots of factors. It's basically like this: a) Create an app to act as the parent. Make this app like you would expect. Corporate info, features appropriate for the corporate identity, etc. b) Create a tab in this app that loads a list of 'child apps' for each agent. This could be a list, buttons, search logic, whatever. This screen just displays the appropriate agent instances. Using the insurance analogy here. c) Tapping a agents icon, name, whatever, loads another UIViewController that is configured to download the data for the agent's app then displays menus, features, content the agent created. Hope this helps.

Your insurance example is one that I would love to be able to do. But I was thinking the ability to reference / launch a BTv1.4 app in particular would be ''doable''.

Yes, you can use this logic to launch existing apps. The trick, and the challenge, will be getting the parent app setup to 'understand' what the heck a v1.4 app is! LOL. In v1.4, the app delegate launches an instance (instantiates) of an AppViewController object. This object is instantiated by calling it's initWithApplication method. In other words, create an AppViewCotroller and show the app object I pass in when I call the initWithApplication method. In a v1.4 app you can see this logic on about line 173 in the app delegate. So, app delegate in turn launches a AppViewController. In AppViewController, you'll see where it sets up the home screen menu and other application options. Tapping an item on the home screen loads an additional screen. So far so good, nothing too complicated. All this means is that you'll need to build a menu or button (or list of buttons) that launches a v1.4 app when tapped. The best way to do this will be to start with a v1.4 app, not a v1.5 app. This is because the v1.4 app code will be in place to handle all the other mini sub-apps that are also v1.4 apps. Get confusing I know. a) Build a v1.4 app b) Add a menu item that reads 'Show Apps' or something. c) Look at the AppViewController file and intercept the tap when this 'show apps' item is tapped. d) Instead of loading a built in screen type (v1.4 built in screen type) when this item is tapped, load your own custom view controller that lists all the apps you want to show. hard to know how you want to manage this list of apps? Probably just manually type them in? The idea is that your code will need to know the app ID of the one selected. It will then instantiate an instance of an App that will then get passed to the initWithApplication method in the AppViewController. Push this view controller on the stack and you're good to go. For most folks, the trouble comes in when they don't understand how to instantiate instances of Objects, such as the Application.h / .m object. Because they don't understand the core concepts behind Objective C, but have a wonderful idea instead, they can't quite get this to work. I wish I could explain it better but can only say that you can do this but will need to get comfy with how to instantiate the Application.m object found in v1.4 and the AppViewController in v1.4 then push that view controller on the screen.

Too much info for now, will read again tonight when I'm good and drunk, I think that might help. Thanks, Fred