Okay, so you want to build a web app. Let's use a very basic web application for instance. The user story is this: The user logs in. The user goes to another page, which has a form. When the user clicks submit, data is saved and they can view it later. It will also send an email five minutes later that does something with that data. That sounds like super simple app? Easy! You can totally build that no problem. Hold on. Not so fast there. Let's break it down to see what's actually going on, and then you decide whether it's truly easy. The user logs in. This clues us in that there is some form of authentication. There are many forms of authentication, not all created equal or easily created. Such as: You could use OAuth, as in, not actually do the authentication yourself. Leave it to Google or whomever to do it for you, and instead store an encrypted oauth token. If you're using Rails, you could use Devise and then it's not a matter of implementing but rather integrating. Again, if you're using Rails/ActiveRecord, you could leverage has_secure_password to create your own user system while having a streamlined password approach that's been fine-tuned for you.


I guess you came to this post by searching similar kind of issues in any of the search engine and hope that this resolved your problem. If you find this tips useful, just drop a line below and share the link to others and who knows they might find it useful too.

Stay tuned to my blog, twitter or facebook to read more articles, tutorials, news, tips & tricks on various technology fields. Also Subscribe to our Newsletter with your Email ID to keep you updated on latest posts. We will send newsletter to your registered email address. We will not share your email address to anybody as we respect privacy.

This article is related to

Architecture,Web App