This question is locked. New answers and comments are not allowed.
First, I have thoroughly enjoyed working with the Icenium Mist beta and commend you on an outstanding product. The version 1.5 release has resolved the GitHub repository commit and push glitches I was experiencing and seems quite stable. Now I am at a crossroad considering moving from the current cloud-based build service for my production app (big red A) to Icenium but have a few questions about upcoming features to address scenarios that aren't currently covered in Icenium's impressive infancy.
• Cordova 2.5.0 introduced a bug that requires Kendo Mobile to be initialized differently for Android and iOS (script tag at the bottom of index.html or document.ready vs. deviceready). This bug doesn't exist in 2.4.0 (Icenium's current Cordova version) or previous versions. Will Icenium handle this for 2.5.0+ in a way that doesn't require a bunch of developer trial-and-error and conditional logic just to initialize the app properly without splash screen glitches?
• For users like myself with existing Kendo DevCraft Complete subscriptions, is there a way to target Kendo Mobile internal builds for testing with the debug build configuration or possibly an "edge testing" build configuration?
• I am currently able to set the duration of my iOS and Android splash screens, disable iOS webview bounce, enable/disable app exit-on-suspend, and display splash screen progress spinners with an xml config file. Will simple configurations like this make their way to the Icenium project properties dialogue or will they need to be set in code with Cordova APIs or scripted otherwise?
• The iOS background services are awesome–good job! What is the time line for Android background services?
• What is the timeline for Windows Phone and Blackberry distribution?
I am aware these are some low level and possibly unforseen issues but am wary about migrating entirely while several versions into my app with the current build service provider.
• Cordova 2.5.0 introduced a bug that requires Kendo Mobile to be initialized differently for Android and iOS (script tag at the bottom of index.html or document.ready vs. deviceready). This bug doesn't exist in 2.4.0 (Icenium's current Cordova version) or previous versions. Will Icenium handle this for 2.5.0+ in a way that doesn't require a bunch of developer trial-and-error and conditional logic just to initialize the app properly without splash screen glitches?
• For users like myself with existing Kendo DevCraft Complete subscriptions, is there a way to target Kendo Mobile internal builds for testing with the debug build configuration or possibly an "edge testing" build configuration?
• I am currently able to set the duration of my iOS and Android splash screens, disable iOS webview bounce, enable/disable app exit-on-suspend, and display splash screen progress spinners with an xml config file. Will simple configurations like this make their way to the Icenium project properties dialogue or will they need to be set in code with Cordova APIs or scripted otherwise?
• The iOS background services are awesome–good job! What is the time line for Android background services?
• What is the timeline for Windows Phone and Blackberry distribution?
I am aware these are some low level and possibly unforseen issues but am wary about migrating entirely while several versions into my app with the current build service provider.