PC SOFT

WINDEVWEBDEV AND WINDEV MOBILE
ONLINE HELP

Home | Sign in | English UK
  • Overview
  • How to proceed?
  • To generate an application for Android
  • Copying the generated application onto an Android device
  • Implementing a Splash Screen
  • Overview
  • Implementation
  • Operating mode
  • Generation options
  • Configuration for the Android generation
WINDEV
WindowsLinuxUniversal Windows 10 AppJavaReports and QueriesUser code (UMC)
WEBDEV
WindowsLinuxPHPWEBDEV - Browser code
WINDEV Mobile
AndroidAndroid Widget iPhone/iPadApple WatchUniversal Windows 10 AppWindows Mobile
Others
Stored procedures
Overview
The generation of a WINDEV Mobile application for Android groups all project elements (windows, code, etc.) in an archive in order for the application to be deployed on an Android device (physical or emulator) and to be distributed.
How to proceed?

To generate an application for Android

  1. Click Android generation among the quick access buttons. The wizard for generating the Android application starts.
  2. Versions 25 and later
    Select the desired generation mode. This is an important step since the generation format may change depending on the mode selected.
    • "Generate for free deployment (private store, corporate fleet, etc.)": This mode generates an application in Android Package (APK) format.
      Remark: If you use this format to deploy on Google Play Store, a warning message appears during the deployment to indicate that the application can be optimized.
    • "Generate for Google Play Store": This mode generates an application in Android App Bundle (ABB) format, optimized for the store.
    New in version 25
    Select the desired generation mode. This is an important step since the generation format may change depending on the mode selected.
    • "Generate for free deployment (private store, corporate fleet, etc.)": This mode generates an application in Android Package (APK) format.
      Remark: If you use this format to deploy on Google Play Store, a warning message appears during the deployment to indicate that the application can be optimized.
    • "Generate for Google Play Store": This mode generates an application in Android App Bundle (ABB) format, optimized for the store.
    Select the desired generation mode. This is an important step since the generation format may change depending on the mode selected.
    • "Generate for free deployment (private store, corporate fleet, etc.)": This mode generates an application in Android Package (APK) format.
      Remark: If you use this format to deploy on Google Play Store, a warning message appears during the deployment to indicate that the application can be optimized.
    • "Generate for Google Play Store": This mode generates an application in Android App Bundle (ABB) format, optimized for the store.
  3. Versions 21 and later
    The Android SDK and Gradle are required to create the Android executable. You can:
    • Download and install these tools automatically. In this case, WINDEV Mobile downloads and installs all necessary tools with the requested options. Only an Internet connection is required.
      This method is recommended. Caution: The first download can be quite long.
    • Use the tools automatically installed. This option is available if the tools have been downloaded and installed during a previous generation.
    • Use the tools already installed on your computer. In this case, all you have to do is specify the setup paths of Gradle and Android SDK. See Installing the Android SDK for more details.
    New in version 21
    The Android SDK and Gradle are required to create the Android executable. You can:
    • Download and install these tools automatically. In this case, WINDEV Mobile downloads and installs all necessary tools with the requested options. Only an Internet connection is required.
      This method is recommended. Caution: The first download can be quite long.
    • Use the tools automatically installed. This option is available if the tools have been downloaded and installed during a previous generation.
    • Use the tools already installed on your computer. In this case, all you have to do is specify the setup paths of Gradle and Android SDK. See Installing the Android SDK for more details.
    The Android SDK and Gradle are required to create the Android executable. You can:
    • Download and install these tools automatically. In this case, WINDEV Mobile downloads and installs all necessary tools with the requested options. Only an Internet connection is required.
      This method is recommended. Caution: The first download can be quite long.
    • Use the tools automatically installed. This option is available if the tools have been downloaded and installed during a previous generation.
    • Use the tools already installed on your computer. In this case, all you have to do is specify the setup paths of Gradle and Android SDK. See Installing the Android SDK for more details.
    Versions 22 and later
    If you are using a proxy to access Internet, click the "Proxy" button to configure or check the Proxy management. See General options of WINDEV, WEBDEV and WINDEV Mobile for more details.
    New in version 22
    If you are using a proxy to access Internet, click the "Proxy" button to configure or check the Proxy management. See General options of WINDEV, WEBDEV and WINDEV Mobile for more details.
    If you are using a proxy to access Internet, click the "Proxy" button to configure or check the Proxy management. See General options of WINDEV, WEBDEV and WINDEV Mobile for more details.
  4. Go to the next step.
  5. Specify the application name and the package.
    • The application name is the name that will be displayed below the application icon.
      Versions 18 and later
      For the multilingual applications, this name can be typed in several languages. During the setup, the name of the application will be chosen according to the language settings specified for the device. If the application name is not available in the device language, the name defined for the default language of project will be used.
      New in version 18
      For the multilingual applications, this name can be typed in several languages. During the setup, the name of the application will be chosen according to the language settings specified for the device. If the application name is not available in the device language, the name defined for the default language of project will be used.
      For the multilingual applications, this name can be typed in several languages. During the setup, the name of the application will be chosen according to the language settings specified for the device. If the application name is not available in the device language, the name defined for the default language of project will be used.
    • The package is used to identify the application. By convention, it contains the company name (or its Internet domain name in reversed order) followed by the application name. The application name corresponds to the name in the default language of project.
  6. Choose (if necessary) an icon for the application (image in PNG format). This icon is used to make the application more visible in the menu of applications. The default icon will be used if no icon is selected.
    An icon preview is displayed. The arrow button is used to select different icons according to the density of the screen (low density, medium density, high density and very high density).
    Versions 20 and later
    Remark: You also have the ability to use the automatic DPI management. See Android/iOS: Providing an image per DPI for more details.
    New in version 20
    Remark: You also have the ability to use the automatic DPI management. See Android/iOS: Providing an image per DPI for more details.
    Remark: You also have the ability to use the automatic DPI management. See Android/iOS: Providing an image per DPI for more details.
  7. Versions 22 and later
    Specify the email address that will be used by default to send the error report during a fatal error.
    A specific window is displayed when a fatal error occurs in the application:
    The user can:
    • Click the "Error report" link to see the error displayed.
    • Check the box "Send the error report by email". In this case:
      • if the email address was specified, the box will be checked by default and the user will receive the error report in his messaging with the "Sender" and "Recipient" parameters filled.
      • if the email address was not specified, the user will receive the error report in his messaging and it will have to fill the recipient address.
      Remark: To identify the problems encountered by the end user, you also have the ability to use the ADB logs. See Managing ADB logs for more details.
    New in version 22
    Specify the email address that will be used by default to send the error report during a fatal error.
    A specific window is displayed when a fatal error occurs in the application:
    The user can:
    • Click the "Error report" link to see the error displayed.
    • Check the box "Send the error report by email". In this case:
      • if the email address was specified, the box will be checked by default and the user will receive the error report in his messaging with the "Sender" and "Recipient" parameters filled.
      • if the email address was not specified, the user will receive the error report in his messaging and it will have to fill the recipient address.
      Remark: To identify the problems encountered by the end user, you also have the ability to use the ADB logs. See Managing ADB logs for more details.
    Specify the email address that will be used by default to send the error report during a fatal error.
    A specific window is displayed when a fatal error occurs in the application:
    The user can:
    • Click the "Error report" link to see the error displayed.
    • Check the box "Send the error report by email". In this case:
      • if the email address was specified, the box will be checked by default and the user will receive the error report in his messaging with the "Sender" and "Recipient" parameters filled.
      • if the email address was not specified, the user will receive the error report in his messaging and it will have to fill the recipient address.
      Remark: To identify the problems encountered by the end user, you also have the ability to use the ADB logs. See Managing ADB logs for more details.
  8. Go to the next step.
    • Versions 18 and later
      Specify whether or not the application should display a launch screen (also called a "splash screen") at startup. The splash screen is used to have the user wait while the "Initializing" event associated with the project is run. See Characteristics of the splash screen for more details.
      New in version 18
      Specify whether or not the application should display a launch screen (also called a "splash screen") at startup. The splash screen is used to have the user wait while the "Initializing" event associated with the project is run. See Characteristics of the splash screen for more details.
      Specify whether or not the application should display a launch screen (also called a "splash screen") at startup. The splash screen is used to have the user wait while the "Initializing" event associated with the project is run. See Characteristics of the splash screen for more details.
    • Enter the general information about the application: the company name, the copyright and the application description.
    • Versions 18 and later
      Specify whether the application must be automatically launched when starting the device system.
      Remark: ExeInfo is used to find out the launch mode of the Android application.
      New in version 18
      Specify whether the application must be automatically launched when starting the device system.
      Remark: ExeInfo is used to find out the launch mode of the Android application.
      Specify whether the application must be automatically launched when starting the device system.
      Remark: ExeInfo is used to find out the launch mode of the Android application.
    • Versions 22 and later
      Specify whether the maximized application windows can be resized (multi-Window). This option is taken into account from Android 7. If this option is enabled, the windows can be displayed in different modes (1/3, 1/2 or 2/3).
      New in version 22
      Specify whether the maximized application windows can be resized (multi-Window). This option is taken into account from Android 7. If this option is enabled, the windows can be displayed in different modes (1/3, 1/2 or 2/3).
      Specify whether the maximized application windows can be resized (multi-Window). This option is taken into account from Android 7. If this option is enabled, the windows can be displayed in different modes (1/3, 1/2 or 2/3).
  9. Go to the next step.
  10. Specify the version number of generated application. Two formats are available for the version numbers:
    • Standard format. This format is the standard format supported by Windows. This format corresponds to a set of 4 numbers separated by dots.
      • The first group of 4 digits corresponds to the number of major changes performed in the application.
      • The second group of 4 digits corresponds to the number of minor changes performed in the application.
      • The third group of 4 digits corresponds to the generation number.
        We advise you to automatically increment this number at each generation. This increment operation is automatically performed if the option "Automatically increment the version at each generation" is checked.
      • The last group of 4 digits corresponds to the number of reviews (branches in the SCM for example).
    • Format for compatibility. This format was used until version 12 for the WINDEV applications.
      Remark: All the characters (digits and letters) are allowed. For example: "1.01A".
      We advise you to:
      • use a different version number whenever the executable program is created. Indeed, when installing an update, this version number is used to check whether the update is mandatory or not.
      • automatically increment the last characters (digit or letter) of the version number each time the executable program is created (check "Automatically increment the version at each generation").
        For example:
        - the version number "1.01A" will become "1.01B".
        - the version number "A15Z" will become "A16A".
  11. Go to the next step.
  12. The application signature is mandatory for a setup on an Android device. It can be done according to three different methods:
    • Using a couple of public/private keys bought toward a trusted authority: this solution is recommended if the application must be distributed in a business way. It guarantees that the application author can be identified.
    • Using a couple of auto-signed public/private keys: this solution can be used if the application is distributed inside a company for example. It avoids going through the trusted authority (whose services are charged for in most cases).
    • Using a generic signature: this solution can be used when developing the application. An application signed with a generic key cannot be published. Its use is limited to tests in "Go" mode on the same development computer.
  13. Go to the next step.
  14. Versions 25 and later
    If you have chosen to generate the application for a fleet of devices, the wizard proposes to choose the type of devices. You can limit the size of the application by selecting a specific processor architecture.
    Remark: If a device is connected to the PC, use the "Detect hardware automatically" option. Thus, next time an application is generated, this type of device will be automatically selected.
    New in version 25
    If you have chosen to generate the application for a fleet of devices, the wizard proposes to choose the type of devices. You can limit the size of the application by selecting a specific processor architecture.
    Remark: If a device is connected to the PC, use the "Detect hardware automatically" option. Thus, next time an application is generated, this type of device will be automatically selected.
    If you have chosen to generate the application for a fleet of devices, the wizard proposes to choose the type of devices. You can limit the size of the application by selecting a specific processor architecture.
    Remark: If a device is connected to the PC, use the "Detect hardware automatically" option. Thus, next time an application is generated, this type of device will be automatically selected.
  15. Specify whether files must be included in the Android application. You can include:
    • specific resources: images, ...
    • HFSQL data files used by the application, ...
      Integrating files
    By default, the files included in the archive are read-only ("Read" option checked). They can be:
    • used in the read-only application directly.
      For example, if an image is included in the read-only Android application, it can be directly assigned to a control by specifying its name. For example:
      IMG_Image = image1
    • extracted from the archive by programming (fExtractResource). In this case, the file can be modified later.
    You have the ability to specify the destination directory in the l'APK (which means the destination directory in the archive). The "Automatic" option is selected by default: the file is automatically placed in the proper directory according to its type. You have the ability to choose a specific directory.
    Versions 22 and later
    Remark: The "Asset" directory is also proposed.
    New in version 22
    Remark: The "Asset" directory is also proposed.
    Remark: The "Asset" directory is also proposed. If the "Write" option is checked:
    • the file extraction is automatically performed when starting the application (before running the initialization code of project).
    • you have the ability to specify an extraction directory. By default, the data files are extracted into the database directory (<DB Directory>)
      Caution: if the files in "Write" mode already exist on the mobile during the setup, they will not be re-extracted from the archive.
  16. Go to the next step.
  17. Specify whether libraries must be included in the Android application. You can include:
    • specific Java libraries (*.jar or *.aar files).
    • native libraries (SO files).
    • the HFSQL library.
      This library is required if your application is using HFSQL data files.
  18. Go to the next step.
  19. The wizard proposes to include JCenter dependencies in the Android application.
    Versions 24 and later
    It is also possible to specify additional repositories (other than JCenter and Google).
    New in version 24
    It is also possible to specify additional repositories (other than JCenter and Google).
    It is also possible to specify additional repositories (other than JCenter and Google). Go to the next step.
  20. Select the permissions required by the application to operate. Each application must indicate to the Android operating system the services to which it must access in order to operate (access to Internet, access to the camera, etc.). WINDEV Mobile automatically adds the necessary permissions according to the statements used in the application.
    Remarks:
    • If procedures written in native Java have been used, the corresponding permissions must be specified.
    • Versions 22 and later
      From Android version 6, the authorization request is performed during the first use of the feature (beforehand, all requests were grouped during the setup).
      New in version 22
      From Android version 6, the authorization request is performed during the first use of the feature (beforehand, all requests were grouped during the setup).
      From Android version 6, the authorization request is performed during the first use of the feature (beforehand, all requests were grouped during the setup).
  21. Go to the next step.
  22. If your application is available on Google Play, you have the ability to propose your application only for the devices supporting the features used by your application. For example, if your application is using the inertial scroll, it will only be proposed for the devices supporting this feature.
    You can choose to add or remove specific features.
  23. Go to the next step.
  24. Specify the configuration parameters.
  25. If your application is using a Calendar control, a tab with swipe or an internal window with swipe, you must install the "Android Support Library V4" extension. The Android application cannot be generated if this extension is not installed in the Android SDK. The procedure for installing this extension is available from:
    http://developer.android.com/tools/extras/support-library.html#Downloading
  26. If your application is using a Map control, fill the parameters specific to this type of control. See Conditions for using the Map control for more details.
  27. If your application is using an Ad control, fill the parameters specific to this type of control. See Conditions for using the Ad control for more details.
  28. If your application is using the Push notifications, you can:
  29. Versions 19 and later
    If your application is using the In-App purchases, specify the application key. See Android configuration required for the In-App purchases for more details.
    New in version 19
    If your application is using the In-App purchases, specify the application key. See Android configuration required for the In-App purchases for more details.
    If your application is using the In-App purchases, specify the application key. See Android configuration required for the In-App purchases for more details.
  30. Versions 21 and later
    If your application is using the Facebook identification, the wizard for generating the application provides the identifiers required to save the Android application on Facebook. See Using the Facebook identification for more details.
    New in version 21
    If your application is using the Facebook identification, the wizard for generating the application provides the identifiers required to save the Android application on Facebook. See Using the Facebook identification for more details.
    If your application is using the Facebook identification, the wizard for generating the application provides the identifiers required to save the Android application on Facebook. See Using the Facebook identification for more details.
  31. Versions 25 and later
    If your application uses full kiosk mode ( "Device Owner" mode), the application generation wizard offers two options:
    • Deployment (required for Google Play Store): An adb command line must be run on the mobile device after the application is deployed. This operation cannot be undone.
    • Testing only (allows uninstalling by command line): This option allows you to deploy the application in Device Owner mode for testing. It will be possible to enable and disable the "Device owner" mode thanks to an adb command line. To use this option, the application must use a generic signature.
      For more details on kiosk mode, see Application in kiosk mode.
    New in version 25
    If your application uses full kiosk mode ( "Device Owner" mode), the application generation wizard offers two options:
    • Deployment (required for Google Play Store): An adb command line must be run on the mobile device after the application is deployed. This operation cannot be undone.
    • Testing only (allows uninstalling by command line): This option allows you to deploy the application in Device Owner mode for testing. It will be possible to enable and disable the "Device owner" mode thanks to an adb command line. To use this option, the application must use a generic signature.
      For more details on kiosk mode, see Application in kiosk mode.
    If your application uses full kiosk mode ( "Device Owner" mode), the application generation wizard offers two options:
    • Deployment (required for Google Play Store): An adb command line must be run on the mobile device after the application is deployed. This operation cannot be undone.
    • Testing only (allows uninstalling by command line): This option allows you to deploy the application in Device Owner mode for testing. It will be possible to enable and disable the "Device owner" mode thanks to an adb command line. To use this option, the application must use a generic signature.
      For more details on kiosk mode, see Application in kiosk mode.
  32. Versions 22 and later
    The application is compiled and generated in background task. The editor can be used when generating the application.
    New in version 22
    The application is compiled and generated in background task. The editor can be used when generating the application.
    The application is compiled and generated in background task. The editor can be used when generating the application.
  33. At the end of generation, the application can be automatically copied and started on the Android device if this one is connected to the development computer or on the emulator. For more details:

Copying the generated application onto an Android device

The generated application is copied onto an Android device:
  • after the generation of the Android application.
  • by expanding the icon for Android generation ( ) among the quick access buttons and by selecting "Deploy the last application generated on the mobile device".
In the window for copying onto a device:
1. Select the device onto which the application will be copied.
  • If it is an emulator and if this one is not started, WINDEV Mobile will automatically start the emulator when validating the window.
  • If it is a physical device, this one must be connected via the USB port and the "USB debugging" option must be enabled on the device. You also have the ability to use a chromebook: the chromebook via adb providing that the chomebook is passed in developer mode.
    See Preparing the Android phone for more details.
Remarks:
  • Starting an emulator may take several minutes. We advise you to keep the emulator started.
  • This window can also be used to create a new emulator or to delete one if necessary.
  • You have the ability to specify the parameters of command line for starting the emulator.
2. At the end of copy, the application will be automatically started. You will be able to run its test.
Versions 18 and later
Implementing a Splash Screen

Overview

When an Android application is started, the initialization code of project is run before opening the first window. The execution time of this code can be quite long and the user may think that the application is slows or that it encounters a problem.
To solve this problem, we recommend that you use a splash screen, displayed while the project initialization code is run.

Implementation

To use a splash screen, select "Splash screen" in the wizard and click on "Options" to define the information displayed:
  • Name of the application: #APPNAME# is used by default and it corresponds to the application name specified at the beginning of generation wizard. This name can be modified.
  • Version: Corresponds to the version of the application. By default, #VERSION# is using the version number specified in the generation wizard. This number can be modified.
  • Loading message: This message will be displayed on the splash screen. NextTitle used in the project initialization code allows you to dynamically modify this message.
  • Application logo: This logo will be displayed below the application name.
  • An animation can be displayed while loading the application.
  • Background image: : The background image can be used in portrait and landscape mode. A default image will be used if this image is not specified. If a start image is specified, you have the ability to indicate a specific image according to the resolution of device used.
    Versions 20 and later
    Remark: You also have the ability to use the automatic DPI management. See Android/iOS: Providing an image per DPI for more details.
    New in version 20
    Remark: You also have the ability to use the automatic DPI management. See Android/iOS: Providing an image per DPI for more details.
    Remark: You also have the ability to use the automatic DPI management. See Android/iOS: Providing an image per DPI for more details.
You can also specify the color to use for the different captions as well as the background color of the splash screen.

Operating mode

The code in the "Initializing" event associated with the project is run in a thread while the splash screen is displayed. It is recommended to run long processes in this event (for example: connection test, connection, extraction of resources etc.).
New in version 18
Implementing a Splash Screen

Overview

When an Android application is started, the initialization code of project is run before opening the first window. The execution time of this code can be quite long and the user may think that the application is slows or that it encounters a problem.
To solve this problem, we recommend that you use a splash screen, displayed while the project initialization code is run.

Implementation

To use a splash screen, select "Splash screen" in the wizard and click on "Options" to define the information displayed:
  • Name of the application: #APPNAME# is used by default and it corresponds to the application name specified at the beginning of generation wizard. This name can be modified.
  • Version: Corresponds to the version of the application. By default, #VERSION# is using the version number specified in the generation wizard. This number can be modified.
  • Loading message: This message will be displayed on the splash screen. NextTitle used in the project initialization code allows you to dynamically modify this message.
  • Application logo: This logo will be displayed below the application name.
  • An animation can be displayed while loading the application.
  • Background image: : The background image can be used in portrait and landscape mode. A default image will be used if this image is not specified. If a start image is specified, you have the ability to indicate a specific image according to the resolution of device used.
    Versions 20 and later
    Remark: You also have the ability to use the automatic DPI management. See Android/iOS: Providing an image per DPI for more details.
    New in version 20
    Remark: You also have the ability to use the automatic DPI management. See Android/iOS: Providing an image per DPI for more details.
    Remark: You also have the ability to use the automatic DPI management. See Android/iOS: Providing an image per DPI for more details.
You can also specify the color to use for the different captions as well as the background color of the splash screen.

Operating mode

The code in the "Initializing" event associated with the project is run in a thread while the splash screen is displayed. It is recommended to run long processes in this event (for example: connection test, connection, extraction of resources etc.).
Implementing a Splash Screen

Overview

When an Android application is started, the initialization code of project is run before opening the first window. The execution time of this code can be quite long and the user may think that the application is slows or that it encounters a problem.
To solve this problem, we recommend that you use a splash screen, displayed while the project initialization code is run.

Implementation

To use a splash screen, select "Splash screen" in the wizard and click on "Options" to define the information displayed:
  • Name of the application: #APPNAME# is used by default and it corresponds to the application name specified at the beginning of generation wizard. This name can be modified.
  • Version: Corresponds to the version of the application. By default, #VERSION# is using the version number specified in the generation wizard. This number can be modified.
  • Loading message: This message will be displayed on the splash screen. NextTitle used in the project initialization code allows you to dynamically modify this message.
  • Application logo: This logo will be displayed below the application name.
  • An animation can be displayed while loading the application.
  • Background image: : The background image can be used in portrait and landscape mode. A default image will be used if this image is not specified. If a start image is specified, you have the ability to indicate a specific image according to the resolution of device used.
    Versions 20 and later
    Remark: You also have the ability to use the automatic DPI management. See Android/iOS: Providing an image per DPI for more details.
    New in version 20
    Remark: You also have the ability to use the automatic DPI management. See Android/iOS: Providing an image per DPI for more details.
    Remark: You also have the ability to use the automatic DPI management. See Android/iOS: Providing an image per DPI for more details.
You can also specify the color to use for the different captions as well as the background color of the splash screen.

Operating mode

The code in the "Initializing" event associated with the project is run in a thread while the splash screen is displayed. It is recommended to run long processes in this event (for example: connection test, connection, extraction of resources etc.).
Generation options

Configuration for the Android generation

The configuration parameters are as follows:
Android SDK:
The generation is using the Android SDK.
You may have to specify the minimum version required to run the application.
Versions 25 and later
WINDEV Mobile can generate applications compatible with Android version 5.0 (and later).
New in version 25
WINDEV Mobile can generate applications compatible with Android version 5.0 (and later).
WINDEV Mobile can generate applications compatible with Android version 5.0 (and later).
Remark: If your application is using features not supported by the selected minimum version, a specific icon is displayed on the right of minimum version. An information message allows you to see the details of features that will not be supported if this minimum version is stored.
Minimum version
Setup location:
The possible options are as follows:
  • Internal memory: The application will be installed in the internal memory of the device and it cannot be installed in the external memory (SD card for example). The application will not be installed if the internal memory of device is full.
  • Internal memory movable to the SD card: The application will be installed in the internal memory of device but it can be moved by the user into the external memory from the application for managing the applications (accessible from the menu of device parameters). If the internal memory of device is full during the setup, the application will be installed in the external memory.
  • SD Card movable to the internal memory: The application will be installed in the external memory of device but it can be moved by the user into the internal memory from the application for managing the applications (accessible from the menu of device parameters). If the external memory of device is full or not accessible during the setup, the application will be installed in the internal memory.
Consequences of installing an application in the external memory:
  • Only the APK file of the application is installed in the external memory. The application data (databases, external files, etc.) are still stored in the internal memory, at the same location as if the application was installed in the internal memory (/data/data/<package name>/<application name>).
  • The APK file installed on the external memory is encrypted with a key allowing it to operate with the device that installed it only. Therefore, an application installed on the SD Card operates for a single device.
  • Installing an application on the external memory does not impact the performances of the application.
  • If the user connects his device to the PC in "mass storage" mode (or in "disk drive" mode), the SD Card is automatically dismantled from the device and it is no longer accessible from this one. All the applications installed on the SD Card and currently operating are killed. The applications installed on the SD Card will not operate as long as the SD Card is dismantled.
Advanced configuration
The options of the advanced configuration are as follows:
  • Customizing the commands
    • Command of Java compiler
    • Versions 19 and later
      Signature command
      See the documentation about the Android SDK for more details.
      New in version 19
      Signature command
      See the documentation about the Android SDK for more details.
      Signature command
      See the documentation about the Android SDK for more details.
  • Android SDK: Version used to compile the application. The most recent version installed on the computer is used by default.
  • Versions 19 and later
    SHA1 fingerprint of the certificate used to sign the application: To modify this print, all you have to do is modify the certificate used.
    New in version 19
    SHA1 fingerprint of the certificate used to sign the application: To modify this print, all you have to do is modify the certificate used.
    SHA1 fingerprint of the certificate used to sign the application: To modify this print, all you have to do is modify the certificate used.
  • Customizing the manifest.
    The manifest generated for the Android application can be edited. You have the ability to add, modify, delete nodes or attributes.
    Caution: Modifying the manifest may trigger compilation errors or failures during the execution on the device.
  • Versions 19 and later
    Generation options:
    • Don't include the Android Support library: This option is an advanced option, reserved to very special cases.
    New in version 19
    Generation options:
    • Don't include the Android Support library: This option is an advanced option, reserved to very special cases.
    Generation options:
    • Don't include the Android Support library: This option is an advanced option, reserved to very special cases.
    • Versions 21 and later
      Enable the multidex generation: This option is used to compile huge projects that reach the limit of 65000 methods.
      New in version 21
      Enable the multidex generation: This option is used to compile huge projects that reach the limit of 65000 methods.
      Enable the multidex generation: This option is used to compile huge projects that reach the limit of 65000 methods.
    • Versions 21 and later
      Ignore the HTTPS errors: This option is checked by default and it is available for the applications created with a version earlier than WINDEV Mobile 21 and using the HTTP functions or Webservices. Caution: If you uncheck this option, it will not be redisplayed. To keep the operating mode of application, you will have to use the "HTTTP.IgnoreError = 0" statement in the code. in order to ignore the errors.
      New in version 21
      Ignore the HTTPS errors: This option is checked by default and it is available for the applications created with a version earlier than WINDEV Mobile 21 and using the HTTP functions or Webservices. Caution: If you uncheck this option, it will not be redisplayed. To keep the operating mode of application, you will have to use the "HTTTP.IgnoreError = 0" statement in the code. in order to ignore the errors.
      Ignore the HTTPS errors: This option is checked by default and it is available for the applications created with a version earlier than WINDEV Mobile 21 and using the HTTP functions or Webservices. Caution: If you uncheck this option, it will not be redisplayed. To keep the operating mode of application, you will have to use the "HTTTP.IgnoreError = 0" statement in the code. in order to ignore the errors.
  • Versions 23 and later
    Deployment options:
    • Obfuscate and reduce the size of generated code: This option is used to:
      • optimize the size of generated code for the Android applications (can be used from Android SDK 4.0). You must install a version of sdk-tool in version 21 or later.
        SDK
      • makes the code generated for the Android applications unreadable in order to protect them from decompilation and reverse-engineering operations.
    • Encrypt the strings: This option is used to encrypt all legible character strings found in the code (useful if identifier or password information is found in the code for example).
    New in version 23
    Deployment options:
    • Obfuscate and reduce the size of generated code: This option is used to:
      • optimize the size of generated code for the Android applications (can be used from Android SDK 4.0). You must install a version of sdk-tool in version 21 or later.
        SDK
      • makes the code generated for the Android applications unreadable in order to protect them from decompilation and reverse-engineering operations.
    • Encrypt the strings: This option is used to encrypt all legible character strings found in the code (useful if identifier or password information is found in the code for example).
    Deployment options:
    • Obfuscate and reduce the size of generated code: This option is used to:
      • optimize the size of generated code for the Android applications (can be used from Android SDK 4.0). You must install a version of sdk-tool in version 21 or later.
        SDK
      • makes the code generated for the Android applications unreadable in order to protect them from decompilation and reverse-engineering operations.
    • Encrypt the strings: This option is used to encrypt all legible character strings found in the code (useful if identifier or password information is found in the code for example).
Related Examples:
Android Speech Synthesis Android (WINDEV Mobile): Android Speech Synthesis
[ + ] This educational example explains how to manage the recognition and the speech synthesis Android.
The speech synthesis is performed by using either the WLanguage functions, or an external JAR file included in the WINDEV Mobile project.
Minimum version required
  • Version 15
Comments
Click [Add] to post a comment