3
16 Comments

Looking for technical co-founder for music streaming startup

Hi everyone!

I've been dedicated to building a music community centered on transparency and fair compensation for artists.

We kicked off with an invite-only public beta, resulting in a 5-star rated iOS app and 7,000 organic users, including notable artists. After thorough testing, we've enhanced our mobile app design and introduced a subscription model. We are introducing a new streaming model that ensures payout increases by 1,500-16,000%, with payments made directly from listeners to creators, promoting transparency in supporting artists.

Our tech stack includes Rails, Vuetify, PostgreSQL, Nginx, and AWS. I lead the design efforts alongside our dedicated frontend team and iOS/Android developers. I contracted freelance Rails developers for the backend, but as we move forward it's important we collaborate closely with passionate developers aligned with our company's vision at an equity level.

We chose a web 2 framework for its user-friendly adoption, recognizing that the main hurdle often lies in executive board dynamics rather than the technology itself. However, as our platform evolves, we're open to integrating AI and blockchain-based technology when it aligns with our growth trajectory.

Currently, we're seeking an experienced Rails developer to address remaining issues before our summer launch and assist with scalability.

If interested, feel free to reach out!

  1. 1

    Experienced rails developer and ML engineer here. How can I contact you?

    1. 1

      I noticed the email address wasn't working: use this one [email protected]

    2. 1

      This comment was deleted 24 days ago.

  2. 1

    Interested, where should I reach out to you?

    1. 1

      I noticed the email address wasn't working: use this one [email protected]

    2. 1

      This comment was deleted 24 days ago.

  3. 1

    Rails is a terrible idea in the long run (your entire tech stack is), but you can save some time with the mobile app dev, move to Flutter

    1. 1

      Can you explain in detail why our stack is terrible?

      So far it's been stable, and we've integrated about 100 APIs. Our focus has been on launching and validating our product in the market. Through this process, I've learned that technology isn't the primary concern; it's about aligning with market needs. Once we establish a successful formula, even with less optimal components, refining becomes easier.

      We actually met with the former head of a large media outlet, and he is interested in joining our team to lead our marketing efforts, indicating the potential impact of our project.

      Our goal remains addressing fundamental challenges faced by artists, such as a fragmented creator landscape and the minimal $0.003 payouts per stream.

      1. 1

        Keep in mind, somebody liking your software idea does not make your tech stack any better or the other way around.
        As anything "terrible" is relative, it is only true if your aim is to build a stable, scalable and supportable system.
        "integrated about 100 APIs" you are already in a bigger mess than you think
        if you building a project for fun practically any language will do, if you building it alone best language will be the one you know best.
        When you build proper business software factors like number of dependencies, long-term support, scalability, talent pool, available resources ($), the CTO expertise & experience, hosting costs and another 30-40 things like the above are factors you need to take in account when you selecting a tech stack.
        AWS - stupid expensive on a monthly basis, only very specific use cases is usable
        AWS - you stuck with it as a major dependency = stupid expensive in the long run
        RUBY - fun language to play with, not something you build complex systems with, the model–view–controller may sound good but that is no way to build API, and the talent (if you can call it that) is very limited
        PostgreSQL - good database, very limited programmability options and API must bear all the system logic = very inflexible (better than MongoDB)
        Vuetify - just why? Typescript is invented already and none of the old frontend frameworks pretend that never happened and consider 200k dependencies a "community support" (but at least you may find a Vue dev to use it).
        Nginx - that actually is an indispensable tool if you were stupid enough to use Docker or any other type of containers.

        1. 2

          Everything you've stated here is purely opinion based and, in my opinion, your opinion is ridiculous.

          Ruby not something you build complex systems on? I think you'd be surprised at what runs predominantly on Ruby (GitLab is the first example that comes to mind).

          Vuetify is a simple front end framework that already comes with components built in that make it faster to develop and I believe it also has Typescript support.

          Stupid enough to use Docker? Have you actually developed for the web recently?

          Honestly, you're the type of person I would hate to work with. Full of opinions but says nothing.

          1. 1

            everything is an opinion in the end, I have wasted way too much time attempting to help people avoid mistakes, and making some mistakes is the only way to learn despite how stupid they are (I have done my fair share of those)
            But assuming you remember my advice soon or later you will know if I was right or not, the only question is what will be the cost of that lesson.

            1. 3

              @scottywalker92 is correct. @petrovn your tone is dismissive. GitHub, Airbnb, Shopify, Instacart, Hulu, Groupon, Soundcloud, Kickstarter, Fiverr, Gumroad, Etsy, Twitch, Goodreads, and Dribbble all use Rails. All successful companies at scale.

              I also checked some of your sites, they move slow, you're using some type of parallax effect when things scroll, and it's clunky. Your UI/UX is extremely dated as well. I think you're more concerned about sounding like an authority, and your blanket advice is empty especially when it comes without assessing the execution of said stack. Execution is everything.

              1. 0

                considering the sites are more than 10 years old I think they are good, I make custom software solutions, websites are more of a "something to put on the main domain so it is not empty" kind of a deal not a showcase of my work so I attract customers.
                And very good list of examples, all of them also use PHP, Python and React, so your point is if you are a multimillion company you use "Rails", I work with such companies, and they are desperately trying to fix the messes created by the above-mentioned technologies, but unfortunately, some messes are difficult to replace and people with no understanding of tech @scottywalker92 make them even worse, and you know making a mess is a way to ensure job security, plus convincing misinformed people of what is good for them is definitely good for the ego and job security, we do not want to forget about job security.

                1. 1

                  I also hope you notice the irony in your last sentence. You’ve literally replied to this guys post trying to convince him of what’s “good for him”. I have little doubt that you do this for most of your contract work, convince misinformed people of rewrites and green builds to keep your work coming in? Nothing like that job security . . .

                  1. 0

                    of course I did notice, you are very funny

                2. 1

                  Did you just say that I have no understanding of tech?

                  Because I have a different opinion to you?

        2. 1

          This comment was deleted 24 days ago.

Trending on Indie Hackers
How I Launched My AI Startup with a Warm Email List and Zero Marketing Budget? 27 comments What you can learn from Marc Lou 19 comments Here's how we got our first 200 users 18 comments Software Developers Can Build Beautiful Software 10 comments Worst Hire - my lessons 8 comments Transforming Habits: What I Learned from 90+ Days of Regular Workouts 7 comments