Tiêu đề [External] ESL Specs_ Plingo analytics dashboard.pdf ✅

Change set: 1. Add students update 2. List of students 3. List of activities 4. Group activity 5. Individual activity 6. List of homeworks 7. Assign homework 8. Review homework ESL Specs: Plingo analytics dashboard 1. Overview 1.1. As we see a growing interest to learning data analysis among our potential clients, we want to provide them with a dedicated tool that will serve the following purposes: 1.1.1. School district supervisors will be able to quickly understand the current state and the trends in performance of the schools that belong to the district. 1.1.2. School managers will be able to analyze performance of the exact school with ability to segment it by teachers, classes and even analyze individual students. 1.1.3. School teachers will be able to analyze classes they teach. 1.2. Our Dashboard will serve all the purposes mentioned above, but different roles will have different access types, so school manager will not be able to analyze district, school teacher will not be able to analyze classes they do not teach and district supervisor can have full access though (though they most probably will not be interested in digging too deep). 1.3. Our current focus is to develop a demo of such a dashboard tool and use our own data to demonstrate the possibilities. We will provide a link to this tool to interested clients so they can have a feel and provide more specific feedback on what they really want. 2. Related Files and Designs (incl. content) 2.1. UI - Figma project 2.2. Charts library - recharts
3. User experience requirements 3.1. Authorization 3.1.1. When an unauthorized user accesses the Dashboard, they see an Authorization screen with one possibility to use Google Authentication. 3.1.2. When the user presses the “Continue with Google” button, they see a standard flow of Google authorization start (where they need to sign in to google, choose account, etc) 3.1.3. If any issue happens and the user is not authorized, they stay on the Authorization screen. So they can try again. 3.1.4. Once a user is authorized, they see the Dashboard appear. 3.2. Instructions overlay 3.2.1. If a user authorizes for the first time ever, they see an overlay with instructions appear on top of the dashboard.
3.2.1.1. For the MVP, the “first time ever” can be determined by the existence of a specific cookie that gets set after dismissing the overlay. I.e. “first time with this browser history”. 3.2.2. When a user presses the “Got it” button, they see the overlay disappear. 3.2.3. When the user presses the overlay (semi-transparent area), nothing happens. We don’t want users to accidentally close the instructions. 3.3. Outdated data overlay 3.3.1. When a logged in user returns to the dashboard and we know the data is outdated, a user sees an overlay appear on top of the Dashboard asking them to reload the page. 3.3.1.1. For MVP, the definition of the “outdated” can be as simple as “no action was made on the page for >1h 3.3.1.2. Post-MVP, we will consider other criteria (incl polling the data status) 3.4. Add students overlay 3.4.1. A user can add students via an overlay with QR code. This overlay appears in the following cases:
3.4.1.1. User presses a QR code button in the School (Class) view. 3.4.1.2. User presses a dedicated button in the List of students. 3.4.2. A user can close the overlay by pressing the corresponding button and return to the page they triggered the overlay from. 3.4.3. When changing the class in the corresponding dropdown a user sees the QR code changes to reflect the selected class. 3.4.4. Once the student installs and/or opens the app using the QR code, they appear in the corresponding section of the Add students overlay. Hence that student is added to the class.