SupremeClassroom
AI based peer learning and attendance system
Created on 28th December 2025
•
SupremeClassroom
AI based peer learning and attendance system
The problem SupremeClassroom solves
🧩 The Problem It Solves
Modern campuses suffer from fragmented systems.
Students use multiple apps for attendance, learning materials, food, notices, and discussions.
Admins rely on manual work, paper registers, or unsafe proxy-based attendance.
This causes:
❌ Wasted time
❌ Low student engagement
❌ Attendance fraud (proxy)
❌ Poor peer learning
❌ Scattered information
💡 What Campus Super App Does
Campus Super App brings everything into ONE secure Android app, making campus life simpler, safer, and smarter.
🎯 Core Use Cases (From First Principles)
1️⃣ Peer Learning (Knowledge Grows Together)
First principle:
Students learn better when they teach, discuss, and validate ideas together.
How the app helps:
Students ask doubts
Other students answer
Answers get upvoted by peers
Best explanations rise to the top
✔️ Encourages active learning
✔️ Builds confidence & communication skills
✔️ Reduces dependency on teachers for small doubts
2️⃣ AI-Based Help (Instant Support)
First principle:
Help should be available anytime, not only during class hours.
How the app helps:
AI explains concepts
AI gives hints, summaries, and clarifications
Helps students revise faster
✔️ Saves time
✔️ Personalized learning
✔️ Reduces stress before exams
3️⃣ Smart Attendance (Location-Based Verification)
First principle:
Attendance should verify physical presence, not just a name.
How it works:
Attendance opens only in class time
Student must be inside campus/class location
GPS + session timer verifies presence
Automatic notifications remind students
✔️ Prevents proxy attendance
✔️ Fully digital & secure
✔️ No manual registers
4️⃣ Centralized Campus Services
First principle:
One identity → many services.
Students can:
Order food 🍔
Access library 📚
View learning materials 🎓
Participate in discussions 💬
Buy/sell items 🛒
✔️ One app, one login
✔️ Faster access
✔️ Less confusion
🛡️ Safety & Reliability
Location-based attendance → no fake presence
Role-based access (Student / Admin)
Real-time sync → accurate data
Notifications → fewer missed classes
🚀 Why It’s Better Than Existing Systems
Existing Systems Campus Super App
Multiple apps One unified app
Manual attendance Location-verified attendance
Passive learning Peer + AI learning
No feedback loop Upvotes & discussions
Delayed help Instant AI support
📱 Platform
Android App
Built using React Native + Expo
Designed for Indian campuses
🏁 Final Impact
Campus Super App makes campus life:
Smarter → AI + analytics
Safer → Location-based verification
Faster → One platform
More engaging → Peer learning & upvotes
💬 It turns a passive campus system into an active digital ecosystem.
Challenges we ran into
🚧 Challenges I Ran Into (and How I Solved Them)
While building Campus Super App, I faced several real-world development challenges. These weren’t just coding issues, but system-level and time-management problems.
⏱️ 1. Adding Many Features in Limited Time
Problem (first principle):
Time is a finite resource, but features grow non-linearly.
I was building:
Peer learning system
AI help
Attendance with location verification
Admin dashboards
UI + navigation
Trying to build everything at once caused:
Feature overlap
Bugs due to rushed integration
Mental overload
How I solved it:
Broke features into core vs optional
Focused first on attendance + dashboard (core value)
Added AI and peer learning incrementally
Reused components instead of rewriting UI
✅ Result: Working MVP first, polish later
🔑 2. Gemini API Key Errors (AI Integration)
Problem (first principle):
APIs require correct authentication + environment setup.
I faced:
Invalid API key errors
Requests failing silently
API working in browser but not in app
Root cause:
API key not exposed correctly in Expo environment
Incorrect use of .env variables
How I solved it:
Stored the API key using Expo environment variables
Restarted Metro bundler after changes
Added proper error logging instead of silent failures
✅ Result: Stable AI responses inside the app
🗄️ 3. Supabase Errors (Auth & Data Sync)
Problem (first principle):
Backend systems are state-dependent (auth state, session, permissions).
I faced:
Auth state not updating correctly
Data not syncing in real time
Permission denied errors
Root cause:
Incorrect Row Level Security (RLS) policies
Auth listener not cleaned up properly
Navigation triggering before session was ready
How I solved it:
Fixed RLS policies for user roles
Used onAuthStateChange carefully with cleanup
Delayed navigation until session was confirmed
✅ Result: Reliable login and real-time data flow
🧠 Key Learnings
Build core logic first, features later
APIs fail silently unless logged properly
Backend security rules matter as much as frontend code
Debugging is a skill, not a mistake
🏁 Final Takeaway
These challenges taught me how real applications break — and how to fix them systematically.
💡 Writing code is easy. Making systems work together is the real engineering.
Tracks Applied (9)
Creative Use of Kiro
AWS
Requestly
Requestly
DigitalOcean
DigitalOcean
Cloudflare
Cloud Flare
InsForge
InsForge
Best Blog Post
AWS
Top Feedback
AWS
Social Engagement Prize
AWS
Gemini API
Gemini
Technologies used