Why Fretscape exists.

I've been writing code since I was 10. I picked up guitar at 17. Neither one made me famous - but I never stopped coming back to both.

Guitar came first as a love, second as a skill. I was in a band for a few years, learned enough tabs to get by, never bothered with theory because I was too cool for that. I didn't really know what I was playing beyond the patterns my fingers had memorised.

Life happened. I hung up the guitar, started coding full time, built a career as a developer. Years passed. I came back to guitar briefly, but it didn't stick.

Then, in my early thirties, I picked it up again. Properly this time. Taught myself theory. And something clicked - it wasn't as hard as I'd always assumed. I fell in love with guitar all over again, except now I actually understood what I was playing.

I'd spent twenty-odd years writing code and twenty years playing guitar. Eventually, the two were going to collide.

My daughter Isla started learning when she was nine. She wanted to play - really wanted to - but she was on one of my old PRS guitars. Full size. Way too big for her hands.

She couldn't reach the stretches. She couldn't use her pinky yet. And every chord resource I found showed her the exact same shapes it would show me - a grown adult with full-size hands. There was nothing that said 'here are the chords you can actually play right now, with your hands, on your guitar.'

So I started building it.

I limited the fret span so she'd only see shapes her hands could reach. I excluded the pinky so she wouldn't get frustrated trying fingerings that were impossible for her. I set the difficulty to beginner so the library only showed shapes she could manage.

And it worked. She could play chords. Real ones - not dumbed-down versions, just the ones that fit her hands. She stopped getting frustrated and started making music.

That was the moment Fretscape stopped being a side project and started being something that mattered.

The more I built, the more I couldn't believe it didn't already exist.

I sat with my guitar for hours working out what makes one fingering harder than another. Stretch. Barre type. How many fingers. Whether the shape puts your hand in an awkward position. Obvious things - things every guitarist feels instinctively - but nobody had quantified them. Try turning something you 'just know' into logic a computer can understand. It's the kind of problem I live for.

Then I started looking at chord changes. Which fingers move, which ones stay put, how far they travel. The idea that the best voicing for a chord depends on what chord comes next - it seems so obvious when you say it out loud. But no chord tool thinks that way. They all treat every chord as if it exists in isolation.

I kept expecting to find a competitor that already did this. I looked at every chord app, every online tool, every guitar resource I could find. Nothing. Not one.

I don't know why. Complacency? Different priorities? It doesn't matter. What matters is that guitarists deserve better tools, and now they have one.

Honestly? It was writing the 'Guitar for Every Hand' page.

Here's the thing: I didn't build Fretscape for people with physical limitations. I built it for every guitarist - from the beginner who wants to stay in open position to the seasoned player experimenting with unique tunings. The filtering system exists because a powerful chord tool should let you narrow things down to what fits your hands, your level, your setup. That's just good design.

But sitting down and writing out the scenarios - a guitarist missing a finger, a guitarist with arthritis, a kid with small hands, someone recovering from an injury - I realised something that genuinely made me angry. These capabilities were already there. They fell out naturally from building the system properly. Which means every other chord tool could have done this too. And none of them bothered.

Guitar is magical. I want to share that with as many people as possible. The idea that someone might have given up because every tool showed them shapes they physically couldn't play - and that the fix was this straightforward - that gets to me.

Fretscape rebuilds the library around whoever is playing. That it helps people I never specifically set out to help is the thing I'm most proud of.

Fretscape is built by one person - me, Kyle - from Yorkshire, England.

No venture capital. No team of fifty. Just a guitarist who codes, a daughter who needed better chord shapes, and the kind of obsessive focus that doesn't let go of a problem until it's solved properly.

And Beckie - my wife - who has listened to me talk through problems she has no reason to care about, put up with me disappearing into this thing for a year, and never once told me to stop. Fretscape exists because she gave me the space to build it.

I build Fretscape the way I'd want someone to build a tool for me: thoughtfully, with care, and with the assumption that the person using it deserves more than a chord dictionary from 2005.

Made in Yorkshire, England. Just like the tea.