I m building ToolkitLoop, and I made one deliberate choice in its Character Counter: the main number is the number of characters a person can actually see. A family emoji, a flag, or an accented letter can involve several underlying code points. Showing those technical values as the default can make a short piece of text look much longer than it feels to the person writing it. So General mode starts with visible characters and a custom limit. The technical details are still available when needed: graphemes, code points, UTF-16 units, and UTF-8 bytes. For platform-specific writing, the tool switches rules for X and SMS rather than treating every platform as the same limit. I m still debating the default UI: should advanced counts be visible immediately for everyone, or stay tucked away until someone needs them? For people building writing tools or developer tools, which option would you prefer?
My first instinct was to show one simple count. Then I ran into a problem: writers usually care about visible characters, while browser form limits can use UTF-16 code units. A draft can look fine in one counter and still fail a form field.
I m considering two approaches:
Show only a simple count until someone selects a target like web form .
Show both counts from the start, with a short explanation.
I lean toward the first option because most people should not need Unicode terminology while writing.
ToolkitLoop makes small online tasks feel simple again. Start with a private Word Counter that instantly tracks words, characters, sentences, paragraphs and reading time in your browser—no signup, no raw-text uploads.
