Java Development Kit Setup

Download a compatible JDK release for your operating system and execute the installer. After installation, define the runtime location by assigning the installation directory to a system environment variable named JAVA_HOME. Append the executable subdirectory (%JAVA_HOME%\bin on Windows or $JAVA_HOME/bin on Unix-based systems) to the global execution path. Verify the configuration by querying the compiler vertion:

javac -version

Android SDK and Platform Tools Provisioning

Install the official Android development IDE, which automatically provisions the underlying SDK components. Locate the SDK root directory after the initial setup completes. Create a system variable named ANDROID_HOME and assign the SDK's absolute path to it. Extend the PATH to include the platform utilities and command-line tools. Validate the bridge connectivity by checking the debug client status:

adb version

Node.js Runtime Deployment

The automation architecture relies on a JavaScript execution engine. Install the current Long-Term Support distribution of Node.js from the official registry. The setup wizard typical handles path registration automatically during the process. Confirm both the runtime and package manager are accessible:

node --version && npm --version

Appium Core and Server Initialization

The automation framework and its integrated server instance are distributed via the Node package manager. Provision the tools global using the following directive:

npm install --global appium

Modern releases bundle the server functionality directly within the core package. Once installed, establish an APPIUM_HOME variable pointing to a dedicated workspace for drivers and plugins. Ensure the global npm binaries directory is registered in the system PATH.

Complete Toolchain Validation

Verify the assembled environment by launching the automation server. Execute the startup command and monitor the console for successful driver attachment and active network listeners:

appium --base-path /wd/hub

A successful initialization logs the active endpoints and confirms the environment is prepared for mobile automation workflows.