One year ago, on August 5, 2025, Writon was born. But the story of Writon did not actually begin on that day. Like most things worth building, it came from a series of ideas, experiments, failures, and problems that eventually led to something I decided was worth committing to.

This is the story of how that happened — from the earliest idea, through Twitter and ChromaKey, to Writon itself, university, going live, graduation, and the very different reality of trying to keep a project alive afterwards.

Before Writon

I had always had ideas for things I wanted to build. The difficult part was not coming up with ideas; it was deciding which one to actually turn into something real.

The idea that eventually became Writon started taking shape at a particularly ordinary moment. After returning home from a dental procedure, I was lying on my bed and could not really do much. I had my PC, plenty of ideas, and time to think.

I started asking myself a simple question: what can I actually build with the computer in front of me?

I had thought about many projects before, but this time I decided that instead of leaving another idea in my head, I would choose one and try to build it.

Twitter → ChromaKey → Writon

Before Writon became a text processor, there was another direction. I had been thinking about using AI to help build my online presence, particularly on Twitter. The idea was to create an AI content partner that could help generate and organize content around artificial intelligence, technology, startups, and internet trends.

The concept was ambitious. I imagined producing large amounts of content every day, following strategic posting schedules, and using AI as an idea engine and content strategist.

But while thinking about AI writing content for me, my attention shifted toward a more fundamental problem: what if AI could help people improve the writing they were already doing?

That led to ChromaKey.

The ChromaKey Idea

ChromaKey was an AI-powered Android keyboard concept designed to rewrite text while preserving the user's personality and tone. Instead of forcing everyone to write in the same polished, artificial style, the idea was to make AI adapt to the way a person naturally communicates.

I imagined different writing modes for different situations:

The philosophy behind it was simple: "It feels like an iPhone, looks like GitHub, writes like you — just better."

ChromaKey never became the final product, but it was an important step. It forced me to think beyond AI as something that simply generates text and toward AI as something that can work with the way people already communicate.

August 5, 2025: Writon Is Born

Eventually, the ideas became more focused. Instead of building a keyboard or an AI social-media assistant, I wanted to create a standalone tool that could help people improve their writing.

I wanted something I could use myself, particularly for academic work and everyday writing. The vision was straightforward: build a free and accessible writing tool that helps people improve their text without taking away their own voice.

That was the point where Writon became a real project.

August 5, 2025 marks the beginning of Writon as the project it would eventually become. But deciding to build it and successfully bringing it online were two very different things.

The First Attempt Failed

My first attempt at bringing Writon online did not go as planned. I eventually gave up on that version.

That could have been the end of it.

Instead, returning to university gave me another opportunity to revisit the idea. I had more stability, access to the resources I needed, and a reason to keep learning. I returned to the project, rebuilt parts of it, experimented with the architecture, and continued developing the underlying system.

Writon became less of an idea and more of an engineering project.

University Changed the Project

While I was at university, Writon developed alongside everything else I was learning. The project gave me a practical environment in which to apply what I was learning about software development, APIs, artificial intelligence, interfaces, security, and deployment.

One of the biggest pieces of that work was writon-core, the core engine behind the project. I continued improving the underlying architecture while also refining the user interface and overall user experience.

The original ideas from ChromaKey were still present, but Writon was becoming something much more focused: a platform-agnostic text processing tool rather than a keyboard.

Eventually, after rebuilding and refining the project, I successfully brought Writon online.

What Writon Became

Writon evolved into an AI-powered text processor built around the idea that improving writing should not have to mean surrendering control of the writing itself.

The project grew to support multiple AI providers and different text-processing capabilities while maintaining the broader philosophy that had been present since ChromaKey: make the technology useful, accessible, and flexible.

More importantly, Writon became something I could point to and say: I built this.

The Part Nobody Sees: After University

Building something while you are in university is one thing. Maintaining it after university is another.

While I was studying, I had a level of stability that made it easier to dedicate time and resources to Writon. After graduating, that environment changed.

Suddenly there were other realities to deal with: looking for employment, limited resources, and even a broken PC. Time and resources that once went into development became harder to find.

This is the part of building a project that is rarely visible from the outside. When people see a project online, they see the website, the code, the features, and the finished product. They do not always see the circumstances surrounding the person maintaining it.

Writon was no longer being built in the same environment that had allowed it to grow.

When Development Slowed Down

The last significant work I did on Writon was around November or December 2025. At that stage, much of the work was focused on maintenance: updating dependencies, fixing things when necessary, and keeping the project stable.

Since then, development has slowed considerably.

But slowing down is not the same thing as giving up.

Writon has remained one of the best things I have ever built. Even during periods where I was not actively writing code, the project never really left my mind.

A Year Later

August 5, 2026 marks one year since Writon officially began.

Looking back, the most interesting part is not simply that the project exists. It is everything that had to happen for it to exist: the ideas that came before it, the Twitter experiment, ChromaKey, the decision to finally commit to one idea, the first failed attempt, returning to it during university, rebuilding the project, developing writon-core, improving the interface, and eventually putting Writon online.

Then came graduation, a change in circumstances, fewer resources, and a period where the project had to survive without the same level of attention.

That is also part of the story.

What Building Writon Taught Me

Writon taught me that building software is about much more than writing code.

It taught me about leadership because at some point there is nobody else responsible for deciding what happens next. It taught me patience because good ideas rarely become good products immediately. It taught me to learn continuously because every new problem eventually forces you to understand something you did not know before.

Most importantly, it taught me how to adapt.

The project I initially imagined was not the project I eventually built. Twitter led to ChromaKey. ChromaKey helped shape Writon. Writon changed again as I learned more, encountered new problems, and understood what I actually wanted the product to be.

That evolution was not failure. It was the process.

Today

Today, Writon remains live at writon-api.onrender.com .

Development is not where I want it to be yet, but I am not finished with the project.

This past year has been challenging, and there were moments when I seriously considered walking away from Writon. But the more I look back at everything that went into creating it, the harder it is to see it as something I should simply abandon.

I want to return to Writon, continue improving it, and keep it alive. There is still a lot I want to build, learn, and change.

One year after its birth, Writon is not a finished story.

It is a project that survived its first year — and the journey continues.

You can explore the live project at writon-api.onrender.com or explore the source code on GitHub .

The lesson I carry forward is simple: you do not always get to choose the circumstances in which you build, but you can choose whether the idea is worth returning to.