SHAMEL connects attendance, identity verification, academic scheduling, reporting, and role-based operations across a browser workspace and a Flutter mobile application.
An operational layer for a university—not another isolated attendance register.
SHAMEL organizes daily academic work around five defined roles: system administration, college coordination, teaching, student self-service, and gate operations. Each role sees a focused interface while working against the same institutional records and API.
Two platforms
One system of record. Two ways to work.
01
Web platform
A full browser workspace for university-wide administration, college-scoped coordination, teaching workflows, student services, and gate monitoring.
Dashboards and role-based operational views
Scheduling, classrooms, courses, exams, and records
Exports, audit history, reports, and live gate workflows
02
Flutter mobile app
A role-aware Android application built for fast access to schedules, dashboards, reports, people, gate records, and authenticated university data.
Secure token-based access to the same REST API
Role-specific navigation for admin, coordinator, teacher, student, and gate
Local theme preference and resilient API discovery
How they work together
A shared operational loop.
01
Capture
Gate and lecture events enter through browser or mobile workflows.
→
02
Authorize
Authentication and role scope decide what each user can access.
→
03
Synchronize
Both clients use the Django API and institutional data model.
→
04
Act
Dashboards, warnings, reports, and approvals reflect the same records.
Source-verified architecture. Live production connectivity is not claimed by this website.
Complete feature inventory
Verified in the project source.
Every item below maps to an implemented route, data model, API endpoint, or Flutter screen. Planned and fixture-only functions are excluded.
Product video
See the complete operating model.
The longest verified product film in the project: a 50-second tour built from real SHAMEL interfaces and source-backed architecture.
Real product UI
Screens captured from the working project.
The selected evidence set was visually reviewed before publication. Permission prompts, device launchers, black frames, and duplicate states were excluded.
Security, storage, integrations & ownership
Institutional control is part of the architecture.
01
Security
Role-based access, bearer-token mobile authentication, audit records, login protection, and scoped data access are implemented in the source.
02
Storage
The deployment supports PostgreSQL for the server and SQLite-based local or edge operation. Biometric templates are stored as embeddings rather than raw identity claims.
03
Integrations
Django REST endpoints connect the web and Flutter clients; Channels supports real-time updates; export routes produce CSV, Excel, and PDF reports.
04
Data ownership
SHAMEL is designed for institution-controlled deployment. This website does not claim third-party certifications or provider guarantees that are absent from the project evidence.
SHAMEL
See how connected campus operations can work.
Explore the real interfaces, product film, and verified capability inventory above.