UX Design Brief: Reggio – Teacher Attendance & Admin App
Project Overview
Reggio is a mobile application designed to streamline the process of marking attendance and managing classroom administrative tasks for teachers. The app aims to reduce the burden of paperwork, improve efficiency, and provide a centralised platform for educational documentation.
Problem Statement
Teachers face increasing pressure to manage multiple responsibilities, including the time-consuming task of marking attendance. Current paper-based systems are inefficient, prone to loss or damage, and environmentally unsustainable. There is also a lack of digital tools that offer reminders, accessibility, and integration with broader educational workflows.
Target Users
Primary Users: School teachers (primary and secondary levels).
Secondary Users: School administrators, education department officials.
User Needs
Quick and easy attendance marking.
Secure storage and retrieval of attendance records
Reminders for daily/weekly updates.
Ability to submit reports and lesson plans.
Accessibility across devices and platforms.
Inclusive design for varying levels of tech proficiency.
Project Goals
Simplify Attendance Management: Replace manual registers with a digital, intuitive interface.
Centralise Admin Tasks: Enable submission and sharing of reports and lesson plans.
Enhance Accessibility: Design for users with different abilities and tech experience.
Ensure Scalability: Build a solution that can grow with institutional needs.
Support Cross-Platform Use: Ensure compatibility with Android and iOS.
Design Considerations
User Interface (UI): Clean, minimal, and intuitive layout with clear navigation.
User Experience (UX): Prioritise core user journeys such as login, attendance marking, and report submission.
Accessibility: Use inclusive design principles (e.g., readable fonts, voice support, color contrast).
Data Security: Ensure user data is encrypted and securely stored.
Offline Functionality: Allow attendance to be marked offline and synced later.
Customisation: Enable date-specific reports and calendar integration.
Deliverables
User Personas & Journey Maps.
Wireframes & Interactive Prototypes.
UI Design System (Typography, Colors, Components).
Accessibility Audit.
Usability Testing Reports.
Final High-Fidelity Screens.
Annotated User Flows.
Presentation Deck for Stakeholders.
Success Metrics
Reduction in time spent on attendance tasks.
User satisfaction scores from teacher feedback.
Increase in report submission rates.
App adoption rate across schools.
Reggio UX strategy
Reggio is an app created to help teachers efficiently mark and manage student attendance registers. It is designed to provide a smooth and streamlined experience, enabling teachers to dedicate more time to other important tasks.
Problem:
Teachers face constant pressure to manage multiple responsibilities both within and beyond the classroom. Their success is often measured by their ability to tackle daily challenges effectively. One of the recurring difficulties they encounter is the time-consuming task of marking attendance registers.
Issues faced:
1. Excessive paperwork consumes valuable time and resources.
2.Important documents are at risk of being lost, damaged, or soiled.
3. Over-reliance on paper contributes to environmental degradation.
4. A lack of reminder systems leaves teachers without prompts for daily or weekly register updates.
5.Students with valid absences often miss crucial lessons and notes, creating learning gaps.
Important considerations:
1.Why is this app being developed?
2. Who will this app benefit once it has been completed?
3. How will these individuals benefit from using this app?
4. Is the concept feasible?
5. Is the concept scalable?
6. How can the app help educators manage tasks such as, marking the register?
7. Which operating systems or platforms need to be considered
when building this app?
8. What measures will be taken to ensure the app is inclusive, ethical, and accessible to users across various education levels?
Key objectives:
Prioritise Core User Journeys:
Focus on essential user interactions that highlight the app’s ability to provide seamless and effective solutions, ensuring an impactful experience for users.
Developing a unified platfrom:
Offer users a centralised platform for compiling register and admin related documentation.
Allows users to send or submit reports and lesson plans:
The app should enable users to manage and submit class reports and lesson plans, which can be shared seamlessly with members of an educational organization or institution.
Design for Accessibility:
Ensure the app is intuitive and user-friendly, accommodating individuals across various age groups and technical abilities.
Provide Informative Resources:
Supply users with educational materials and guidance to deepen their understanding of skin health and preventative measures.
Date specific customised reports:
Equip users with accurate and reliable reports through are date stamped and accessible through the calendar feature.
and tones?
Initial research:
Mobile application development involves creating software
designed to operate on mobile devices and tablets, which run on
operating systems like Android and iOS. The development process
is composed of key stages, including planning, design, development, testing, and deployment.
Each stage requires collaboration among individuals with specific
roles, contributing to the successful creation of a mobile application. Organisations can select a platform for their mobile app based on their specific needs, choosing between native platforms or cross-platform solutions.
Initial research:
Below are some most commonly used mobile application platforms
1. Android(Native)
2. iOS(Native)
3. Flutter(Cross-platform)
4. Xamarin(Cross-platform)
5. React-native(Cross-platform)
Initial research:
Button Size Standard:
45px -72px
High priority button = 72 pixels
Medium priority button = 60 pixels
Low priority button = 42 pixels
Button Spacing Standard:
12-24 pixels for a large button
24-36 pixels for a medium button
36-48 pixels for a small button
Typography:
Page titles = 20pt
Paragraph text = 14pt
Buttons = 14pt
Text inputs = 16pt
Other important considerations for app development:
Adopt User-centered Design
Focus on app responsiveness
Performance optimisation
Adopt the best codebase architecture
Prioritise app security and user’s data privacy
Consider adding offline Support
Continuous and Quality Testing
App store optimisation (ASO)
App updates and maintenance
Resource: Best Practices for Mobile App Development in 2024 – GeeksforGeeks
Structure
To build a simple app that will streamline the process of marking the register and other related tasks:
Screen 1: The app needs to have a simple login screen with text or interactive fields allowing the user to enter their user name and password.
Screen 2: The app needs to have a homescreen or dashboard with the user’s name as a title followed by the class they are currently teaching, five centralised tabs linked to tasks that may need to be completed by the user on a daily basis (mark the class register, submit a report, daily lesson plan, calender & old reports). There needs to be a feature allowing the user to convert documents to various formats (word, pdf, xls, powerpoint & odf).
Screen 3: The app needs to have a menu with items ‘profile, settings, old reports & logout’ (optimised for mobile & other small devices).
An admin will have access to adding, editing or removing accounts remotely. The information declared on the app will be sent to a database that will send the relevant information via email to the admin.
Flow
The userflow is a simple diagram allowing us to map a user’s journey while using the app:
Build
The next step would be to conceptualise how the app will function while prioritising a strong user friendly UI:
Login screen with a simple two step verification process.
Dashboard/ home screen with four centralised tabs
and a menu with the items ‘profile’, ‘settings’, ‘old reports’ & ‘logout’.
