This document provides an overview and status update of work being done to develop a Repairman App. Last week involved finalizing pages and committing code to GitHub. This week's focus is on services, authentication, and reworking the home page. Services include APIs for dispensers and user preferences. Authentication involves login and registration. The home page will show repair jobs using data from the backend and a reworked design. Next week involves implementing the backend, testing with real API data, and meetings with the PWA team.

1. MUHAMAD ALDY BINTANG
UNIVERSITY OF INDONESIA
2019/08/02

2. LAST WEEK
Merging User App project from my local to the other
Add Loading screen and Update Session
Finalization dashboard page as home page
Finalization the other page and commit to Github

3. OVERVIEW OF THIS WEEK
Services for Repairman App
 get Dispenser API from Jhonny
 store and get data from storage with Preference
Authentication page for Repairman App
 Login
 Register
Rework on Home page for Repairman App
 Fixing the design on HTML and CSS
 Try to generate data from backend (typescript) to be displayed

4. SERVICES FOR REPAIRMAN APP
Dispenser API, using the same format from User/Student
App:
Get token Get Dispenser Repair
Login Send Report
Register Repairman arrived
Function created inside the Dispenser API service:
getToken() getDispenserDetail()
getDispenserRepairCondition()
registerNewUser() getAssignmentDone() repairmanHasArrived()
loginUser() getAssignmentFuture()
getAssignmentToday()

5. SERVICES FOR REPAIRMAN APP
Preference Manager service, implement the same
technique as in User/Student App.
To set/store and get data in storage of browser.
Two function are created:
 setData() = set data into storage with key reference
 getData() = get data from storage using key reference

6. AUTHENTICA
TION PAGE -
LOGIN
Repairman can login
either using email
address or employee ID.
It has the same system
as User/Student App
login system.

7. AUTHENTICA
TION PAGE -
REGISTER
To register, Repairman
App has more attribute
than User/ Student App:
 Full Name
 Employee ID
 Profile picture
Repairman only can
register using company
email address, for
example:
 repairman1@ntust.edu.tw

8. HOME PAGE OF REPAIRMAN APP
It has same functionally as Dashboard page on
User/Student App.
It has three fragments:
 Done Mission
 Today Mission
 Future Mission
The UI design already given by Ms. Annie and
implement by Thariq
Rework some UI design and integrate it with data from
backend code (typescript)

9. HOME PAGE OF
REPAIRMAN APP
– DATA EXAMPLE
Besides is the example of
JSON object for Next
Mission.
Not raw data from API,
using this format so can be
displayed on HTML code.
For all three fragments of
Home Page were tested
using dummy data to know
if the design is working.

10. HOME PAGE – DONE MISSION
Done Mission divided into per
day.
It has report pictures which
from repairman when after the
repairment.
Pictures which stored in
base64 format must be
converted before displayed
using img in HTML.

11. HOME PAGE – TODAY MISSION
Today mission only shows the
mission stores in database with
the same day of repairman
phone time.
If the time is more than the
mission time, example:
 Repairman phone time = 12:00 PM
 Mission time = 10:00 AM
then the mission will disappear
from Today Mission list.

12. HOME PAGE – FUTURE MISSION
Future Mission has same
design as Done Mission but
without pictures.
It generate data which hasn’t
defined as Today Mission but
already given by the company
to the repairman.

13. NEXT WEEK PLAN
Create back end code to convert data from API to JSON
object format for each fragments on Home Page.
Testing using real data from API.
Have weekly meeting with PWA teams.
Maintaining User/Student App if any improvement.
 Dashboard:
https://smartcampus.et.ntust.edu.tw:5000/dashboard
 Test only:
https://smartcampus.et.ntust.edu.tw:5000/dashboard/MA_03_01