Hi HN,<p>I've been programming for about three years, and this is my first full-stack web app. It's a tool for organizing musical ideas. Building and deploying it has been a great learning experience, and in that spirit I'd be grateful for any thoughts or suggestions if you care to take a look. Thank you!<p>source: <a href="https://bit.ly/3giqrBU" rel="nofollow">https://bit.ly/3giqrBU</a><p>Why:<p>Composing music is different for everyone, yet some practices are employed by many musicians. One such practice is to record a musical idea on a phone, capturing the idea at its freshest, and for many, clearest. This often leads to a lengthy catalogue of chronologically organized recordings that can be difficult to parse when sitting down to flesh out a piece of music – what matters most is the content of the idea, more so than when it was conceived. The purpose of SoundSeeker is to allow you to organize musical ideas based on their content instead of when they came to be, and to serve as an educational personal project in my growth as a software engineer.<p>What:<p>A graph-based organizational tool for scratch audio recordings<p>Planned features:<p>in-app audio recording, in-app audio trimming, custom labeling outside of the main tiered organizational system.
Looks like a good start - and lots of polish, refinement still possible.<p>Have you been regularly getting feedback from new people you've introduced to it to make little adjustments to the text/copy, and other elements?<p>P.S. I think it'd be a good idea to put your "Why" paragraph from this post right under your "Organize Your Musical Ideas" header; you could put the text in a left or right column, and then put a smaller demo video (that people will likely maximize on their own) in the opposite corner - so both the text and video demo are in the "Hero" / top part of the page where scrolling isn't necessary to see either.