Skip to content
pubscout

Compare

The strongest value in each row is marked.

Attributeexpand_tap_area

Manually expand the tap area of a widget without changing its size or layout.

pub.devRemove
hit

Decouple Flutter layout size from hit-test size to deliver taps outside parent bounds.

pub.devRemove
ScoresHealth5068 (best)
Maintenance055 (best)
Quality9197 (best)
Popularity70 (best)56
Community52 (best)41
Compatibility100100
UsageDownloads (30 days)22k (best)4.7k
Likes60 (best)54
Pub points140 / 160160 / 160 (best)
GitHub stars3850 (best)
MaintenanceLatest release1.1.1, 4 years ago1.2.4, 4 months ago (best)
Major versions in 12 months0 (best)1
Contributors3 (best)1
Publishermalikwang.comzennn.dev
FitPlatformsAndroid, iOS, Web, Windows, macOS, LinuxAndroid, iOS, Web, Windows, macOS, Linux
WASM-readyYesYes
KindFlutter widgetsFlutter widgets
Code generationNoNo
Direct dependencies00
LicenseMITMIT
Setup effortLowLow
JudgementStrengths
  • Does not change the widget's size or layout
  • Includes a debug flag (debugPaintExpandAreaEnabled) to display the actual expanded area
  • Enables precise separation of paint/layout bounds from hit-test bounds.
  • Includes a built-in Dart DevTools extension for inspecting hit scopes and debugging missed taps.
  • Supports slivers via SliverHitScope for custom scroll views.
Weaknesses
  • Expanded area cannot exceed the boundary of the Parent Box
  • Requires careful placement to avoid gesture conflicts when wrapped inside or outside other GestureDetectors
  • Deferred hit-testing is O(n) over registered targets on a scope, meaning large numbers of targets can affect performance.
  • Requires careful scope placement so that the HitScope's layout box actually covers the expanded hit area.
WarningsNoneNone
expand_tap_area vs hit: which Flutter package should you use? | pubscout