Client Design Discussion

[jacksonschwarz]

Lets start abstracting the Client in this thread. Lets go off this point: The core functionality is tracking who takes what so on client side we need to be able to record the person's info, the item(s), the time in and out. We want to know what's available and what isn't. Maybe know who owns what like in our case we had to know if a item belonged to MLH, IEEE, or Tech sandbox So based on this statement, we need as a bare minimum:

• a login/sign up page, taking in the student's name and ID
• a page for selecting/borrowing items
  • potentially a dialog for the actual sign-out form

Let my know if anything should be added, after all, this is just a bare skeleton. Without a doubt, this should be a single-page application, and so a framework discussion should start here as well. I'm strongest with Angular2, so it has my vote but I'm willing to learn otherwise.

[Ethan-Arrowood]

I say we do not do a login/sign up page at first. Auth systems are not easy to implement and I’d rather focus on the utility of POB application. If we have time at the end (which I doubt) we can consider implementing an auth Page. For now I think we just have ‘users’ enter in their personal details when they want to borrow something

[jacksonschwarz]

@Ethan-Arrowood That actually makes a ton of sense, just to make that part of the form instead of a separate entity

[Ethan-Arrowood]

Exactly. So what I’m imagining is a pretty simple SPA that has a menu. That menu contains links to different ‘pages’ (but are actually just different components. You know what I mean). Each component or view would be a different function for the app.

1. Manage inventory of items. (Add, remove, edit)
2. Borrow an item (this would probably include a sorta menu to browse inventory and then a form to ‘check out’ an item/items)
3. Return an item (would maybe bring up list of borrowed things, select what’s being returned and then everything updates itself)

[jacksonschwarz]

I agree with the idea of an inventory view, I think it would be smart to have it also function as a returning option(just by selecting/swiping the item, similar to deleting an email). Both the inventory and the list of items to be borrowed could be the same component with different flavors.

[Ethan-Arrowood]

Interesting idea, if that’s something you think you can implement I say go for it 🎊 Id encourage you to consult with everyone else before moving forward to get varrying opinions.

[ShawnToubeau]

I came up with these two concepts, let me know what you think!

[ShawnToubeau]

This too

[jacksonschwarz]

I'm a fan of the Admin user idea, that will be super useful for keeping track of who specifically has taken out what.

How will the users actually check out items? I'm thinking if we have the Welcome page it will be as simple as just clicking on the item with a small confirmation dialog. Thoughts, everyone?

[ShawnToubeau]

We could have like a virtual "shopping cart" where people can click on individual items and add them to their cart

[jacksonschwarz]

I love that idea, that way it can be super simple to add items to the cart, and we could just have a "checkout" component

[ShawnToubeau]

Like in the last image, imagine a button that says "check out item" under the details section

[ShawnToubeau]

Or right next to the item name

[jacksonschwarz]

It could be a button in the corner of the item list, maybe with a badge saying how many items you selected, so you could select more than one item and check them out all at once. That being said, I still like the idea of the item's transaction history being public

[ShawnToubeau]

Exactly! I think this gives us a good idea of what we need so we should get started building it 🙂