authentication

[YhorbyMatias]

¿What if we implement facebook and google authentication?

[amhed]

What if we define what the app will do first before authenticating anyone?

On Wed, Jul 20, 2016, 4:50 PM Yhorby Matias Heredia S. <
[email protected]> wrote:

¿What if we implement facebook and google authentication?

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
#3, or mute the thread
https://github.com/notifications/unsubscribe-auth/AAjW2xRtUXK-1Xaz66k7z0Mp9ae4qUGCks5qXrRCgaJpZM4JRUYg
.

[YhorbyMatias]

oK I agree, what the app will do?

[amhed]

• It will have registered users
• In order to become a registered user you need to share a book
• Sharing a book means adding it to the database
• If a book already exists, it shouldn't get added to the database again, but is should augment the amount of books available for sharing in inventory
• A registered user can view all books that have been shared
• A registered user can search the books by name
• A registered user can request to have a book lent to him/her. When that happens there's a series of rules that the system must put in place:
  • You can have a book for 30 days
  • You can only have one book at a time
  • After 30 days you need to return the book to the next person on queue
  • You can request to be on the queue for any book you want, but you must wait your turn

There's more case scenarios, but these ones are the ones that come to mind right now. These should all become issues, and they should be completed using TDD as well