A comprehensive TODO list about cs1699project HOT 6 OPEN

@pitchaim I figured this would be the payment flow, feel free to offer suggestions,

1. The user requests an errand costing $10, since this is a micropayment, the fee is 5% of the cost, plus $0.05, so the total cost would be $10.55. We can hold onto that money until the person who requested the errand completes it, thereby making our life easier if someone tries to steal money by saying they completed the errand without doing it.
2. When the user finally completes it and both parties (Requester and Runner) are satisfied, the runner can request to get paid the $10. To payout with paypal, it costs $0.25 per payout. So this would be bring the overall cost to $10.80, if we don't take any fees out for ourselves.

So we can use paypal checkout for making the errand, and then paypal payout for paying people

Or we could also do, we don't charge anyone until someone accepts the errand, that way they can cancel it if they need to without getting charged

from cs1699project.

Tomorrow after my classes I will work on 3.

And 5, as they kind of relate.

from cs1699project.

https://github.com/square/retrofit/tree/version-one this library can be used for the PayPal rest calls

from cs1699project.

@ajhenry re. 2a, do we want to integrate Paypal on Request Errand (& set up price/payment tracking throughout) or when a task is complete? The Braintree API for Express Checkout I'm working with now will just drop the user into a payment window when they want to make a payment, so we could include a Paypal button in the Task activity or just open the Braintree activity when someone marks a task complete. Might make life easier, and no need to track Paypal login on our end.

from cs1699project.

I will take care of 1, and push it up in a few

from cs1699project.

I can work on the Feeds next, it may not be until the weekend however, if someone wants to do it before then, lemme know

from cs1699project.