Hey all-- I'm one of Ditto's cofounders. Grateful for all of the support when we Launched on HN a bit ago. Happy to answer any questions if anyone has any!

Just wanted to follow up on this and mention that we've just rolled out our localization features. Ditto now handles variants (including languages, user segment-based text, and more). I wrote about it here: https://www.dittowords.com/blog/introducing-variants-for-loc...

It's been in development/QA for a while, and we were super excited to see all the feedback and questions about localization during our launch.

Frankly we're flattered that our launch has gotten the attention of localization tools (hi localazy + lokalise, thanks for joining us on HN!). Always appreciate others working on solutions for product text in all of its stages.

Although we do think we play an integral part in the product development process, if teams switched off Ditto, they wouldn't be any worse-off than they were before. The text would still exist in their mockups, and their apps can continue to serve the structured JSONs of text that we generate. Because we aren't a CDN, they aren't dependent on us to actually serve that text.

However, we do hope to have an on-prem offering for enterprise customers in the future, especially those with tighter security constraints!

Thanks so much for the support -- we feel really lucky and excited to have been able to grow Ditto over the last year. :)

Right now, teams in Ditto use it as a translation/l10n solution if they already localize their mockups. However, we are hoping to support this more fully in the very near feature (likely this upcoming week!) with the ability to create variants of text in mockups in Ditto (including languages, user groups, states, etc.).

That means a lot, especially because we handle all of the design (including the landing page) in-house. Thanks for the support!

We're actually launching a feature called Variants to tackle this very use case (and translations) in our app in the next few days! It's definitely been highly requested by teams using Ditto and will hopefully allow them to create variations of text for different mediums, audience, user segments, etc.

Curious to hear what kinds of audiences/mediums of communication you typically account for in your product, and how much variation in the product text is written for each?

decision maker, technical, non-technical, investor, slides vs web, high level vs low level, age, expert vs beginner, user category A vs user category B, casual vs formal, brief vs expanded. so multiple tags would be best? maybe grand vision this could be different UIs for skill-level.

Hey Tejas, great to see you here on HN! Thanks for the support both then and now :)

Thank you for your support!

Definitely been there as an engineer as well. The amount of overhead and engineering time it takes to make punctuation changes, fix spelling errors, and even simple iterations to copy in-app only increases as a product's surface area increases. Thanks for forwarding us along!