Android, Chromebook & iOS Device Support

the new solution builder sdk & api now facilitates mobile app tools if your license includes mobile support , follow the guide below to enable it including android, chromebook & ios device support in your launch code android & chromebook in your callback function (see splauncher properties docid bpkdmtjdpmi02x4qpzcw ) you will need to include mobileappinstallurl = result appinstallurl; in your final else statement, for the failed result type, as you can see exampled below callback function (result) { var resulttype = result type; if (resulttype=='failed') { if ( ) { } else { mobileappinstallurl = result appinstallurl } } this will return the correct mobile store install url depending on the device type that clicked the launch link from there, it is up to you how you expose this url to the user, and any messaging you provide to help then understand the installation link behavior ios ios requires a unique flow in order to support a standard \<a> tag href to trigger deeplinking in your callback function (see splauncher properties docid bpkdmtjdpmi02x4qpzcw ) you will need to include an additional else if check before the last else statement you would edit for android & chromebook support callback function (result) { var resulttype = result type; if (resulttype=='failed') { else if (result mobilelaunchurl) { // this is special case for ios where we have to show a \<a> link with href set to this url to get // ios deeplinking to work resulttype = 'ios launch app'; document getelementbyid('ios launch app link') href = result mobilelaunchurl; } else { mobileappinstallurl = result appinstallurl } } install link behavior installation as stated above, when an android, chromebook, or ios device encounters a launch link, and the user does not have the screenpal application installed, the callback will fail you will be provided download link to pass on to the user you may want to provide some additional instruction to the user, such as please click the download link (ios follows the link automatically) and install the screenpal app from the app store once you are finished, come back to this page press the launch button again to load the application and unlock it here is an example of this implemented on the same page with the android & chromebook launch link failed to launch did you have our app installed? please click the download link and install the screenpal app from the app store once you are finished, come back to this page press the launch button again to load the application and unlock it download now you can see this behavior in action on our example page here is an example of an ios launch link triggered by the callback you implemented before click the link below to launch or install the app on ios if you are taken to the app store, install the app once you are finished, come back to this page press the launch button again to load the application and unlock it launch or install the app opening and unlocking the application once the app is installed, when a user clicks on a button or link you have implemented, the app on the device will open once opened, the app will unlock the paid features that are available, and in app upsells or purchase flows are removed currently, any custom publish implementation that would show in the desktop apps, will not be displayed the available export/share options are as follow android operating system share modal chromebook save video to file ios operating system share modal note deep linking workflows docid\ fcjbaomsucbu8clrs0tm5 are not supported by the android, chromebook, and ios apps the applications will launch, but they will just launch into the main ui, regardless of the selected workflow