The run-in-companion-app method
requires an installation of the AppBuilder companion app on the device. Its main advantage lies in the fact that you get to quickly test your project on multiple and different devices as long as they all have the companion app installed. Still, you also need to consider the companion app limitations
which mostly come from the fact that it acts as a container for your application.
The direct-run method
, on the other hand, prepares an application package that can be installed directly on a device. It does not use the companion app at all. Instead, what AppBuilder
does, in the case of this tutorial, is package your project files and build them on our servers utilizing Cordova
. Since every mobile platform build environment is different (for instance you need Mac for iOS and Windows for WindowsPhone builds), the advantage of using AppBuilder
is that it builds your application in the cloud in a pre-configured environment that is chosen based on the targeted mobile platform. Once the build successfully completes, you are presented with an application package:
- .apk for Android,
- .ipa for iOS,
- .xap for WindowsPhone.
You can then manually install the package on your devices as long as each platform requirements for code signing
are fulfilled. In that case you don't need any other AppBuilder
installations on your devices.
You can have a look at the app distribution section
in our documentation for additional information on distributing an AppBuilder