# ux writing Published articles for ux writing. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Why I joined the Daily UI challenge after 5 years in UX, and what it taught me DevFeed: [Why I joined the Daily UI challenge after 5 years in UX, and what it taught me]() Original publisher: [Read original article]() Author: Neil Nkoyock Published: 2026-07-21T03:10:03Z Content type: opinion Language: en Sources: [LogRocket Blog]() Topics: [Artificial Intelligence]() Tags: [ai](), [career-development](), [creativity](), [design](), [illustration](), [typography](), [ui](), [uncategorized](), [ux](), [ux-design](), [ux-writing]() ### AI overview A UX designer revisits the 100-day Daily UI challenge to reconnect with hands-on design and compare manual work with AI-assisted concept generation. The experience explores whether shared AI tools flatten creativity, while observing that submissions responding to the same prompts can still differ substantially in typography, layout, color, illustration, and visual personality. ### Source excerpt After five years in UX, I revisited the Daily UI challenge to reconnect with hands-on design. Along the way, I learned that great interfaces come from thoughtful briefs, sound judgment, and user feedback, not just better AI tools. The post Why I joined the Daily UI challenge after 5 years in UX, and what it taught me appeared first on LogRocket Blog. ## Got skills? Make the Figma agent a better collaborator DevFeed: [Got skills? Make the Figma agent a better collaborator]() Original publisher: [Read original article]() Author: Sachi Shah; Sean Lee Published: 2026-07-01T13:45:00Z Content type: article Language: en Sources: [Figma Blog]() Topics: [Figma](), [Prompt Engineering](), [User experience (UX)](), [Accessibility](), [User interface design]() Tags: [accessibility](), [agent](), [design](), [design-systems](), [figma](), [skills](), [standards](), [ux](), [ux-writing](), [workflow]() ### AI overview The article explains how reusable skills make the Figma agent a better collaborator. Teams can teach the agent their workflows, design feedback practices, UX writing standards, accessibility checks, brand voice, compliance guidance, and review processes through plain-English instructions and examples. ### Source excerpt From sharing your best thinking to learning from your team's go-to prompts, here's what skills unlock in the Figma agent. ## The art of the professional pivot DevFeed: [The art of the professional pivot]() Original publisher: [Read original article]() Author: Aaron Britt Published: 2023-12-07T00:00:00Z Content type: article Language: en Sources: [Figma Blog]() Topics: [User experience (UX)](), [SockTz]() Tags: [career](), [design](), [pinterest](), [product-design](), [ux-writing](), [writing]() ### AI overview Six creatives describe career pivots within and beyond product development. The article presents strategies such as reframing a role or making a larger change, with Ry Reid's move from customer support to UX writing and later toward visualizing ideas as a central example. ### Source excerpt Six creatives working in the product design world share their journey to making big leaps and side shuffles into their next career chapter. ## How OkCredit uses Philology to experiment with Android strings without releasing a new app version DevFeed: [How OkCredit uses Philology to experiment with Android strings without releasing a new app version]() Original publisher: [Read original article]() Author: Rashanjyot Singh Published: 2022-07-13T06:31:23Z Content type: tutorial Language: en Sources: [OkCredit - Medium]() Topics: [Android](), [User experience (UX)](), [Library](), [Open Source](), [Localization (l10n)]() Tags: [android](), [android-app-development](), [android-library](), [engineering](), [experimentation](), [language](), [mobile-app-development](), [open-source](), [ux](), [ux-writing]() ### AI overview This tutorial explains how OkCredit experimented with Android string resources and translations without releasing a new app version, using the open-source Philology library. The article describes the need for faster string experimentation across a multilingual user base and the use of a pilot to assess the approach. ### Source excerpt How OkCredit Android App improves UX writing by changing strings on the fly (and you can too!)Foreword⚠ First things first! We don't want to make any false claims, and to tell you straight off, you cannot update the strings stored as XML resources in your android app. However, we are here to tell you how we achieved that effect in OkCredit android app by using 'Philology', an open-source android library. OkCredit is a digital ledger app used by millions of small business owners and their customers daily to facilitate the recording of credit/payment transactions digitally all over India. The app supports over 11 different languages and to cater to such a diverse userbase, one key aspect is to communicate effectively. A pain point often shared by our product managers and language localization teams was that each time we wanted to experiment with strings, change/update them or make changes to translations of specific languages, we had to release a new version of the app. Hence, we wanted to have a setup that would enable us to experiment with strings faster and update them on the fly without releasing a new version of the app. Let's Get Started Like most apps, OkCredit app uses a lot of XML string resources, and an ideal implementation to set up string experimentation would be one that requires the bare minimum amount of changes in the way we conventionally fetch strings, which is using getString(...) method of the Resources class. The android developer community is amazing and that's what we realized yet again when we instantly found exactly what we needed. We figured out quite a few technical blogs and a couple of open-source libraries that explained the underlying mechanism well (hence, we won't do that much herein and simply share the relevant links). However, to build conviction that it could run flawlessly at scale, we needed to pilot the solution first-hand. After using it for numerous experiments to improve the experience for millions of our users, with this b