|
|
|
|
|
by cassiepaper
150 days ago
|
|
Great niche! Few questions:
- Were you soloing the entire thing? What about ops/research/market analysis? What about the design? - Did you think about it as product-first or technology-first? Other words, did you build a solution for scoped audio mgmt, or a music player for kids? - What's your tests status? Full coverage? CI/CD? - How did you approach the entire legal aspect? Single lawyer? Self? Not at all? |
|
Solo? Yes, everything. Design, code, marketing, support. No team, no outsourcing. Last few months Claude Code has been a huge help for brainstorming, copywriting, and rubber-ducking code problems.
Product or tech first? Product first, 100%. Started with the problem: my kid needs access to more music, but I don't want to hand over Apple Music. Tech decisions followed from there. SwiftUI because I wanted native performance, Realm for offline, etc.
Tests/CI/CD? Honestly, test coverage is thin. I have unit tests for critical parts (subscription logic, playback state) but not full coverage. No CI/CD - just manual builds and upload to TestFlight. Good enough for a solo project.
Legal? Self, mostly. Apple's standard EULA covers the basics. The app doesn't collect anything.