I run and edit Klivvr's blog, the place where our product, design, and content teams write about how a fintech app for over a million users actually gets built. I commission and edit every piece that goes up, and write some of them myself. Below are three I'm proud of. Click through to read them in full on Klivvr's blog.
The story behind K.ai, Klivvr's in-app AI assistant and the first natively embedded AI in a fintech product in the region. The piece walks through why it only answers from a user's real account data instead of guessing, and why trust mattered more than cleverness in how it was designed.
Read on Klivvr's blog →Want the full build story, with production data? See the K.ai case study →
How Klivvr's writers ship copy fixes over-the-air using Phrase, instead of waiting on a full app release. It includes the small rewrite (from a flat "Something went wrong" to a specific, useful message) that shows why the workflow matters.
Read on Klivvr's blog →A behind-the-scenes look at Klivvr's redesign: a new "Klivvr Design" design system, dark mode, and a unified tone of voice built around active, second-person language across both English and Arabic.
Read on Klivvr's blog →The blog is where the Language & Communication Guidelines get stress-tested outside of the app. Same tone pillars, same active-voice standard, same allergy to jargon, applied to longer-form writing about our own work. See how that guideline came together in the tone-of-voice case study →, or how it shows up on-screen in the product writing case study →.