5 times Dittowords helped me as a UX writer (with gifs!)
Dittowords was one of the first tools I tested as a UX Writer, and I must admit that two years ago, it didn’t work so well (bugs, confusing experience…). I saw the application improving, and it became more valuable daily. Some might say I should have quit using Ditto by that time, but now I see how it helped as I learned how to be a UX writer.
I’m talking about my experience here; if you need to know the step-by-step, look at these:
- Ditto Basics Playground: Takes you through the basics of Ditto, including starting new projects, using our plugin, making edits, etc.
- Ditto Components Playground: Goes over how Ditto components work, from creating to editing to attaching.
Before any job title, I’m a writer. And it shapes how I see the world and solve problems. Just to start things properly.
5 times Dittowords helped me as a UX writer
1 — Editing multiple copies at the same time
Editing microcopy was my first task when I still was a Product Analyst (but already doing some UX writing). By then, I reviewed Figma and checked if each word fitted the purpose, following what was in an approved glossary I had built before.
Although I was happy doing my UX writing, losing microcopies was frustrating. It mainly happened because I wasn’t fluent in Figma and didn’t understand how the versions worked.
So, I learned how to use Ditto to write & sync microcopies. This also helped ensure I used the same title on every screen (which led me to think about consistency).
2 — The why
As a UX writer, you never change a copy just because — I knew it, but seeing the “notes” field available to type why I changed something helped me think and ask myself before just changing something.
Copies are strings, and although the code’s simplicity is not your duty, it’s good to have this in mind. In addition, being near developers and QAs help the team build better products (and code).
3 — Localisation
I worked on a translation/localisation project where we had to translate a payment app from Portuguese to English. We had less than a month to work, so we hired a company to translate, and I was responsible for adjusting the tone and organising the copies.
A Google spreadsheet was the primary tool, and I transferred this content to Ditto in small bunches as a part of each new delivery because I couldn’t just stop for a week or two and only do this. It was like an “internal project”, and with every new task, I would improve it.
Feels magical, I know.
4— Organising projects and frames
Instead of content design systems and visual design systems existing in isolation, the ideal is one design system that accommodates everything, marrying the content and design together in the way it will actually be used and experienced. (Rachel McConnell)
If it’s not your reality (I believe it’s not in most companies), assure you understand how your design team organises Figma files— it will save you a lot of time. Ask a colleague to show you the files, design system, and architecture. You don’t need to reproduce it; see it as a resource for your files. I didn’t do this for the first time, and I regret it.
That’s how organising Ditto projects accordingly to Figma files helped me understand product design structures.
5 — Organising component
Figuring out how to organise components in Ditto made me think about the product’s information architecture and learn its importance and how it would impact the design.
It also avoids using your phone to check the App you work on (or in Figma files) to review a copy, for example. Instead, you can search the component names or copy and find everything organised and tagged.
These prints belong to the Cosmo app, a flower oracle & identifier you can test by clicking here (it’s a prototype and works better on your phone).
I hope this article inspires you somehow. Feel free to share and ask me questions.
Thanks for reading and clapping. 👏
