Aviquill didn't start as a business idea. It started as a frustration.
For most of my life, my notes lived everywhere. Sticky Notes. Notepad. Evernote. Random text files scattered across folders I forgot existed. Whenever I had an idea, I wanted to get it out of my head as quickly as possible. I wasn't thinking about knowledge management systems or productivity frameworks. I just wanted somewhere to put the thought before it disappeared.
The problem wasn't capturing ideas. The problem was finding them again.
Months later I'd remember writing something important, but not where. Was it in Evernote? A text file? A note on my desktop? An unfinished document buried inside a project folder?
Over time I realized I wasn't struggling with writing notes. I was struggling with navigating them.
The unexpected inspiration
The funny thing is that the biggest influence on Aviquill wasn't another note-taking app.
It was Unreal Engine.
As a game developer, I spent countless hours inside Unreal's graph editors. Blueprints could become massive, but the engine gave you tools to navigate complexity. You could bookmark important areas. Collapse sections into reusable groups. Jump between parts of a graph without losing your place.
Nobody called it note-taking software, but the experience stuck with me.
Unreal wasn't helping me organize notes. It was helping me navigate complexity.
That idea stayed in the back of my mind for years.
Why canvases never clicked for me
Eventually I started experimenting with infinite canvases.
I loved the freedom at first. Being able to place ideas anywhere felt natural. But after a while I ran into a different problem.
My canvas became enormous.
Important notes disappeared into the distance. Interesting ideas became difficult to relocate. The more information I added, the harder it became to navigate.
I didn't need a bigger canvas.
I needed better ways to move through it.
The question that created Aviquill
What if a note-taking app borrowed more ideas from development tools?
What if navigation was treated as a first-class feature instead of an afterthought?
What if finding information felt less like searching through files and more like moving through a living workspace?
That question eventually led to features like bookmarked locations, floating editors, constellation search, and spatial organization systems that continue to evolve today.
Aviquill wasn't designed around folders.
It wasn't designed around documents.
It was designed around movement.
Why I'm sharing this
This section of the website exists because I think software becomes more interesting when the reasoning behind it is visible.
Every feature in Aviquill exists because it solves a problem I personally ran into while trying to think, create, and organize ideas. Some experiments worked. Some failed completely. Some features took months of iteration before they felt right.
Here I'll share those stories.
The decisions behind features. The mistakes. The prototypes. The lessons learned along the way.
If you're curious about why Aviquill works the way it does, you're in the right place.