Subject: Feature Request - Add Fast Scroller for Code Viewing on Mobile

[MadaraMods]

Dear GitHub Mobile Team,

I'd like to suggest a quality-of-life improvement for the mobile code viewing experience.

Current Issue:
When reviewing code files on the GitHub mobile app,scrolling through long lines of code becomes tedious and time-consuming. Many code lines extend beyond the screen width, requiring excessive horizontal scrolling which disrupts the code review flow.

Suggested Solution:
Please implement afast scroller or horizontal scroll enhancement feature specifically for code viewing. This would significantly improve the experience for developers who need to quickly review and analyze code on mobile devices.

Benefits:

· Faster code navigation and review
· Improved productivity for mobile developers
· Better user experience for code analysis
· Reduced frustration with long code lines

Use Case:
As someone who frequently reviews code on mobile,this feature would save considerable time and make the mobile code review process much more efficient.

Thank you for considering this suggestion. The GitHub mobile app is already great, and this addition would make it even better for the developer community.

Computer vs. Mobile Experience:
On desktop computers,users can quickly scroll through code using a mouse wheel or touchpad, allowing for smooth and efficient code navigation. This ease of scrolling significantly enhances the code review process. However, on mobile devices, the lack of a similar fast-scrolling mechanism makes code review much more challenging and less efficient

Suggested Solution:
Please implement afast scroller or horizontal scroll enhancement feature specifically for code viewing. I want mobile users to benefit from the same scrolling convenience that desktop users enjoy, through a FastScroller implementation. This would significantly improve the experience for developers who need to quickly review and analyze code on mobile devices

[HenSquared]

Hey @MadaraMods thanks for contributing by providing feedback for us. I've created an issue internally for our Android team to look at this.