Article · About a 10 minute read

The Three Things to Never Build In Your App: Authentication, Notifications, and Payments

Tejas Kumthekar · Courier Free Beginner

This is the cleanest framing of the exact call you are making: which parts of your product are your actual reason to exist, and which are solved problems you should assemble rather than build. It argues that auth, payments, and notifications are commodity infrastructure where rolling your own mostly just delays your MVP. Treat it as a starting point for the decision, not a rule, since a few products do have a real reason to own one of these layers.

• Auth, payments, and notifications are solved problems, so building them yourself usually costs you launch time you cannot get back.
• Your build effort should go into what makes you different, not the plumbing every app needs.
• The author says outsourcing these three would have shortened his own MVP timeline significantly, which is the honest lived version of the argument.