Blog in English

I shared my app TimeMate with a screen demo, but everyone kept asking about the wallpaper 😅 so here it is!

Horizontal Screen

4K (3840x2160)

2K (2560x1440)

Full HD (1920x1080)

Vertical Screen

4K (2160x3840)

Full HD (1080x1920)

Preview

Besides releasing the app on the App Store, submitting it to Homebrew’s main branch was a completely new experience for me. Thanks to a user’s suggestion, I learned that getting listed in Homebrew’s official installation database actually requires meeting a certain set of standards. I’ve been using Homebrew for years, yet somehow never paid attention to how it really works.

A quick side story: when I shared the app in a group the other day, someone left a comment like, “always tinkering with some tiny tool.” I honestly didn’t know how to respond. But the surprising part came from a different place — this tiny little app actually received a donation. The amount wasn’t big, but the fact that someone voluntarily contributed without asking for anything made me feel like this app is useful not just for me, but for others as well.

It’s true that I “tinker” a lot — the kind of stuff many people wouldn’t bother doing. But everything I build comes from a real need of my own, and I use these apps every day. Nowadays, if a product isn’t labeled with “AI” or “Blockchain,” it’s considered “out of meta.” But I think even in a world where humans can build rockets for space tourism, there are still people making needles and pencils. For me, as long as something I build shows up at the right moment and solves someone’s problem, that’s already more than good enough.

I’m not sure if anyone else feels the same, but whenever I work on a product, I’m always excited about building the “core” features. The moment I have to deal with non-functional stuff like onboarding, landing pages, or user guides… my energy drops instantly 😅

I’m not great at UX writing, and I’m not the type to confidently “sell” things with fancy words either. But if I write too technically, it becomes dry and boring. So I always end up stuck somewhere between those two extremes: clear – concise – engaging – but still accurate.

Sometimes I scroll through other solo indie projects and see how meticulous some folks are with their onboarding flows and landing copy. Every line is polished, every message feels intentional. And honestly, I truly admire that.

Meanwhile, I’m usually the kind of person who just wants to jump straight into coding. But when it comes to explaining features or writing a simple intro, I can spend ages trying to craft just a few sentences.

Maybe it’s a common weakness among developers: we’re great at solving problems, but not always the best at describing them in words. I’m trying to slow down and put a bit more care into the “non-code” parts. After all, users don’t read our code — they read our words.

In this post, I'll be sharing with you the Pomodoro Technique, a time management method that can help you stay focused and productive.