LACES PLATFORM PAYMENT and ADDITIONAL FUNCTIONS

The LACES platform ([login to view URL]) is a new web platform born to connect certified fitness trainers and clients that want to have fitness classes where they prefer. In order to launch our service online the platform needs an upgrade, implementing several new functions. The platform is actually online and active (alpha version). The database has been designed and deployed and is almost complete and where it is not, everything is arranged to be completed. Anyway some minor addition or modification may be necessary for developing the new functionalities. BRIEF DESCRIPTION OF THE ACTUAL VERSION: 1 - developing theory: "single page app" 2 - server side : REST web service developed in Java language which rely on the JAX-RS API by means of Jersey ([login to view URL])library , which communicates with the database thanks to the Java Persistence API (JPA) / Hibernate ([login to view URL]); 3 - client side: Single page application based on the client Model View *(MV*) framework Backbone.js for Javascript ([login to view URL]) and the HTML, CSS and Javascript framework Twitter Bootstrap ([login to view URL]). WHAT WE NEED - Implementation of the oauth2 protocol on our server to guarantee safety communication and transfer of data and information of client and trainers. - Implementation of the online payment system (stripe and/or paypal). This payment system will be used for the payment of the classes from the users to the platform and, then, the platform will transfer the money to the trainers (once per week/month). It will be usable the code that the payment providers offer for free. ADDITIONAL FUNCTIONS: - See the classes TRAINER: possibility, for the trainer, that after the creation of a class to see, adding a button, the classes created directly on his profile page; - See the classes USER: equally, but the possibility is to see the “booked classes”; - Delete a booking by the user: add a button on client side and create a connection between the client side and the not yet developed "delete API"; - Delete a class by the trainer: add a button on client side and create a connection between the already developed "delete API"; - Notification center: when a class is deleted by the trainer, all the client that were booked needs to receive an e-mail (and a notification direct on the platform). The implementation of some aspects related to these functionalities may be constrained by some design choice that we have been already taken. These can also be discussed after the first contact.