|
|
|
|
|
|
by eggbrain
1867 days ago
|
|
|
First off, congrats on launching, the product looks super smooth! Had a few thoughts off the cuff: 1. From a product perspective, do you worry about relying heavily on Figma? If marketing and design teams move towards different design tools like Invision, or if Figma changes / restricts API access, or decides to move into this same area, I could imagine it could cause issues down the line. 2. From the sales side of things, how do you tackle getting buy-in with three fairly different stakeholders (design / marketing / engineering)? I could imagine the marketing team buying in, but not getting engineering to fully buy-in, causing "success" to rely on inter-office communication, rather than the product itself. 3. On the developer side, how does Ditto handle interactions with other third party libraries or existing code that may also modify text, e.g. using Optimizely to A/B test wording on the page? Congratulations once again, and look forward to your future success! |
|
|
1. We integrated with Figma first on the design side due to a couple of reasons: we were really excited about the growth on the platform, the community, and their ability to serve as a single source of truth for design (with live editing). As an early developer on both their Plugins platform and REST API, we've definitely seen their APIs evolve.
Ideally, we want to be design-tool agnostic (including integrating with Sketch, AdobeXD, InVision, etc.) and integrate with everywhere copy lives (including docs, sheets, etc.) once we have enough engineering bandwidth. We think serving as that text layer / infrastructure for text is a fairly different value prop from design tooling, but we do hope to decrease our reliance on Figma over time.
2. Copy is definitely unique in that it's touched by so many roles horizontally in an org (not only in EPD but also marketing/legal/etc.), unlike a lot of role-based tooling (devtools, design tools, etc). We've been really lucky so far in seeing a lot of our growth happen organically by those at larger companies with roles owning the copy (UX writers, content designers, copywriters, etc.) championing our tool to other stakeholders. However, this is definitely something we're still trying to figure out how to do effectively, and we've seen some cases where adoption is held-up because of cross-team communication.
3. At the moment, Ditto brings text into development as structured JSONs, which we keep fairly open-ended on how teams want to integrate into their UIs and 3rd party tools. They can also manipulate the text in development and/or bring it into A/B testing frameworks. In the future, we hope to handle some of those use cases ourselves :)