appium/java-client

Java language binding for writing Appium Tests, conforms to W3C WebDriver Protocol

Hosted by OpenJS Foundation · part of Linux Foundation

View on GitHub ↗Jump to charts ↓Open shareable report →

appium/java-client has 1k+ stars and 750+ forks on GitHub, is written in Java, and was last pushed on Oct 18, 2026. Data as of . Signed-in members get hourly updates — create a free account.

Summary Information

Updated 2 hours ago
Added to GitGenius on October 15th, 2026
Created on April 4th, 2014
Open Issues & Pull Requests: 266 (+0)
GitHub issues: Enabled
Number of forks: 756
Total Stargazers: 1,283 (+0)
Total Subscribers: 150 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 4.0 hours
Mean response time: 63.1 days
90th percentile: 33.6 days
Tracked items: 44

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 17
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 1,100 days
Stale 30+ days: 16
Stale 90+ days: 16

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

  • bug (6)
  • User side problem/problem of an external tool (3)
  • NeedsInfo (2)
  • invalid (2)
  • Android (1)
  • CI (1)
  • Good First Issue (1)
  • Needs investigation (1)

Most active issues this week

Sign in to see which issues are moving.
Sign in

Detailed Description

Appium Java Client is a Java language binding for writing automated tests against mobile and desktop applications using the WebDriver Protocol.

The tool solves the problem of testing applications across Android, iOS, macOS, and Windows platforms by providing Java developers with a standardized interface to Appium servers. It implements the W3C WebDriver Protocol, allowing developers to write tests that conform to industry standards while leveraging Appium's cross-platform automation capabilities. The client abstracts the complexity of communicating with Appium servers and handles platform-specific details through a unified API.

Teams should adopt this tool if they are building Java-based test automation suites for mobile or desktop applications and want to leverage Appium's capabilities without writing raw protocol calls. It suits projects that need to test across multiple platforms with a single codebase and organizations already invested in Java and Selenium ecosystems. The tool requires careful attention to version compatibility, as the README emphasizes that Selenium does not follow semantic versioning, meaning breaking changes can occur in patch releases, necessitating specific version pinning between the Java client and Selenium dependencies. The project provides detailed migration guides for moving between major versions, which is essential reading when upgrading.

The project maintains active migration documentation across multiple major versions, indicating ongoing evolution and breaking changes as dependencies shift. The tool has undergone significant architectural changes, including a shift to depend on selenium-api only and a requirement that users run Java 11 or above, showing willingness to modernize the codebase. The project publishes both stable releases through Maven Central and pre-release versions through alternative channels, providing options for teams at different stages of adoption.