A Java API for searching and downloading Android applications from Google Play, with device emulation capabilities.
Google Play Crawler is a Java API that allows developers to programmatically search, browse, and download Android applications from the Google Play Store. It solves the problem of accessing Google Play's data and APK files without using the official Android app or web interface, enabling automation and integration into other tools.
Android developers, researchers, and automation engineers who need to interact with Google Play programmatically for app analysis, data collection, or bulk downloading.
Developers choose this tool because it provides a simple, command-line driven interface to Google Play's functionality without requiring complex reverse engineering. It offers device emulation, proxy support, and integration with both Maven and SBT build systems.
Play with Google Play API :)
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Emulates a Samsung Galaxy S3 and allows device checkin to generate ANDROID-ID, enabling programmatic registration with Google accounts for API access.
Provides a comprehensive CLI with subcommands for operations like download and search, plus configuration file support to streamline login and proxy settings.
Supports Maven and SBT build systems, with clear dependency references in the README, making it easy to incorporate into Java-based projects.
Includes a 'usegcm' option to simulate Google Cloud Messaging, allowing downloads triggered from the Google Play web interface directly to desktop.
Only emulates a Samsung Galaxy S3 by default; accessing apps for other devices requires manual modification of properties, as admitted in the TODO section.
Requires protobuf compiler version 2.5, an older version that may be difficult to install on modern systems and could cause compatibility issues.
Proxy configuration does not apply to the 'usegcm' option, limiting its utility in environments where all outbound traffic must be controlled.
Relies on Google account credentials for automation, which likely violates Google's terms of service and poses risks of account suspension or legal action.