To release the Android apps, you develop with Kuika to end users via the Play Store, Appetize or APK and publish them in test environments, you need to execute configuration settings.

You can execute the configuration settings of the applications you are developing through the Configuration Manager module.

For the mobile application you have developed to run on the Android operating system, you need to make App Settings and Android settings in the Configuration Manager module.

In this learning content, we will examine the actions to be taken in App Settings and Android settings respectively.

Let's start with the App Settings tab.

Through the Connection Settings section, you can define the database string of the application you are developing and the Backend URL information where the Back-end of your application will operate.

• You can use the DB Connection String field to enter the database connection string for your application.
• You can use the Backend URL field to define the URL where you will make the backend of your application live.

In scenarios where you create Process Automation in your application, this section defines the database connection string for Process Automation, the Base URL where the Workflow Engine goes live, and the email provider used for the tasks in Process Automation.

Through the Search Service section, you can define configurations for performing data search and management operations in your application.

You can define the authentication provider you will use in your application through the Authentication and Authorization section, set password policies for passwords to be used in your application, and provide configurations for Google integration to enable login with Google. In addition to these configuration settings, you can also perform MSAL (Microsoft Authentication Library) integration in this section. In scenarios where you want to use OTP, that is, a one-time password, you can execute the definitions for your OTP settings in this section. You can enable or disable the two-step authentication method in the application you have developed. Finally, in this section, you can use the Expire Old Sessions Upon New Login Switch to ensure that old sessions are automatically terminated when a user logs in with the same account in different places.

You can manage the timing settings of the different types of Notify Actions you use in your developed application through the Notify Actions configuration settings.

If you want to use Deeplink technology, you can define the configuration settings by going to Deeplink Settings in App Settings.

To use e-mail notifications in the application, you need to define information for your mail provider in the Mail section. In this section you can use one of the two different mail providers, SMTP or AWS.

You can integrate with payment systems quite easily in the applications you develop. In scenarios where you want to use Stripe, Iyzico and/or Param infrastructures as payment transactions, you need to make configuration settings for the relevant provider in the Payment Method section.

Through Invers configuration, you can integrate the Invers telematics device into your application. This integration allows you to manage device data directly from your app.

Through the WhatsApp Business section, you can integrate the WhatsApp Business service into your app using the developer information you receive from WhatsApp. In this way, you can manage your customer communication processes faster and more effectively.

To protect your apps from spam and abuse, you can use the Google reCAPTCHA service provided by Google. By defining your Developer information provided by Google to the Google reCAPTCHA section in the App Settings, you can increase the security of the applications you develop on the Kuika platform. With this integration, you can strengthen user verification processes and ensure that your app offers a more secure and reliable experience.

After your relevant definition in the App Settings tab, we can move to the Android tab.

In the Android tab, activate the Support Android switch to see the relevant settings and define configuration settings.

In the Mobile App Settings field, you are expected to define information for your app. Fill in the information in this section in a way that is consistent with the information you entered in the Google Play Console.

• Define the name of your app in the App Name field.
• In the Bundle ID field, you are expected to enter the unique key information of your application.
• In the Version field, you are expected to define the version information of your application.
• In the App Version Code field, you must define the version code of your app. Remember, you need to increment this code with each update.
• In the Minimum Android Version field, you can define the minimum Android Operating system version that the Android application you developed can run. You should keep in mind that the minimum Android version is Android 8 in the applications you develop with Kuika.
• You can specify whether your application can use HTTP traffic in the Use Cleartext Traffic field.
• You can set whether your Android apps accept all SSL certificates as trusted in the Trust All Certificates field.

With Haptic Enabled you can manage how your app reacts to touch actions natively.

The next section is where you define the publishing format of your app. You can publish the applications you develop in Kuika with Appetize, APK and AAB packages. For the publishing process of your Android application, you are expected to perform the definition processes in Google Play Connect API setting section. In this section

• Start by giving your configuration setting a name.
• Under the Publish Type heading, you will be asked to choose between Appetize, APK and AAB.
• In the scenario where you choose Appetize, you need to identify the Appetize API Token provided by Appetize. This will allow you to integrate with Appetize.
• If you select APK, you can optionally define SHA-256 Certificate Fingerprints. You can access SHA-256 Certificate Fingerprints information from Play Console.
• When you select AAB, you can optionally define various information. This information is
  
  • Signing Store File, where you can upload the .jks file that provides the key store,
  • Key alias information,
  • Password information for the key,
  • And enter the SHA-256 information to be used in the application signing process.

In cases where you use maps in the Android applications you develop, you are expected to define the Google Maps API Key information, which is the integration information in the Maps section to integrate with Google Maps.

In the next sections of the Android configuration settings, Geolocation, Camera and Bluetooth, you need to define the permission texts for the scenarios where the location, camera and Bluetooth of the user devices will be used. In these sections, you need to define permission texts in English by default. In cases where you add different languages to the application, you need to define for each language.

In the Push Notification section, you need to execute two different settings. The first one is to define the relevant configuration settings under the Configuration heading in order to send push notifications. Through this heading, you are expected to define the Sender ID, Server Key, Service Account JSON and Notification Certificate information you obtained through Firebase Console and Google Cloud Console account.

The second is to define a permission text to send push notifications to the user, as in the previous sections.

The next section in the Android configuration settings is GPS Tracker settings. In the GPS Tracker settings, under the Settings heading:

• Naming the setting,
• Define the minimum distance between updates in meters,
• Determine the accuracy of the location by selecting either approximate or exact,
• You need to specify whether or not to receive location information in the background.

Finally, in the GPS Tracker section, similar to the previous sections, you should define a permission text stating that the user's location will be tracked. In cases where you track location information in the background, you need to define a permission text that the user's location will be tracked in the background even when the application is not running.

You can use Google reCAPTCHA to ensure that your app is protected against malicious use. To use Google reCAPTCHA in your Android apps, simply add your developer credentials to the Google reCAPTCHA field in the Android configuration settings.

In the next section, Options, you can choose whether the app can only work in landscape, portrait or both landscape and portrait. In the same section, you can specify whether the Android app can run on a phone, tablet or both.

In the App Icons heading, you are expected to upload the icon of your application both square and circular; In the Splash heading, you can upload a logo or image for the splash screen of your application and adjust the fit of this image on the screen. In the Color field, you can define the background color of the splash screen.

By defining these settings, you can make your application ready for publishing and testing.