5
10 Comments

Tech stack does actually matter

For the indie hackers out there that say that tech stack doesn't matter, I say: it actually matters.

But not in the way you'd think. It doesn't matter for the success of the company because some stacks are flashier or more optimized for performance.

It matters for development speed. If you, as a technical indie hacker, can develop, iterate and deliver fast, then the tech stack is good enough. More than often, that means traditional boring technologies. For me, it is Python, React, Bootstrap and Postgres.

It is crucial, especially before you have a proven business model, to choose the technologies that you are most comfortable with.

And don't waste time building non-mission critical features.

I spent way too much time in the past:

  • developing user management flows
  • manually developing OAUTH2 flows for social logins
  • developing fully automated flows for payments
  • almost building my own customer support tools inside the products I was building.

Now, with SpamLabs, I do it differently:

  • integrate already existing user management (Clerk.com) which already supports out-of-the-box social logins
  • use customer portal and payment links to manage payments. No callbacks and fully automated flows yet.
  • use Crips.com for customer support.

Let's go 🚀

, Founder of Icon for SpamLabs (discontinued)
SpamLabs (discontinued)
on August 21, 2023
  1. 2

    Why Clerk.com vs. firebase login?

    1. 1

      You might want to take a look at this featured IH article that was posted a while back that talks a lot about the answer to this question directly: adding-auth-to-your-project-everything-you-need-to-know-plus-recommendations

    2. 1

      I fiddled around with firebase and it lacked the UI part. With Clerk.com they also provide official ready-to-go UI for register, login, user management, emails, etc. which was a big plus for me. For firebase I only found some open source projects offering that but they seemed pretty unmaintained to be comfortable using them.

      Also, firebase often pushes you to use them as an ecosystem, including their other services. I just wanted an auth system that works.

      1. 1

        Thanks for the details.

  2. 1

    That's a great point, use the tech stack that allows you to move fast.

    I will even add one controversial point: avoid testing in the beginning. It will slow you down. Build what your users will see as fast as you can and avoid what is not user facing.

  3. 1

    Which services are you using specifically for payments?

    1. 1

      Right now just Stripe, more precisely their customer portal + pricing tables.

  4. 1

    I totally agree with you. Why would anyone should deal with something like auth when we got so many awsome solutions out there that we can use for nearly free at the beginning.
    Use whats good for you and don't follow any "hey you must try this out"-Trends if itsnot usable for you.
    For me I use most of the time Angular, Angular Material, NestJS and Postgres

    1. 1

      100% agree. Using a familiar stack and using integrations/already made solutions where it makes sense is way better than trying things out. Of course, that is if you want to ship.

Trending on Indie Hackers
Hi IH — quick update. The MVP is live. User Avatar 33 comments Building ExpenseSpy solo, no funding — launching June 17 on iOS & Android User Avatar 26 comments Day 7: 51 people answered my question. I wasn't ready for what they said. User Avatar 18 comments I Built a Football Sentiment Platform in 18 Days. The World Cup Starts in 7 Days. Now I Need Distribution. User Avatar 17 comments Built an n8n booking alert system — is cold outreach dead for B2B micro-tools? User Avatar 16 comments I built a $5/1k-listing CRE data API because CoStar is overkill for first-pass scans User Avatar 14 comments