_handleSwipeEnd doesn’t verify that the swipe being ended still corresponds to the message being handled (it doesn’t check _swipeTrackingMessageId and doesn’t track the pointer id). With multi-touch (or overlapping gestures), a second pointer can overwrite _swipeStartPosition/_swipeTrackingMessageId, and the first pointer’s onPointerUp can incorrectly trigger reply on the wrong message. Track PointerDownEvent.pointer and validate both pointer id and message id in update/end before applying the threshold / replying.

_handleSwipeUpdate calls setState on pointer-move events, which will rebuild the whole ChannelChatScreen (including the ListView) at gesture sampling rates and can cause jank on long chats. Consider moving the swipe offset into a per-message widget/state (e.g., a dedicated StatefulWidget for a bubble with its own setState/ValueNotifier) so only the swiped row repaints, or otherwise avoid screen-level rebuilds for pointer updates.

_resetSwipe always calls setState(() => _swipeOffset = 0) even when no swipe occurred (offset already 0). Since onPointerUp runs for every tap/scroll interaction on a message, this forces an extra rebuild for normal taps and scrolls. Guard the setState (only when _swipeOffset != 0 / swipe was active) and update _swipeStartPosition/_swipeTrackingMessageId inside the same setState to keep state mutations consistent.

In the dead zone calculation on line 158, the multiplier 0.08 seems arbitrary and could benefit from a named constant or comment explaining its purpose. The magic number makes it difficult to understand the intended sensitivity behavior in the dead zone.

The AnimatedContainer animates the transformation when swipeOffset changes, but during an active drag gesture (when the user is swiping), the animation duration of 150ms creates a lag between the finger position and the visual feedback. This can make the swipe feel unresponsive or sluggish.

Consider disabling the animation during active drag by checking if _swipeTrackingMessageId is set, and only animating when snapping back to the original position after the gesture ends.

The reply hint content (icon and text) is duplicated in two places - once for left-aligned swipes (lines 564-577) and once for right-aligned swipes (lines 585-598). This duplication makes the code harder to maintain. Consider reusing the same content widget and only changing its position in the Row for the right-aligned case.

The maxSwipeOffset (64.0) and replySwipeThreshold (48.0) are defined as local constants within the _buildMessageBubble method. Since these values are recreated on every build, consider extracting them as class-level constants (e.g., static const) to avoid repeated allocations and improve code organization.

The division check if (abs <= 0) on line 154 is redundant since abs is the result of .abs() which is always non-negative. The condition should be if (abs == 0) to properly check for zero, though even this is not strictly necessary since the subsequent calculations would naturally return 0 when abs is 0.

The channelMessage: true parameter is being passed to ChannelMessagePathScreen, but this parameter doesn't exist in the constructor definition. The constructor only accepts message parameter (see channel_message_path_screen.dart:21). This will cause a compilation error. Remove the channelMessage: true parameter from this call.

_applySwipeResistance computes curved using math.pow, which returns a num. That makes the final expression a num, but the method return type is double, so this will fail strong-mode type checking. Convert the pow(...) results (and/or the final expression) to double before returning.

ChannelMessagePathScreen is constructed with a channelMessage: named argument here, but the current ChannelMessagePathScreen constructor only accepts {message}. This will not compile unless the screen is updated to accept that parameter (or the argument is removed).

_applySwipeResistance uses math.pow(...) which returns num, so curved and the final multiplication become num. Since the method returns double, this is likely a compile-time type error (returning num where double is required). Convert the pow results to double (or otherwise ensure the expression is typed as double) before returning.

ChannelMessagePathScreen is instantiated with a channelMessage named argument, but the current ChannelMessagePathScreen constructor only takes {super.key, required this.message}. This will not compile unless the other screen is updated accordingly. Either remove this argument or update ChannelMessagePathScreen to accept and use it.

Swipe tracking calls setState from onPointerMove, which will rebuild the entire ChannelChatScreen at pointer-move frequency while swiping a single message. In busy channels this can cause jank. Consider isolating swipe state to the message bubble (e.g., a dedicated stateful widget / ValueNotifier + ValueListenableBuilder) so only that row repaints during the gesture.

ChannelMessagePathScreen constructor (in channel_message_path_screen.dart) only accepts {message}; passing channelMessage: true here will not compile. Either remove the argument or update ChannelMessagePathScreen to declare and use a channelMessage named parameter (and update other call sites accordingly).

_applySwipeResistance returns a double, but return 0; returns an int and will fail strong-mode type checking. Use 0.0 (or rawOffset if you want to preserve sign) to keep the return type consistent.

onPointerUp calls _handleSwipePointerUp for any pointer, but _handleSwipePointerUp doesn’t verify event.pointer == _swipePointerId. A second finger lifting (or another pointer) can reset the swipe or even incorrectly trigger a reply using a mismatched start position. Gate the onPointerUp handler (and possibly onPointerCancel) by pointer id, similar to _handleSwipePointerMove.

hintBuilder takes {isStart} and _buildReplySwipeHint has separate start/end layouts, but _SwipeReplyBubble always calls hintBuilder(isStart: false), making the isStart: true branch dead code. Either wire isStart based on swipe direction / bubble alignment, or simplify the API by removing the unused parameter/branch.

Remove undefined constructor argument

ChannelMessagePathScreen is constructed with channelMessage: true, but the screen constructor only defines ChannelMessagePathScreen({super.key, required this.message}) in lib/screens/channel_message_path_screen.dart (no channelMessage named parameter). This introduces a hard compile error (undefined_named_parameter) and prevents the app from building with this change.

Useful? React with 👍 / 👎.

this is so dumb... it not a problem

Gate swipe lock on vertical motion

The swipe lock checks only horizontal delta (dx) and ignores vertical displacement, so diagonal drags used to scroll the chat can still lock into reply-swipe mode once dx passes 12 px. On touch devices this can trigger accidental replies during normal list scrolling, because _handleSwipePointerUp later evaluates the horizontal peak against the reply threshold.

Useful? React with 👍 / 👎.

this not a problem i have noticed.