Now that Omvona has a name and somewhere to document the work, it's time to get into the actual development.
The past few days have largely been about getting things organised, establishing the development environment and putting the initial structure of the application together.
I've also started working through some of the basic functionality that everything else will eventually depend on. There's nothing particularly exciting to demonstrate publicly just yet, but it's good to have something taking shape beyond the original idea.
Turning an idea into something workable
I've spent a fair amount of time recently thinking through what Omvona should eventually be capable of and how the different parts of the application might work together.
The scope is ambitious, and it's surprisingly easy to find myself thinking years ahead when I've barely finished the first few steps.
I've made that mistake before. It's easy to mistake having a detailed plan for making actual progress.
This time I want to focus on getting something useful working, testing it properly and allowing what I learn to influence what gets built next.
That doesn't mean ignoring the bigger picture. I still want to make sure the application has the right foundations to grow, without eventually becoming another collection of disconnected features.
But there's only so much value in planning before you have something real in front of you.
A home for the project
Another significant step has been settling on the name Omvona, registering the domain and building the first version of the website and blog.
It's still early, but I wanted somewhere to document the development from the beginning rather than trying to reconstruct the story months or years down the line.
The intention is to keep these updates fairly straightforward, covering what I've worked on, decisions I've made and anything interesting I've learned along the way.
What comes next
My immediate focus is continuing work on the core application and figuring out the most sensible place to begin turning the wider vision into something people could actually use.
That starting point isn't completely settled yet, and I'd rather give it proper consideration than rush into building features simply because they're on a list.
There's an enormous amount still to do, but the groundwork is in place and I've got something tangible to build on.
A reasonable start, I think.