wouterdeman / timesheet.chrome-app Goto Github PK

The client should be able to add/remove/edit it's current position as a new location or link it to a customer that is represented by the timesheetmodule and stored as a location in the tracking service.

There are issues with the selection of the google account you want to use. The chrome app currently starts an auth web flow and from then on the user is in the hands of what google sends back as account selection page. We should investigate if we can suggest the selection of @bite accounts and that the approve dialog is shown only once (interactive: false ?).

As privacy is a big issue when sending location and time based information the user running this client should be able to easily control wether the chrome app is sending information to our services. When you imagine a use case where employees need to inform their employers about their location during working hours he/she will be obligated to send time/location information to inform his/her employer but we want to let the users feel confident using a client like this from day one.

Can we use polymer in our first client, what are the advantages ?