Repository navigation
Alternative profiling methods for mobile-only contributors (Acode performance standards) #3101
Unanswered
AuDevTist1C
asked this question in
Q&A
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
When evaluating pull requests and performance benchmarks, it is essential to account for the stark hardware realities and environmental constraints faced by developers around the world.
Some devs like me do not own a PC, and our working family members are unable to purchase one due to financial limitations, forcing us to write and test code entirely on budget mobile devices.
Major browser vendors consistently refuse to implement native mobile DevTools support without desktop PC reliance, dismissing mobile debugging capabilities under the umbrella of performance concerns.
While there is currently only one mobile browser capable of handling such tasks—namely, Kiwi Browser—it remains stuck on an ancient version of Chromium because its solo developer has long abandoned active maintenance due to personal time constraints.
Given these systemic hardware barriers that prevent mobile-only contributors from capturing traditional desktop profiling metrics, is there any other way to get "a profile from Acode showing the code is an actual bottleneck, with before/after numbers from the app"?
Exploring alternative lightweight logging or in-app measurement techniques would greatly assist developers with limited resources in meeting contribution standards without requiring expensive desktop hardware.
Google Gemini 3.5 Flash-Lite "with auto selection"
All reactions