Technical Specification: "Schoolar" Project Overview: The objective is to develop an optimized, stable Android application titled "Schoolar." The UI must adhere to a minimalist-compact aesthetic, utilizing the Ubuntu font family, fluid animations, and a strictly text-based interface (no icons).

  1. Initialization & Onboarding Upon the initial launch, the application shall execute a three-step configuration wizard:

Step 1: Administrative Security: Establish a master password for Teacher (Admin) access. Step 2: Database Population: Option to batch-add student profiles or bypass for later configuration. Step 3: Curriculum Setup: Define a daily timetable (maximum 6 periods). This includes assigning lesson names and precise start/end timestamps. Completion: Upon finalizing the setup, a confirmation modal shall appear with the text: "There, all set."

  1. Global Features & Aesthetics Theme Engine: A dynamic theme switcher allowing users to toggle between Dark and White modes. System Utilities: A "Factory Reset" function located within the settings to purge all local data and return to the initial setup phase. Design Language: A clean, icon-free layout prioritized for high performance and readability.

  2. Lock Screen Interface The persistent lock screen serves as the primary dashboard: Header: Centrally aligned digital clock and date. Dynamic Timetable: A bottom-center module resembling a calendar interface. It must display 6 editable lesson slots (e.g., Lesson 1, Lesson 2, etc.). Navigation: A top-right trigger button to access the user-selection menu, containing Teacher, Student, and Settings (all of which require the Admin password for entry, except the Student profile).

  3. User Profiles & Permissions

A. Teacher (Administrator) The Teacher profile grants elevated privileges for full database management: Student/Curriculum Management: CRUD (Create, Read, Update, Delete) capabilities for student rosters and lesson schedules. Security: Ability to modify the Administrative password. Evaluation System: Full authorization to input, modify, or strike through academic evaluations within a digital diary.

B. Student (Public Access) Designed for shared-device environments without password barriers: Roster View: A comprehensive directory of up to 40 students (e.g., Student 1 through Student 40). Personalized View: Selecting a student profile reveals a real-time timetable and the evaluation diary for the current date. Historical Data: A dual-row date navigation system allowing students to scroll back and review previous academic records.

Share this project:

Updates