Why we built SouthpawStrings

SouthpawStrings brings guitar reference tools and practice material into one place, with left-handed players included from the start. A player should see a fretboard the way round they play it and find the shape they need. Then they should get back to the music without setting everything up again.

The site does two related jobs. The theory tools help someone explore scales, chords, intervals, and how they fit together. The practice player keeps a song's video, sheet music, and playback controls in one place. The Desk is a workspace where these tools open as windows side by side.

Why the tools share a desk

A scale diagram, a chord chart, and the player are often useful at the same time. On separate pages, a player keeps jumping between them and choosing the same settings again. The Desk gives them windows they can move, and music settings, such as the key, that every tool shares. Signed-in users can save a desk and come back to the same arrangement later.

Left-handed support is built into how the tools draw and respond, not added afterwards. The music itself does not change. The picture has to match the instrument in the player's hands.

Why you can start without an account

A visitor can try the theory tools and keep a practice library in their own browser. An account adds saving across devices and the full set of practice features. Data kept in the browser and data kept in an account are stored differently, and are recovered differently if something goes wrong. The site needs to explain this before someone relies on either.

Practice content is personal. The account library encrypts sensitive practice details and uploaded media when they are stored. The privacy policy limits how that data is used. These protections do not make every profile field private, and they do not remove the need for secure sign-in and backups. The trust policy explains what is and is not covered.

Support is optional. Donations do not unlock any features. Earlier designs for paid tiers are still in the project history, but they are not how the site works today.

How the work developed

The project history shows a move from separate tools and practice screens to one shared Desk. Earlier practice-library work had already decided how videos and sheet music would move across. Later changes fixed real problems people hit: windows that covered content, settings lost while an account loaded, and controls that behaved differently on phones.

The shared window behaviour later became Desk Engine, a separate code library. SouthpawStrings still owns the music tools, accounts, and visual design. Keeping that line clear means a fix to window behaviour can help more than one application.

Every change passes automated tests, then a development copy of the site, then a separate step to release it to the live site. Database changes follow their own procedure, with safety checks built in. Release notes record what changed. They do not replace an introduction or up-to-date instructions.

Scope and limits

Data kept in the browser and data kept in an account are recovered differently. Donations are optional and do not unlock features. Internal operating instructions and release details are not public.

Continue reading

Read the case study for how the site is built, secured, and run, or open SouthpawStrings itself.