TypoGuard

if you need a to try a a uniuque spell to you can diffently try this prouct

Good and useful product

Nice work on TypoGuard! Fixing typos right where people type, like chat boxes, Gmail, and AI assistants, is a practical idea, and the ‘Did you mean’ inspiration makes it easy to grasp. I like that it’s available on Chrome, Edge, and Firefox, and that the free plan lets people try it before upgrading. Congrats on the launch!

Nice work on TypoGuard! Fixing typos right where people type, like chat boxes, Gmail, and AI assistants, is a practical idea, and the ‘Did you mean’ inspiration makes it easy to grasp. I like that it’s available on Chrome, Edge, and Firefox, and that the free plan lets people try it before upgrading. Congrats on the launch!

Good call excluding password, card and OTP fields by type and autocomplete attribute. How does it handle rich editors like Gmail compose where the field is not a plain input, and can I turn it off for a single site?

this fixes so much of the issues that were taking time..would recomment it

Really clean execution on TypoGuard! Having a focused, low-friction workflow makes onboarding much smoother for first-time users. Curious how you are prioritizing power-user shortcuts versus keeping the core interface lightweight as you add new features?

The exclusion of password, card, CVV, OTP and PIN fields by input type, autocomplete and field name is the part I would want to verify before installing. Does the red underline also skip contenteditable editors that are not real inputs, like some rich-text comment boxes, or only standard form fields?

Good call limiting detection to the field being edited and excluding password, card and OTP inputs by type and name. Keeping it to spelling only rather than rewriting sentences is a clear scope, and it would be helpful to know how it handles non-English text in mixed-language messages.

Excluding password, card, and OTP fields by type, autocomplete, and name before any read is the right boundary for an in-page spell checker. Keeping the model to spelling only, not grammar or voice, also avoids rewriting someone mid-sentence. On a rich-text editor, does the red underline survive when the field re-renders, or does it only mark plain inputs?

Because great ideas deserve better than a typo! 👀 Love the idea of catching mistakes as you type, without interrupting your workflow. Small corrections, big difference in productivity!

The "what it does not do" section is what made me read the rest: excluding password/OTP fields by input type and autocomplete attribute, reading only the field you are actively editing, and not persisting what you type. That is the right set of tradeoffs for a spell checker that lives inside other people's forms. One real question: in rich-text editors that virtualise long documents (Notion, Google Docs, Slack composer), does the red underline anchor to the actual typo position, or does it drift to the end of the block once the editor re-renders? That is where most inline correctors fall apart in my experience.

The "what it does not do" section is what made me read the rest: excluding password/OTP fields by input type and autocomplete attribute, reading only the field you are actively editing, and not persisting what you type. That is the right set of tradeoffs for a spell checker that lives inside other people's forms. One real question: in rich-text editors that virtualise long documents (Notion, Google Docs, Slack composer), does the red underline anchor to the actual typo position, or does it drift to the end of the block once the editor re-renders? That is where most inline correctors fall apart in my experience.

Skipping password, card and OTP fields by default is a really thoughtful touch, and it's the first thing I'd worry about with an extension that reads text fields. How does it handle rich-text editors like Notion or Google Docs, where the text isn't a plain input? And is grammar on the roadmap, or are you keeping it spelling-only on purpose?

Good call excluding password, card and OTP fields by input type and autocomplete attribute. Does it handle multilingual typing, or switch dictionaries when someone mixes languages in one field?

Super helpful! Excited to see how the AI spell-checking performs.

Super helpfuI! Excited to see how the AI spell-checking performs.

Good that the excluded fields are listed by input type, autocomplete and name. One case that slips past all three: plain text fields that hold secrets anyway, like an API key box in a dashboard or a recovery code field typed as text. Do you skip strings that look like keys (long, no spaces, mixed case and digits) before they leave the browser?

Super helpful UI! Excited to see how the AI spell-checking performs.

This is very helpful for writers who face spelling issues.

Since it only fixes spelling and leaves grammar alone, does it handle names and technical jargon without flagging everything in red? A per-site pause or a custom dictionary would be handy for developer and support-team use.

I'm surprised how many typos I got from AI and myself. Great idea, I would just allow people to add their tone. Speaking perfectly isn't always what people want.

Very helpful, does everything as advertised, good job!

Such a useful tool! I love how TypoGuard makes real-time spell checking effortless across different websites.

This is an extremely useful tool for anyone who is deeply involved in technology

Amazing, good work. Congratulation.

Goog idea! nice work and I think the same this fixes so much of the issues that were taking time..would recomment it

Drawing the line at spelling, not grammar or style, is a good call. Rewrite tools tend to flatten everyone's voice. How does it handle words that are correct but uncommon, like product names, slang, or a non-English word mixed into an English sentence? Is there a personal dictionary, and does it learn from the suggestions I dismiss?

looks good. very useful tool

Catching typos directly in the field, rather than after copying text elsewhere, is a clear time-saver for email and chat. I like that it only corrects spelling and leaves grammar alone — how does it handle proper names and domain-specific terms so they are not repeatedly flagged?

Great execution on the onboarding flow and clean UI layout! How are you handling real-time state updates and scaling under peak concurrent traffic?

Great work, would love to know how do you differentiate from Grammarly? Also great website, landing page, but would like to let you know that in some places the website looses it's consistency. You might want to check that out. All the best!

Good call keeping it to spelling only instead of rewriting sentences. Does it handle mixed-language typing, for example an English email with a few Spanish or German words, or does it flag those as mistakes? A way to add custom words like brand names would be really useful too.

The page says it corrects spelling only, not grammar or style, and that it reads just the field being edited. How does the underline behave in rich-text editors that re-render often, such as the compose box in Gmail?

Correcting spelling only, without rewriting the sentence, is the useful constraint. A red underline in the field you are already typing is less friction than pasting a draft into another tab.

Keeping spelling corrections separate from style rewrites makes the scope clear. Can a correction be undone with one click or a keyboard shortcut? Showing both the original word and the replacement would help people catch an incorrect suggestion without losing their place.

Nice work. TypoGuard is looking good.

The choice to correct spelling only, and not rewrite grammar or style, is what would make me trust this in Gmail. A one-click wavy underline that discards the text after the response is a clearer privacy story than most writing extensions. Does the free plan cap checks per day, or is the limit only on which sites it runs on?

This is actually a pretty useful little app. Finding quality frumples in the endless jungles of Jabberwocky is harder than it looks, and the automatic squiggle detection seems like a smart solution. One thing I'd love to see is a way to adjust the snicker-snack intensity per subreddit, since some borogoves are much more sensitive to promotional galumphing than others. Great idea and looking forward to seeing how it evolves!

I like that you spelled out what it doesn’t do: no password/OTP fields, only the field being edited, and spelling only, no rewriting. That’s what would make me trust a browser extension like this. One question: how does it handle names and technical terms (product names, code identifiers) inside a sentence? Is there a personal dictionary or an “ignore” option so they don’t keep getting flagged?

Does the spell check work offline, or does every correction need a round trip to your backend? Curious how noticeable the latency is while typing fast.

I like that you spelled out what it doesn’t do: no password/OTP fields, only the field being edited, and spelling only, no rewriting. That’s what would make me trust a browser extension like this. One question: how does it handle names and technical terms (product names, code identifiers) inside a sentence? Is there a personal dictionary or an “ignore” option so they don’t keep getting flagged?

this fixes so much of the issues that were taking time..would recomment it

this fixes so much of the issues that were taking time..would recomment it

this fixes so much of the issues that were taking time..would recomment it

Cool project! congrats on the launch.

Clear positioning. I like that it only reads the field you are editing and skips password inputs, which is spelled out plainly. Handy for a founder writing a lot of emails. — Rob Eley, RFPG

The spelling-only scope is the smartest decision here — rewrite tools always flatten my voice, so a tool that just catches typos in the field I'm typing in is exactly what I want. The privacy boundary (never reading password/OTP fields, only the field being edited) is clearly explained, which builds trust. One question: does it handle names and technical jargon, or can I add words to a personal dictionary so my project names don't get flagged every time?

really cool and easy to get started

Our care coordinators write a lot of quick emails and portal notes to families, often in English mixed with Spanish or Bengali, so spelling-only (no rewriting) is the right scope for us. Two things would decide it: can we add care-industry terms and program names to a shared team dictionary, and does it stay quiet on non-English words in a mixed-language sentence instead of underlining all of them?

The explicit spelling-only scope is useful for messages where preserving the writer’s voice matters. A custom dictionary for names, job titles, and credential abbreviations would be especially helpful in resumes and cover letters. Is a personal dictionary planned?