I would disagree here. You probably need OAuth with popular social services and implement username, password or OTP-based auth overall. For an MVP, you don't need to care about more details beyond this; it is hardly 10% of the entire effort, if not 5%.
replyI feel seen. It's compounded if you also need to add HIPAA row-level security compliance that spans to every form of resource.
replyIt takes like an hour. So that's a quick mvp then
replySocial logins, email logins, password resets, multi-tenant, organizations, many to many users to organizations, etc etc. Not necessary for MVP, but can definitely be painful hacking in later if the MVP hits.
replyWhat you are talking about is in a large part authentication. You can do authentication using an external service and still have your user table locally. You can also do authorization locally with a local session table while leaving authentication to a SaaS.
replyBy the time you're so big you need all of that, there will be other people at the table to "hack that in".
replyI strongly disagree. If you’re selling to other businesses, much of that is an expectation.
replySocial logins, multi-tenant and organizations are very far from table-stakes for an MVP.
replyWhether it's painful to put in later or not is sadly nothing that the managers and executives concern themselves with.
Depends on the company and product. The SSO/Social login, multi tenant and multi platform are indeed needed for my MVP.
replyAll I am seeing here is Django modules
replyDjango, Rails etc handles this.
replySo... you just have to not build your web app in the most popular web app language? Somehow i think there will be big time debt from that decision
replydeleted
reply[dead]
reply