How do I Become an Android Developer on a Mac?

This lesson describes the basic steps you need to follow in order to start up as an Android developer using an Apple Mac. System configuration information and screen captures are provided.

Introduction

Android is another mobile device family supported by LiveCode. The steps discussed in this lesson outline a process that allows you to set yourself up as a LiveCode developer for the Android platform and successfully build and deploy test applications. The steps are set out in chronological order, first determining the software requirements and then setting up your system.

Note: The screen captures are up to date at the time of writing this lesson.

Software Requirements

You will need an Apple Mac that has the following software installed:

- Latest version of LiveCode

- Java SDK (JDK)

- Android SDK (recommend SDK tools only)

Note: It is assumed that you are familiar with the installation process of an Apple operating system and LiveCode. Please make sure these are installed before you commence with the remaining steps of this lesson.

The following steps run you through the software installation process that you would typically follow on a Mac.

Downloading Java SDK (JDK)

Downloading Java SDK (JDK)

Newer versions of MacOSX do not come pre-installed with the required JDK. You can download it from: http://www.oracle.com/technetwork/java/javase/downloads/index.html.

This link takes you to a landing page for a number of Java specific downloads. You should download the JDK. This can be accessed by selecting the download "JDK" option on this page

Navigate to the download link that is specific to your operating system and select the download link. You may get the kind of download dialog that is shown in this step. Save the file to your file system, execute it and follow the installation steps that guide you through the installation.

Note: You may get a warning dialog if you try to install Java SDK over a previously installed version. The dialog should allow you to reinstall the software, if you would like to do so.

Downloading the Android SDK

Downloading the Android SDK

If you do not have Android SDK installed, then you can download it from: http://developer.android.com/sdk/index.html.

NNavigate to the SDK Tools only download link that is specific to your hardware platform. You may get the kind of download dialog that is shown in this step. Save the file to your file system.

Executing the Android SDK

Executing the Android SDK

The Android SDK files you have downloaded comes in a zip file that contains the Android SDK and AVD Manager. You can install the Android SDK into your development environment by executing the following steps:

1. Use Finder to navigate to the location into which you downloaded the Android SDK zip file.

2. Double click on the file to extract it.

3. Move the extracted package into a location that is to store the Android SDK.

4. Navigate into the package that was moved and locate the file android-sdk-mac/tools/android.

5. Execute android-sdk-mac/tools/android.

Installing the Android SDK Packages

Installing the Android SDK Packages

The main dialog, shown in the figure of this step, is the Android SDK manager.

The Android Package Installer lets you select the packages you would like to install in you Android development environment. By default, only a few pacakges are selected. From this version of the SDK I would recommend keeping the default selection.

Please make sure that you also have checked the latest "Android SDK Tools" and "Android SDK Platform-Tools" from the "Tools" dropdown

Note: Very old versions of Android are not supported and the very latest versions of Android may not be supported until LiveCode has been updated.

Ensure that you install the SDK Platform Android 4.0.3 package.

Note: There is a known "black screen" issue when deploying certain stacks to a simulator running Android 2.2, API 8 with revision 2 . If you experience this issue please create and use an newer Android revision AVD (e.g. 4.1)

 

 

Accept Licence Agreement for each package

Accept Licence Agreement for each package

You will now need to accept the licence agreements for each package

1) Select the package from this left hand window

2) Select the "Accept Licence" checkbox

3) Select the "Install" button

 

Configuring a Virtual Device

Configuring a Virtual Device

Once you have installed the required packages, you can use the Android SDK and AVD Manager to set up a virtual device that can be used in your development environment. This allows you to test your applications without requiring a physical Android device. You can set up a virtual device as follows:

1. Select Manage AVDs from the Androids SDK Manages Tools window

2. Choose "New" from the  AVD Device manager window

3. Choose the Name for your virtual device.

4. Set the Target an installed Android API.

5. Fill in the SD Card Size.

6. Optionally enable Snapshot. This speeds up the launch of the emulator.

7. Select Create AVD.

 

Starting the Virtual Device Simulator

Starting the Virtual Device Simulator

You can launch the emulator by highlighting the virtual device you created and selecting Start... .

Configuring a Physical Device

In addition to setting up virtual devices, it is possible to set up physical devices. These devices can be accessed after they have been appropriately configured for debugging.

Install the appropriate device drivers for the devices you would like to use. Details of how to do this can be found at the Android Developer Website.

The relevant device must be set to debug mode, once the necessary drivers are installed. To enable debug mode, please see your manufactures recommend instructions for doing so. An example for a Galaxy S3 running Android 4.1.1 is-

1) Go to Settings> About> Software Information> More

2. Now Scroll onto Build Number and tap it 7 times repeatedly. After tapping the build number 5 times you’ll see a message “Press it two more times to be a developer!” and after tapping 7 times you’ll see message “You are now a developer” or “Developer mode has been enabled”

3) Navigate to Settings> Developer options

4) Check option for Android Debugging

Configuring LiveCode for Android Support

Configuring LiveCode for Android Support

By now, you should have successfully installed the required software in you development environment. The next step is to launch LiveCode and configure it to interface with the Android SDK.

Launch the LiveCode IDE and select LiveCode -> Preferences to launch the Preferences menu. Then select Mobile Support and you are presented with the dialog shown in this step.

This dialog allows you to configure the path to the Android SDK root, which you should already have installed. Select ... under Android SDK and choose the directory containing the Android SDK root.

Validation checks are made once you specify the location of the Android SDK root. This ensures that you have selected a valid location and have the required Android components installed.

The following error message may be raised if something is wrong with your set up:

The chosen folder is not a valid Android SDK. Please ensure you have installed it correctly, and enabled support for Android 2.2 (Froyo). (see Installing the Android SDK Packages step)

This indicates that the path you specified is not pointing at the Android SDK root. You may have to navigate one level deeper into the directory hierarchy to access the root directory. The root directory may look something like: ...android-sdk-mac.

The Standalone Application Settings... Window

The Standalone Application Settings... Window

Select File -> Standalone Application Settings... from the LiveCode IDE. Then choose Android from the list of deployment options. This raises the Standalone Application Settings dialog for Android specific builds.

You can make a stack build for Android by selecting the Build for Android tick box and configure any other options you wish to include.

You can select the name of your application using the General option at the top of the pane and add files to your build by using the CopyFiles option at the top of the pane.

Note: Making a stack build for Android disables building standalone mainstacks for any other non-mobile platforms. If you wish to share code and rescues among platforms, factor you application into multiple stacks, using a different mainstack for mobile and desktop targets.

Note: Inclusions, Copy Referenced Files, Bug Reports and Stacks features are not available when building for Android. Use the CopyFiles feature if you wish to include multiple stack files in your application.

Running Under Android

You should now have set up your development environment for Android and are ready to test a LiveCode application on an Android device.

Ensure the emulator is running or and adequately configured physical device is connected before trying to test your code. Then select a device from the LiveCode IDE from Development -> Test Target. Your Test icon on the main pain of the LiveCode IDE should now be active and allow you to deploy your LiveCode application.

NB When deploying to a device, you may receive a "INSTALL_PARSE_FAILED_INCONSISTENT_CERTIFICATES" message. All this means is that there is currently an application installed on your device that has the same identifier as the app your are trying to deploy. This can happen if you are working on a specific app across multiple development machines.

To resolve this issue you can do one of the following-

-remove the existing application from the device you are deploying too

-change the app identifier in the standalone applications settings

Further Reading

Depending on how experienced you are with LiveCode, you may want to review more of the numerous lessons and tutorials we have on developing for Android, iOS and broader lessons that explore the general concepts behind LiveCode.  The release notes accompanying LiveCode releases with Android platform support provide up to date development information and give you an overview of the features that you can access via LiveCode.

0 Comments

Add your comment

E-Mail me when someone replies to this comment