Methodology, UX, and full-stack delivery focused on one outcome: making the next action clear.

I have tried what feels like every productivity system under the sun. The strange thing about most of them is how much work they hand back to the person using them. They provide databases, tags, views, automations, and an empty canvas, then leave you to watch tutorials and invent the system that is supposed to make you more productive.

Paper planners and notecards came closer because they forced useful constraints. There was only so much room, the next step had to be concrete, and the method was visible every time I used it. I even designed my own cards. What those tools lacked was the part software handles well: remembering, sorting, connecting, searching, and resurfacing something before it disappears.

Radarist combines those strengths around one opinionated idea. Every active project is paired with its single next actionable task. The main Radar provides a bird’s-eye view of everything moving forward without placing every possible task in front of you at once. You can only do one thing at a time, so the interface is honest about that.

The supporting system is designed around the moments where personal projects usually break down. An Inbox captures a thought before it vanishes. Spaces separate the different areas of life and work. Focus controls narrow the day, templates make recurring work reusable, and the Awaiting Next Action area refuses to let a stalled project quietly fall through the cracks. Automation supports the method instead of becoming the method.

The first version proved the product but eventually made its own case for modernization. Radarist began as a heavily customized WordPress application built on custom post types and post meta. The current rebuild replaces that foundation with Next.js, React, TypeScript, Postgres, Drizzle, typed validation, and passwordless authentication, while preserving the existing data, visual character, and mental model people already understand.

That makes Radarist more than a redesign exercise. It brings product strategy, brand, interaction design, frontend engineering, data modeling, authentication, content migration, and operational judgment into one coherent piece of work. The difficult part was not merely replacing old technology. It was knowing which constraints made the product valuable, then rebuilding the system without losing them.