Feature Request: Add support for external activity discovery tools (e.g. activity_finder)
Maintainers usually reply within 3 days
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
Research direction
No files, tests, or entry points are identified in the issue. First clarify whether the goal is an Appium client API, plugin or hook interface, or external-tool integration, then define the supported Android behavior and tests that would establish completion.
Written by the indexing model from the issue text.
Description
Hi Appium team,
I would like to propose a feature enhancement that may improve Android automation debugging and activity handling.
I have developed a lightweight open-source tool called activity_finder:
https://github.com/jaxonister/activity_finder
Problem
In real-world Appium automation, especially on Android, one common challenge is discovering:
- current foreground activities
- available activities in an app
- activity transitions during testing
This often requires multiple adb commands or manual inspection, which slows down debugging and test development.
Proposal
The tool activity_finder provides a simple way to:
- list and detect Android activities
- identify current running activity
- help quickly locate target activity for automation scripts
It could be useful if Appium could:
- integrate similar activity discovery capability
- or provide a plugin / hook interface for external tools
- or expose a standardized API for activity inspection
Why this matters
Better activity visibility would significantly improve:
- test stability
- debugging efficiency
- onboarding for new automation engineers
Optional integration idea
Even a simple command or extension like:
driver.getCurrentActivity()driver.listActivities()
would help bridge this gap.
Conclusion
I believe this feature could improve Android automation workflows in Appium ecosystem, and I would be happy to contribute or discuss implementation ideas further.
Thanks for your time 🙌
- Dominant language
- Python
- Stars
- 1.8k
- Forks
- 570
- Avg merge
- 1d 10h
- Merged PRs (30d)
- 24
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from appium/python-client
-
question
Difficulty 4/5 3-5 days Newbie friendliness 25/100
appium/python-client#1168 · 9 comments ·
Maintainers usually reply within 3 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 55/100
appium/python-client#1147 · 7 comments ·
Maintainers usually reply within 3 days
-
Difficulty 3/5 1-2 days Newbie friendliness 38/100
appium/python-client#1091 · 4 comments ·
Maintainers usually reply within 3 days
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
appium/python-client#1076 · 2 comments ·
Maintainers usually reply within 3 days
-
Difficulty 4/5 3-5 days Newbie friendliness 20/100
appium/python-client#980 · 7 comments ·
Maintainers usually reply within 3 days
All issues in appium/python-client
Similar issues
-
pydanty:is-working
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
pydantic/pydantic-ai#8843 ·
Maintainers usually reply within 1 day
-
breaking change enhancement server
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
sktime/sktime#11310 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
needs-triage
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
Maintainers usually reply within 1 day