Define Technology Stack

[JamesFranc]

We need to discuss and justify the technology stack.

• [ ] Server (Infrastructure)
• [ ] Backend (Application)
  • [ ] Database type (is a database necessary for early implementation?)
  • [ ](If yes) Connecting to database and handling data
• [ ] Front-End (Application)

[lucymariej]

Just writing out our current thought process based on our discussion yesterday. Correct or add any info you like @JamesFranc

Server/Database: So, we have already decided for sure our first implementation is only going to be hot-seat and only save game info locally, so we won't need server or database implementation for the moment, although we might want to have that conversation here for later after we figure out the front-end?

As for the front-end, I know we were talking about using Javascript/Html/Bootstrap(MD), Javascript/Html/Material, or just using Unity, with the thought that using web-based technologies makes sense as long as we can use Material or MDBootstrap to give us card functionality, although Unity will give us quicker functionality on gestures. (although web has a nice extended functionality for dragging: UI Touchpunch)

If I missed anything, feel free to add along. Figured keeping this discussion here would keep us on track.

[lucymariej]

MDBootstrap JQuery UI TouchPunch

[JamesFranc]

• Tether - JS library for defining the position of UI elements (this is a dependency for Drop and Shepherd)
• Drop - This might be useful for in game tooltips
• Shepherd Intro level to the game and quick access to info during play
• CountUp - Potentially useful for any numerical animations in game

Also it seems as though we've landed on a web stack (JS in particular)