3 ms·
Why does it take over 40 hours to implement features, which have been implemented for millions of times and have existing solutions and code in the Internet. Au
by zhuxuefeng1994 10y ago
Why does it take over 40 hours to implement features, which have been implemented for millions of times and have existing solutions and code in the Internet. Authorization (Social and Email) seems to be one or two hours of work with existing solutions.
- fredoliveira 10y agoAnd you think you can build a great integrated experience that just works with multiple platforms in "one or two hours of work"? Am I right in assuming that you never built systems like this?
- zhuxuefeng1994 10y agowhy not? There are lots of existing scaffolding having authorization setting up using passport https://github.com/jaredhanson/passport https://github.com/jaredhanson/passport You don't even need to write code if you use https://github.com/rethinkdb/horizon https://github.com/rethinkdb/horizon, firebase, or similar services. For client side, you can reuse previously written code for authorization logic and just write user interface based on requirement. 40 hours are too much for such work
- Skilleen 10y agoI agree, according to the article, the front end of "email authorization" takes the most time to do. For an MVP a login system really just has to work, and then you can personalize it more as you go. Most of the time for an MVP should be dedicated to the main features of app. (In this case uploading pictures, news feed, etc). For my app we used Auth0 to quickly get login working before we had to present it. It took about total 5 hours to set up and test. Since then we have built our own login system and made sleek looking create/login screens; which in total took about ~15 hours.