Digr: Building a product and its organic growth foundation from zero
An independently developed local-first music player for people who still own their music — and an exercise in building product, positioning, brand and distribution as one connected system.
The opportunity
Digr is an independently developed desktop music player for people who still own their music. Modern music software increasingly assumes that music lives inside a streaming service, but many listeners still maintain collections made up of ripped CDs, downloads, lossless files and music accumulated over decades.
Those collections carry more than metadata. They hold taste, memory and years of careful organisation. The software around them often sits at one of two extremes: highly technical tools built for audiophile workflows, or capable desktop library software designed around older interaction patterns. Digr began by exploring the space between them.
Defining the product
The product strategy is built around ownership, local-first architecture, no mandatory account, expressive interaction and large libraries as a first-class use case. The library should work from the user’s own files and folders without first being uploaded to a proprietary cloud. Useful interoperability, including Google Cast, keeps local music from feeling trapped on one machine.
The result is a local-first music player for Mac designed to feel modern without sterilising the experience or turning it into another generic SaaS interface.
Building the brand
The product evolved through earlier naming and concept exploration before Digr became the final name. The identity draws from early-2000s desktop music culture, Y2K interfaces, physical audio hardware, record collecting and music discovery.
The aim was not literal nostalgia. It was to take the personality of Winamp-era software without reproducing its limitations. Tactile controls, expressive skins, display references, a dark interface and an Acid Lime accent give the system character while keeping it credible in a contemporary software environment.
Product and engineering
Digr is being developed with Tauri 2, React, TypeScript, a Rust/Tauri backend and SQLite/local library architecture. Product areas include library scanning, folder watching, playback, queues, EQ, skins and casting.
The important point is that the positioning influences the architecture. If local-first is part of the promise, the application has to work locally rather than simply marketing a cloud product as privacy-friendly. The feature roadmap follows the same constraint.
Designing search into launch
SEO was considered before public launch. The strategy builds topical relevance around the problems Digr is intended to solve: local music players, Mac music players, large music libraries, FLAC and ALAC playback, library organisation, ripping and owning music, local versus cloud libraries, casting and privacy-conscious software.
The content architecture covers category education, problem-led help, comparison research and product-adjacent education. Articles need to be useful in their own right rather than becoming a series of product advertisements.
The product-truth rule
Content cannot imply that Digr supports something it does not currently support. Sometimes the honest answer is to explain a capability that is planned, constrained or not implemented yet. This keeps editorial governance, product development and brand trust aligned.
Technical SEO foundation
The marketing site is built in Astro with static HTML and minimal hydration, hosted on Vercel. The foundation includes unique canonical URLs, titles and descriptions, Open Graph metadata, an XML sitemap, a separate image sitemap, RSS, structured data, accessible heading hierarchy and internal-link validation.
Preview environments are deliberately noindex and nofollow. Structured data is kept truthful too: the site does not fabricate SoftwareApplication.offers while the product is not purchasable.
Building conversion before launch
The marketing site bridges the gap between interest and availability with a branded on-site waitlist form, a Brevo-backed list, clear success and error states, analytics for signup completion, privacy copy and a support contact. SEO traffic before launch should create a useful way to learn.
What exists today
At the time of writing, Digr’s marketing site is live, the desktop application is under active development, the waitlist is open and the initial organic content architecture is in place. Search Console is now collecting the first discovery and indexing data.
No acquisition results are being claimed yet. This case study captures the starting line and will be updated as meaningful product and search data becomes available.
What I’ll measure next
The next questions are which search clusters earn impressions first, how comparison content performs against informational content, what converts organic interest into waitlist signups, which product problems drive the strongest demand, and whether search behaviour can help prioritise future product development.
Digr is an experiment in treating product, positioning, brand, content and distribution as one system from the beginning. The interesting result at this stage is not traffic or rankings. It is that the infrastructure for learning is already present before launch.