However this landing page is not doing a great job at explaining the solution. I'm sure once you see the product everything clicks but the current communication is not really explaing well this problem or showcasing well the features and workflows of your solution.
Launch HN: Ditto (YC W20) – Keep product text in sync from design to production
21–30 of 72 posts
Re: Launch HN: Ditto (YC W20) – Keep product text in sync from design to production
#22Re: Launch HN: Ditto (YC W20) – Keep product text in sync from design to production
#23Re: Launch HN: Ditto (YC W20) – Keep product text in sync from design to production
#24Why limit Ditto to only text assets?
Re: Launch HN: Ditto (YC W20) – Keep product text in sync from design to production
#25I understand the problem that you guys are trying to solve. I experience this pain eveyday at my job. However this landing page is not doing a great job at explaining the solution. I'm sure once you see the product everything clicks but the current communication is not really explaing well this problem or showcasing well the features and workflows of your solution.
But maybe they could move the demo video closer to above fold? Also, is booking a demo really the most important CTA?
Re: Launch HN: Ditto (YC W20) – Keep product text in sync from design to production
#26I understand the problem that you guys are trying to solve. I experience this pain eveyday at my job. However this landing page is not doing a great job at explaining the solution. I'm sure once you see the product everything clicks but the current communication is not really explaing well this problem or showcasing well the features and workflows of your solution.
Re: Launch HN: Ditto (YC W20) – Keep product text in sync from design to production
#27Congrats on the launch, looks great! Couple of questions: 1. Do you support localization? 2. Do you think there is a benefit to using this in addition to a headless CMS that is already managing authored content? At my previous company we did a lot of AB testing around product copy in our signup funnel which was surprisingly effective. This could be a really useful feature to include in the future
2. We built Ditto to specifically tackle product copy, whereas existing CMSs (including headless CMSs) are much more geared for marketing copy (longer form, clear H1/H2/body structure, authorship, etc.) -- which we think are pretty different use cases. With product copy and microcopy, teams have to think a lot more about how that fits into the UI/design/implementation; we're also excited about how our CLI can fit into teams' dev processes (like CI/CD) to streamline workflows!
3. Yup, we're super excited about all the potential extensions of Ditto, A/B testing included.
Re: Launch HN: Ditto (YC W20) – Keep product text in sync from design to production
#28Advanced security is only included in the $30 plan. Do I have to worry about the safety of my data if I pick a cheaper plan?
Sorry that's unclear - we have security measures in place for our app as a whole, regardless of the plan. "Advanced security" refers to the fact that we'll work with enterprise teams to implement custom security measures they might request. For all plans, we have: encryption at rest, encryption in transit, data stored in SOC 1, SOC 2, and ISO 27001-certified data centers, single sign on and mandatory 2FA for employee…
Re: Launch HN: Ditto (YC W20) – Keep product text in sync from design to production
#29However, as a person who used things like poeditor in different small places, there was always a concern about monthly payment for something used quite rarely. In this case, they'd pay for 1-2 months of intense use and then cancel the subscriptions.
In those small companies, I think they would gladly pay a one-time up-front fee, or perhaps a one-time small fee scaled with the amount of text in question... but subscribing for a fixed sum a month for something they don't intend to heavily use yet, probably not.