dotnet/maui

GraphicsView line stroke rendering inconsistent on Android compared to other platforms

Open

#32,465 opened on Nov 10, 2025

View on GitHub
 (1 comment) (0 reactions) (0 assignees)C# (1,951 forks)batch import
area-drawinggood first issueplatform/androids/triageds/verifiedt/bug

Repository metrics

Stars
 (23,245 stars)
PR merge metrics
 (Avg merge 47d 9h) (248 merged PRs in 30d)

Description

Description

When using GraphicsView with a custom IDrawable implementation to draw grid lines, the stroke rendering on Android looks visually different compared to other platforms like windows. The lines appear thinner or inconsistent even when the same StrokeSize and color are applied.

Steps to Reproduce

  • Download and run the attached sample project on Android.

BorderSample.zip

Expected Behavior Grid lines should have consistent stroke thickness and appearance across all platforms when using the same StrokeSize and color.

Actual Behavior On Android, the grid lines appear visually thinner or inconsistent.

(See attached screenshot for reference.)

Link to public reproduction project repository

No response

Version with bug

10.0.0-rc.2

Is this a regression from previous behavior?

Not sure, did not test other versions

Last version that worked well

Unknown/Other

Affected platforms

Android

Affected platform versions

No response

Did you find any workaround?

No response

Relevant log output

Contributor guide

Research direction
Investigate the StrokeSize rendering on Android in MAUI GraphicsView. Compare with Windows implementation and check if the stroke is affected by density or scaling. Look into the SkiaSharp canvas drawing.
Tech stack
csharp
Domain
mobile
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
Git
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
70