-
Notifications
You must be signed in to change notification settings - Fork 5
Project Report_4
AmeliaWen edited this page Nov 27, 2020
·
2 revisions
- User Documentation
- Implementation of Mobile Frontend
- Code Quality
- Project Management and Project Report
Task | Hours |
---|---|
User Documentation | 10 |
Implementation of Mobile Frontend | 70 |
Code Quality | 5 |
Project Management and Project Report | 5 |
- Date: Tue, Nov 17
- Time: 1h
- Attendees: all
-
Minutes:
- Identified tasks required for deliverable 4
- Prepare for presentation
- Discussed mobile activity ideas and themes for the frontend
- Split mobile frontend activity tasks according to deliverable 3
-
Tasks to be solved before next meeting:
- Implementation of each android activity
- Finish presentation slides
The following are some key decisions we made for mobile frontend
- In the purchase page, instead of a pop-op window when a user wants to apply new address for parcel delivery ad implemented in deliverable 3, we choose to use a new activity instead, due to the size of screen in mobile application. In this case, it might to easier for the user to complete purchase at the apply_new_address activity page, instead of add a new address then go back.
- After successful purchase, we use a new activity "successful payment" instead of a simple alert as implemented in deliverable 3, this is also due to the size of screen, it may provide better performance to have a separate activity indicating successful payment.