9 Aug’19

D365 Finance and OperationsHow to set up POS Hybrid App on Android

In this blog we’ll see how to set up the Hybrid App on Android using Xamarin.

Hybrid App is the app that combines the element of both native and web app. Native app are build for a specific platform. Web applications are generalized for multiple platforms and not installed locally but made available over the Internet through a browser.

Xamarin is a cross-platform implementations of the Common Language Infrastructure (CLI) and Common Language Specifications

    1. Element that used to develop application for android
    2. C# language
    3. Mono .NET Framework
    4. Compiler

Following are the steps to follow in order to configure set up the POS Hybrid App

  1. Install Xamarin

Xamarin provides a common development experience for creating cross platform mobile applications. Xamarin facilitates the development of Android and iOS applications by providing the Xamarin.iOS and Mono.Android libraries. These libraries are built on top of the Mono .NET framework and bridge the gap between the application and the platform specific APIs. Open the  visual studio installer you will see the below screen. Make sure the below component are selected

2. Xamarin Configuration

Xamarin.Android uses the Java Development Kit (JDK) and the Android SDK to build apps. During installation, the Visual Studio installer places these tools in their default locations and configures the development environment with the appropriate path configuration. You can view and change these locations by clicking Tools > Options > Xamarin > Android Settings.

3. Android SDK Manager

Visual studio include SDK manager that lets you download android SDK

Uncheck everything. Then check only the following:

Android SDK Tools

Android SDK Platform-tools

Android SDK Build-tools (I don’t think this is necessary)

4. Select the Android SDK Manager

5. You can always debug using actual Android device instead of using Emulator for debugging.

If you need to turn ON Hyper-V in your machine, you will need to go with Visual Studio Android Emulator. To open/configure Visual Studio Android Emulator, go to Tools>Visual Studio Emulator for Android

You will be able to launch or configure the emulator in the new dialog popup.

To make Android SDK Emulator run without lagging, we will need to install Intel HAXM. However, Intel HAXM cannot work together with Hyper-V. So, we need to turn OFF Hyper-V in the machine

Go to control panel turn windows feature on and off and uncheck hyper v

Make sure Virtualization Technology settings is Enable in BIOS settings.

Once we install HAXM we can proceed to android emulator which will open Android virtual device manager dialog box.

The Android Emulator can be run in a variety of configurations to simulate different devices. Each configuration is called a virtual device. When you deploy and test your app on the emulator, you select a pre-configured or custom virtual device that simulates a physical Android device.

6. SDK Configuration Setup

In the Retail SDK folder, open SampleExtensions\HybridApp\Android\solution. Build and deploy using the emulator and verify that everything appears as it should.

7. Export the android app

  • Specify the Application Icon
  • Version the Application – An integer value (used internally by Android and the application) that represents the version of the application. Most applications start out with this value set to 1, and then it is incremented with each build.
  • Version Name – A string that is used only for communicating information to the user about the version of the application these values can be set in the Android Manifest section of project Properties, as shown in the following screenshot

8. Shrink the APK

Xamarin.Android APKs can be made smaller through a combination of the Xamarin.Android linker, which removes unnecessary managed code, and the ProGuard tool from the Android SDK, which removes unused Java bytecode.

9. Archive for Publishing

To begin the publishing process, right-click the project in Solution Explorer and select the Archive.

When we select Ad hoc visual studio will open the signing dialog box app required to be sign with a signing key or if we have already signed we can use import key option. After clicking on the new sign in create key store dialog box shown we can fill the required information it will create key store and will be shown under signing section as we are crating ad hoc publish we click on save it will create achieve file, and it will ask for password if not set earlier.

10. Final step is to distribute the app.

There are different way to publish the app google pay, web or independent

11. Sign In with the credential device will get register and we can see the POS Retail UI

 

Written by

Team Member

CloudFronts

Leave a Reply

Your email address will not be published. Required fields are marked *

Want to streamline your business processes?

  • This field is for validation purposes and should be left unchanged.

Recent Articles

  • Expenses in PSA for Fixed Bid and T&M contracts

    23 August’ 2019

    Problem Definition: One of my clients decided to use Expense module in PSA and to his surprise he could see the amount v...

    Read more
  • Setup Dockers

    23 August’ 2019

    Docker is an independent container platform that enables organizations to seamlessly build, share and run any applicatio...

    Read more
  • Qualify Lead in D365 CE: Select which entity records should be created

    20 August’ 2019

    Wave 2019 Updates brought some really sought-after features. Another one which I would like to bring up is the Lead Qual...

    Read more
  • Early Opt-in for October 2019 Wave 2 Updates

    20 August’ 2019

    August 2, 2019 was when the Wave 2 Updates were to be out. And here we are! By now, you should have gotten the option to...

    Read more
  • Setting Unified Interface App Icons

    20 August’ 2019

    Default App Icons for typical D365 environment look like these.But here’s what you can do to change these to put...

    Read more
  • We respect your privacy.
  • This field is for validation purposes and should be left unchanged.