[ https://issues.jboss.org/browse/TOOLSDOC-412?page=com.atlassian.jira.plug... ] Michelle Murray commented on TOOLSDOC-412: ------------------------------------------ I wrote: {quote} You stated * Hybrid Mobile application project type and project wizard What do you mean by project type? How is this different from project wizard? And * Export wizard for "ready to sign" applications (Xcode and Android) What are "ready to sign applications"? Ones that just need sign off to go in respective platform app stores? How do the apps produced by these wizards differ from those produced by "Export wizards for native code"? {quote} Gorkem replied: {quote} A project type and the project wizard goes together. A new project wizard is basically a side-effect of having a new project type, new project type requires means to crate it. I guess on the documentation a project wizard is an easier place to start. By ready to sign I mean ready for code signing[1]. All mobile OSes require the applications to be code signed by a code signing certificate that they recognise. Usually the certificates are provided as part of their developer/app store subscription. I wanted to stress ready to sign here because our tool does not provide any help for the mobile app. signing at this time. The export wizard for native application produces a compiled binary while native project export only creates a project that can be used with(XCode or android tools) [1]http://en.wikipedia.org/wiki/Code_signing {quote} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira