Skip to content

Comment on Ask HN: Ok to only allow Google/Apple/FB login for mobile app?

Comments

From what you decribe I would skip the registration and use the payment checkout page (e.g. Stripe) to collect all data. It sounds like a new app so first have 100 sales before worrying about more complexity. (In our SaaS startup we dealt with the first 50 sales using email and manual Excel).

Sorry, forgot to add that the app does have some limited adoption/validation using a MVP version of the app. Though I also agree with you and leaning towards "payment-checkout authentication" just so I can release sooner.

However, I was wondering more in general: is there a point at all in having username/password authentication in a mobile app these days, for the reasons i pointed out.

is there a point at all in having username/password authentication in a mobile app these days, for the reasons i pointed out.

It depends on your target market. Requiring social media/google/apple accounts in order to use your app means that there will be a lot of people unable or unwilling to use your app.

Whether or not that matters to you is a business decision that only you have enough information to make.

AboutSource Built by g1lg1l

Hackerly is an independent reader for Hacker News, built on the public HN API. Not affiliated with Y Combinator.