pilino1234 / dat256 Goto Github PK

The following invariant needs to hold:
0 <= delivery weight

To weight input field in:

• View for posting delivery requests #5

See image, basically explains all:

Money lock is not very self-explanatory, so add some description underneath to help the user understand what it does.

• in #4 replace button "Accept delivery" with a button saying "Confirm delivery", if the owner is viewing the request.
• tapping the "Confirm delivery" button should mark the request as delivered
• tapping the "Confirm delivery" button should send the specified payment amount from the owner to the assistant.

The list item should contain

• item
• origin
• destination
• payment
• weight
• distance from origin to destination (km)

The view should contain inputs for the fields

• from
• to
• weight
• payment
• money lock
• item
• description
• photo
• button saying "Request Delivery"

• "Accept delivery" button in #4 should mark the delivery as accepted
• Accepted requests should not be able to be accepted again
• Accepted requests should disappear from #3
• Accepted requests should contain who accepted them

The user should be able to select an image using a file picker and upload it to firebase.

This function should be added to the photo input view in the view for posting delivery requests (#5).

Tweak the spacing on the delivery request form, so that there is less space between the from, to fields etc.

The app crashes if a photo isn't provided with the delivery request. Photos should be optional, and uploading without should work.

When you click accept/cancel/confirm/upload etc. there should be a toast that confirms that the delivery was successfully accepted/uploaded/confirmed etc.

• "Request Delivery" button in #5 should upload the delivery request.
• "Request Delivery" should be disabled if the user don't have payment amount of money to withdraw.
• Positing the delivery request should lock the specified payment amount away from the owner.
• Posted delivery requests should appear in #3

• in #4 there should be a link stating the assistant's name, if anyone has accepted the delivery request.
• tapping on the link should take the user to the assistant's profile page.

If some user flows doesn't work it needs to be fixed.

Add a button in the account tab #37 which logs out the user.

• #2 but replace the distance with delivery request status
• delivery request status is one of: available, accepted, travelling, delivered
• fill the list with all of my posted delivery requests

The switch should start in the off position.
Should be visible in:

• View for posting delivery requests #5

• switch users
• create users
• login users
• replace test data with real user

The following functions should be hooked up to the items in the navigation bar view (#7):

• See all available delivery requests
• See all my posted delivery requests
• Post a new delivery request
• See all delivery requests that I've accepted
• See my user profile

• in #4 there should be a link stating the owner's name.
• tapping on the link should take the user to the owner's profile page.

Add a README to the project root with the following points covered:

• Explain/document the project/directory structure (do this after merging dev and documents to master!). Where to find what.
• gitinspector output
• Source code
• Tests
• Binaries There are none.
• Link to Drive (if needed) Not needed
• Scrum data? How do we present the geekbot data? Not at all, kind of a lot of personal information
• Who is who? (see also mailmap)
• Links to stuff (what kind of stuff?)
• Explain code ownership There is none in our team setup
• How to the project up and running (requirements, installing dependencies, running)

The tab bar should contain the following navigation items (see mock for more details):

• Available delivery requests
• My posted delivery requests
• Post new delivery request
• My accepted delivery requests
• User profile

The following invariant needs to hold:
0 <= delivery payment <= owners account balance

To payment input view in:

• View for posting delivery requests #5

• #20
• when a user is viewing their own profile each editable field should have an edit button
• tapping the edit button should show an alert view with a text field to edit
• any edits to the fields should be saved

Create 2 users Alice and Bob, which we can use for the demo.
Make sure that all delivery requests look real. No TEST etc.

• #2
• fill the list with all available delivery requests

Delivery weight should be visible in the following views:

• Details view #4
• List item for delivery request #2

Delivery payment should be visible in the following views:

• Details view #4
• List item for delivery request #2

Delivery weight should be visible in the following views:

• Details view #4
• List item for delivery request #2

It should be clear to the user what the form does.

The view should contain

• item
• origin
• destination
• payment
• weight
• distance from origin to destination (km)
• money lock
• button saying "Show on map"
• button saying "Accept delivery"

• the view should contain public contact information: name, mail, phone, avatar

Should ask if the user wants to post a delivery or search for deliveries

• post concept picture in Slack
• implement views
• implement filters and send user to delivery list
• back button