Private previewWorkspaces are by invitation

HeedPost

01Collect

Feedback boardsBoards that ask for exactly what your team needs to act.Votes, comments & mentionsOne vote per person, threads with mentions, and notes only your team sees.In-app widgetFeedback from inside your product, from customers who are already signed in.

02Understand

Merge & duplicatesTen posts asking for the same thing become one, with every vote kept.User segments & revenueProSee which requests your biggest customers want, in dollars.InsightsWho reads, what's rising, and whether you answered.HeedPost AIPlus and ProTags, duplicate judging, drafts, summaries, themes and Ask, each with its own switch.

03Ship and tell

Roadmap & statusesMove a post and everyone who asked hears, in your own status words.ChangelogRelease notes linked to the requests behind them, mailed to everyone who asked.Notifications & digestThe right email to the right person, and a switch for every one.

04Run it

Activity logEvery change, who made it and when, a day at a time.Team, roles & sign-inUnlimited teammates, clear roles, and sign-in your way.Branding, domain & languagesYour logo and colour, your own domain, and 21 languages.ImportMove in from Canny, Featurebase or UserJot, with nobody emailed.

05Connect

Slack & issue trackersPlus and ProSlack threads, and issues in Linear, Jira, GitHub or ClickUp that move posts back.MCP serverPlus and ProYour AI agent can read, file, vote and ship, as you.REST APIPlus and Pro27 operations and one key: build anything on top of your feedback.WebhooksPlus and Pro110 events, signed and retried, the moment they happen.
AIDocsHelpPricingBlog

Collect

Understand

Ship and tell

Run it

Connect

Request an inviteSign in

Notes/Languages

Right to left is not a mirror image

What we learned making HeedPost read properly in Arabic, Hebrew and Urdu, and what doesn't flip.

Nº 32 · HeedPost team · Oct 17, 2026 · 2 min read

HEEDPOST NOTESNº 32

The first idea everyone has about right-to-left languages is that you flip the page. Put the menu on the right instead of the left, align the text to the right, done. That gets you about half way, and the other half is where it either feels native or feels like a mirror.

This is what we learned making HeedPost read properly in Arabic, Hebrew and Urdu.

Think in start and end, not left and right

The biggest change was in how the layout is described, not how it looks. Every "left" and "right" in our styles became "start" and "end". In English, start is left. In Arabic, start is right. Write it that way once and the layout follows the language by itself.

We rewrote 104 of those declarations. To be sure English didn't change, we took full-page screenshots of every page, at phone and desktop sizes, before and after, and compared them pixel by pixel. They were identical. Then we put one declaration back the wrong way round on purpose, to prove the comparison would catch it. It did.

Some things flip, some don't

Arrows that mean "next" or "back" flip, because the direction of reading flips. A chevron pointing to the next page points left in Arabic.

Other things keep their direction:

  • Numbers. "1,248" reads left to right inside Arabic text too.
  • Clocks and media controls. A clock still runs clockwise, and a play button still points the way it does everywhere.
  • Icons that aren't about direction, like a bell or a search glass.
  • Code, email addresses and URLs, which are always left to right.

Mixed text needs care

A board in Arabic will still contain English: a product name, a post someone wrote in English, a code sample. Text in one direction inside text in the other can rearrange itself in surprising ways, especially around punctuation and numbers. Each piece of text needs to know its own direction and be kept apart from its neighbours, so an English title inside an Arabic page reads correctly from start to end.

Fonts are part of it

Urdu is usually written in a flowing style called Nastaliq, with letters stacked diagonally. Its lines need roughly twice the height ours were designed for. For now we draw Urdu in Naskh, the style Arabic uses, which fits the layout. It's a decision we'd revisit once we can measure a page in Nastaliq properly.

Test it the way people read it

The best test is a person who reads the language, using the product for something real. Screenshots and tests catch layout bugs. Only a reader catches the moment where something technically correct still feels backwards. If you serve customers in these languages, ask one of them to try your board for ten minutes. It's the most useful ten minutes you'll spend on localisation.

Start hearing everyone.

Free for your first two boards, with no card.