- Fix swipe-to-react: enable stable ids on MessagesAdapter so the swipe
callback resolves the swiped message (itemId was NO_ID -> lookup failed),
and anchor the reaction popup independent of swipe-recovery translation so
it no longer opens off-screen.
- Replace the typed-text reaction "+" with a themed, scrollable emoji grid
(EmojiPicker) generated from colour-emoji codepoint ranges plus a curated
common set. No third-party picker, so no Guava and it follows light/dark.
- Make the six quick reactions user-configurable and reorderable via a new
Settings -> Quick reactions editor; the double-tap default reaction now uses
the same grid picker instead of a raw text dialog.
- Pulse visible reaction badges (1 -> 1.4 -> 0.9 -> 1, cascaded 0.25s) when a
conversation opens with a reaction as its newest message.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
- Remove the message item OnTouchListener that was swallowing swipe
gestures, so ItemTouchHelper receives swipes again. Single-tap and
long-press use plain click/long-click listeners like the conversations
list; double-tap is detected via tap timing instead.
- Use ic_favorite_black_24dp for the REACT swipe action. message_emoji
is a transparent spacer shape, so it rendered no icon.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
- Rework the quik wire format: the visible body is now an iOS-style
fallback ("Reacted 👍 to \"...\"" or "Reacted 👍 to a message") and the
machine data (emoji, sender address, timestamp, text) is hidden in a
zero-width payload using U+2061..U+2064 so it never collides with the
iOS/Google tapback characters. Non-quik clients see a clean sentence.
- Fix swipe-to-react: the message item touch listener no longer consumes
events, so the RecyclerView's ItemTouchHelper receives swipes again.
- Restore long-press to select messages (removed long-press-to-react).
- Always hide our own outgoing reaction, even when the target message
can't be resolved locally, so the sender never sees the raw payload.
- Tune the reaction picker popup: theme-tinted background, themed text,
smaller emoji, and width capped to the screen so all options fit
without horizontal scrolling.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Add two reaction UX improvements on top of the send-reaction feature:
- Double-tap a message bubble to send the configured default reaction
emoji. A single GestureDetector on the item root now handles tap,
double-tap and long-press, leaving child view touch handling intact.
- Configurable per-direction message swipe actions (none, react, reply,
copy, forward, delete) via a new MessageItemTouchCallback that always
snaps the row back after a swipe. Adds a settings screen for the swipe
actions and a default-reaction emoji picker, backed by new preferences.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Address review findings on the send-reaction feature:
- Run permission checks on the main thread and only switch to IO for the
actual send, instead of touching the UI from a background thread.
- Parse outgoing reactions on the sender's own device. Sent messages don't
arrive back as incoming, so they would otherwise never be attached or
hidden until a full reparse.
- Anchor the reaction picker above the long-pressed message instead of
centering it on the screen, falling back to the list when off-screen.
- Always send reactions as group MMS in a group thread.
- Attribute our own reactions to our own number (via isMe + getMyPhoneNumber)
rather than the recipient's address, and show "Me" for them in the
reactions dialog.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Long-press a message to open an emoji reaction picker. Reactions are
sent as a plain SMS/MMS body using a quik-specific zero-width encoding
that carries the original sender's address and the message's timestamp,
so a receiving quik instance can attach the reaction to the exact
message via address + date lookup (fast path), falling back to the
existing text matching for non-quik senders.
The quik pattern is registered first so it wins over the generic Google
Messages pattern; iOS/Google parsing is unchanged. New ParsedEmojiReaction
fields are in-memory only, so no Realm migration is needed.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
The previous behavior fetched scheduled messages directly from the conversation adaptor. This was causing memory leaks and potentially crashes. Now, the view model fetches it and provides the data through state.
The app was setting gallery to black mode programmatically, and for some reason this was affecting other activities theming. We can just use a custom theme to force black mode that won't mess with other screens.