Skip To Content

Distribute your app

Apps signed with your own developer certificate can be distributed in the following ways:

  • Publish to a public store. Stores will ensure that distribution requirements such as code signing are met. Stores include the following:
    • Google Play
    • App Store
    • Mac App Store
    • Windows Store
    • Ubuntu Apps Directory
  • Publish via an enterprise store. These stores will ensure that distribution requirements such as code signing are met and include the following:
    • iTunes Connect
  • Host on your own website or file server.
    • This method is suitable for all operating systems.
    • Devices must be able to connect to the network location where installation files are stored.
    • As the distributor, you are wholly responsible for complying with distribution requirements for each operating system.
  • Physically copy installation files to devices using USB drives or SD cards.
    • This is ideal for Windows, Mac, Android, and Linux operating systems.
    • iOS requires additional software, such as iTunes, to install an .ipa file.

Creation of installation files

The cloud Make process generates installation files for all platforms. A default installation wizard is generated for you. To supply your own EULA for inclusion in the installation wizard, complete the following steps:

  1. Include your own EULA as a text file called license.txt in your project folder. This text file is embedded and displayed in the installation wizard for your app. If you want your users to be able to browse to a license file on disk after the install, you should include a second file type, such as a PDF.
    Note:

    AppStudio apps are partially built with open source tools, which your app will need to acknowledge in your EULA.

    OpenSSL Toolkit is used to support secure network communication in AppStudio built for Windows and Android. See the OpenSSL Toolkit license for details on acknowledgement.

    The Android Beacon Library is used to support Bluetooth beacon interaction. This library is copyright 2014-2018 Radius Networks, and is licensed under Apache Licensing. See Apache License 2.0 for details on acknowledgement.

  2. Open the project's appinfo.json file, and manually add the license file properties. By default, the license file is not displayed in the installation wizard. To show the license file, ensure that make.showLicense is set to true and that the path to the file is defined. See the following example:
    "make": {
          "license": {
                 "showLicense": true,
                 "path": "assets/licenses"
          }
    },

Multiple license text files can be included for different languages; however, a naming convention including the language's locale code is required for them to appear embedded. For example, a Spanish license file requires the filename license_ES.txt.

To customize the installation wizard that is to be generated (for example, to define which pages display or to customize the images that are used), you will need to use the local Make tool.

Publish to Google Play

To publish to Google Play, you must have a Google developer account. This account incurs an annual subscription fee. To sign up, go to https://play.google.com/apps/publish/signup/.

This account is required to create a keystore file. For additional details, see Sign your Android app.

Once you're signed in with this developer account, you can create a new listing. Tips for creating a new listing include the following:

  • Create good screen captures for phones, 7-inch tablets, and 10-inch tablets.
  • Be aware that your app will be live in approximately 2 hours.
  • Each time you want to update your app, you must use the same keystore file. Be sure to keep your keystore file safe.
  • Consider translating your store item. This includes providing translated descriptions and screen captures.

Publish to the App Store

To publish to the App Store, you must have an Apple developer account. This account incurs an annual subscription fee. To sign up, go to developer.apple.com.

This account is required to create a developer certificate. For additional details, see Sign your iOS app.

Once you're signed in with this developer account, you can create a new listing. To create a listing, go to http://itunesconnect.apple.com. Tips for creating a new listing include the following:

  • The upload of an .ipa file must be done from a Mac using Application Loader.
  • Create good screen captures for iPhones and iPads. Please review Apple's screenshot specifications for up-to-date information on screenshot sizes.
    Note:

    To generate screen captures for specific iPhones and iPads without having the hardware, use an iOS simulator when running AppStudio on Mac.

  • Consider translating your store item. This includes providing translated descriptions and screen captures.
  • Be aware that your app will take one to two weeks for approval.
  • Many apps created with AppStudio have already been submitted to the App Store. Although these successful apps should give you confidence that your app will be accepted, rejected apps are common and often require minor changes before resubmission.