Rightwards Pushing Hand

🫸 is the emoji of forward-coded moving-on — a hand pushing to the right, the iconography of forward-momentum-coded direction, 'next' dismissal-coded swipe, and the universal 'moving on' tag. Where 🫷 reads as leftwards-pushing-coded rejection and 👉 reads as pointing-right-coded highlight, 🫸 captures the moment when the sender wants to communicate forward-coded dismissal energy — a 'next 🫸' moving-on-coded reveal or a 'swipe next 🫸' forward-momentum-coded message. The rightwards-pushing hand borrows from the universal swipe-forward tradition and the modern moving-on-coded forward aesthetic, which is exactly why the emoji reads as forward-coded rather than literal right-push.

In real-world usage 🫸 lives in the spaces where the sender wants to communicate moving-on-coded dismissal. A partner sends it on a 'that's in the past 🫸' moving-on-coded check-in. A friend sends it on a 'next 🫸' forward-momentum reveal. A coworker sends it on a 'swipe next 🫸' dismissal-coded message. The rightwards-pushing hand is what makes the emoji feel forward-coded — it is not just 'hand,' it is 'push-right-coded moving on.'

What separates 🫸 from the rest of the hands family is the forward-coded dismissal register. The emoji is not saying 'leftwards push' (🫷), 'pointing right' (👉), or 'fingers splayed' (🖐). It is saying 'moving on,' which carries a specific swipe-forward tradition. That is why 🫸 travels especially well on moving-on-coded reply tweets, forward-momentum-coded flat-lays, and any context where the sender wants the message to land with forward-coded dismissal energy.

🫸 shows up as the closer on a 'next 🫸' moving-on-coded check-in, the punctuation on a 'that's in the past 🫸' forward-coded reveal, and the softener on a 'swipe next 🫸' dismissal-coded message. It pairs naturally with sentences that name the forward-coded energy — 'next,' 'moving on,' 'swipe next' — and sits beautifully on moving-on-coded reply tweets and forward-momentum-coded captions.

In group chats 🫸 anchors 'next moment' threads, forward-coded reveals, and 'next 🫸' coded tags where the rightwards-pushing hand matches the register. On Instagram it lands on forward-momentum-coded flat-lays and moving-on-coded story reposts. On TikTok it travels in moving-on-coded transitions and 'next 🫸' reaction content.

The emoji also works in dating contexts. A 'that's in the past 🫸' partner message uses the rightwards-pushing hand to communicate forward-coded moving-on romance. Across all of these surfaces the rule is the same: the more forward-coded the moment, the more natural 🫸 feels.

Skip 🫸 in sympathy, condolence, or tender-coded contexts. The forward-coded moving-on cue is the wrong tone for any conversation where the moment is heavy. A quiet ❤️ or a sentence that acknowledges the moment is a better fit.

Avoid 🫸 in coded-conflict or coded-shutdown contexts where the forward-coded energy feels off. A 'next 🫸' message works for moving-on-coded reveal; for tender moments use 🤗 or a sentence.

Skip 🫸 when you want to communicate rejection. The forward-coded register is too moving-on for outright rejection; use 🫷 when the boundary needs to land reject.

If someone sends 🫸, the cleanest mirror is another 🫸, 🫷, or a sentence that joins the forward-coded energy. If you want to escalate the engagement, follow with a sentence that adds context: 'next together' or 'moving on for sure.' If the rightwards-pushing hand feels too forward-coded, reply with a softer emoji (❤️ or 🤝) that signals direction without matching the moving-on volume.

When 🫸 lands as a partner 'that's in the past 🫸' check-in, mirror with another 🫸, a heart emoji, or a sentence that escalates the romance. When it arrives as a 'next 🫸' moving-on-coded reveal, mirror with another 🫸, a sentence that joins the team energy, or a direction emoji that matches.