gplay-scraper

GPlay Scraper is a powerful Python Google Play scraper library for extracting comprehensive app data from the Google Play Store. Scrape Google Play Store apps to get ratings, install counts, reviews, ASO metrics, developer information, and 65+ data fields

Runs with mockssource: GitHubhomepagePythonMITcommit 304dcd3d3546

Python, MIT licensed. The project labels itself: android, app analytics, crawler, google, google play, play store, play store api and playstore.

gplay-scraper runs, with stand-ins for the services it depends on. An Argusic agent installed it in 0.2 minutes and hit 1 error and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.

gplay-scraper installed in a venv with all dependencies; all 48 tests pass after fixing the tls_client client_identifier string from 'chrome112' to 'chrome_112'

What the agent ended up with on a clean machine, in its own words. How this is measured

Measured by Argusic on a fresh machine every time. Every number links to its evidence. Argusic Score 92 of 100 (the mean of this project's run scores).

At a glance

verdict
Runs with mocks
Argusic Score
92 / 100
cost of the verifying run
$0.02 (measured)
recorded runs
1
last tested
stars
315
forks
34
open issues
4
watchers
11
size
2 MB
created
last push

Subject data from GitHub, linked at the top of this page, refreshed . Test data by Argusic (CC BY 4.0); every number links to a run page with the full log, the recording, and their sha256 hashes.

What was measured

From the run that decided this verdict. Every line is a recorded value, not an estimate.

Time lost to each failure while testing gplay-scraper, drawn from the recorded run
Every bar is a failure the agent recorded, with the time it cost. Drawn from this run, not from anywhere else.

What went wrong, in the agent's own words

The agent's own words, worst first, never rewritten into advice.

  • tls_client client_identifier 'chrome112' is invalid; library expects 'chrome_112'0.5 minutes
Install time
under a minute
Cold machine to finish
4 minutes
Errors hit and fixed
1 hit, 1 fixed with no human help
How the result was proved
pytest tests/ -v exited 0, 48 passed
Model tokens used
33,214
Exact commit tested
304dcd3d3546
Container image
sha256:cdd920bce783

What was not measured

The other half, so you can see exactly how far this evidence goes. A gap is printed as a gap and never filled in.

Peak GPU memory
this ran on a CPU machine, so there was no GPU to sample
Behaviour over a long run
each attempt uses the smallest documented settings and a fixed time budget, so this measures whether it runs, not how it holds up under load
Behaviour against real services
this run was verified against stand-in services only

The end of the recording

The last lines of the terminal session that decided this verdict, exactly as they were recorded.

        self.assertTrue(hasattr(scraper, 'developer_print_all'))
        # List methods
        self.assertTrue(hasattr(scraper, 'list_analyze'))
        self.assertTrue(hasattr(scraper, 'list_get_field'))
        self.assertTrue(hasattr(scraper, 'list_get_fields'))
        self.assertTrue(hasattr(scraper, 'list_print_field'))
        self.assertTrue(hasattr(scraper, 'list_print_fields'))
        self.assertTrue(hasattr(scraper, 'list_print_all'))
All 48 tests pass. The tests verify object initialization, method availability, and that all 7 HTTP…
tokens used
33,214
All 48 tests pass. The tests verify object initialization, method availability, and that all 7 HTTP…

Replay the whole session, every command from a clean machine to this point.

How it was tested

One agent, one container, no human help. It installs the project the way its own documentation says to, runs it, and fixes what breaks. Everything below is recorded as it happened: the terminal session, the log and the exact commit. The full method.

Strengths and limits

Measured facts, not opinions. How this is written.

What went well

  • Installed in 0.2 minutes, faster than the median of the 30 comparable projects Argusic has measured.
  • Recovered from all 1 error without a human stepping in, which says the failures are documented well enough to solve.
  • Licensed MIT, as reported by its host.

What did not, or is not known

  • Only reached a running state against stand-in services, so nothing here proves it works against the real ones.
  • Measured once so far. A single attempt shows it can run, not that it runs reliably.

Of the 31 android projects Argusic has installed and timed, gplay-scraper was the 3rd fastest to reach a running state, and 24 of 31 reached one at all.

Also tested, in the same area

Every one of these was installed and run by Argusic on a clean machine. Nothing appears here that was not tested.

Run history

tested byattemptoutcomescorecost USDwhen
Argusic Runner1/3Runs with mocks92.000.02

Topics (from GitHub)

androidapp-analyticscrawlergooglegoogle-playplay-storeplay-store-apiplaystorescarperscraper

Embed the badge

Markdown for the project README. It links back here; terms on the terms page.

[![Tested by Argusic](https://argusic.com/badge/gplay-scraper.svg)](https://argusic.com/subject/gplay-scraper)

Questions

Does gplay-scraper run?
gplay-scraper runs, with mocks standing in for external services. Argusic installed and launched it on a clean machine in 0 minutes, hitting 1 error on the way, and recorded the session.
How did Argusic test gplay-scraper?
On a fresh, disposable machine, with every command recorded and the repository pinned at commit 304dcd3d3546. One attempt is recorded, and the full method is on the methodology page.
What did it cost to test gplay-scraper?
The run that produced this verdict cost $0.02: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
How long does gplay-scraper take to install?
0.2 minutes in the run that decided this verdict, from a clean machine to a running state. That is one measured attempt, not an average.
Does gplay-scraper need a GPU?
Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing gplay-scraper?
1 thing broke in the recorded run, and 1 were fixed without human help. Each one, and the time it cost, is listed on this page.
How does gplay-scraper compare with the alternatives?
Of the 31 android projects Argusic has installed and timed, gplay-scraper was the 3rd fastest to reach a running state, and 24 of 31 reached one at all.
Where is the evidence for gplay-scraper?
The recorded run is on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.

Discussion