Hi Everyone,
I’ve been building Campus Coding — a small platform for campus-style placement prep: timed exams, coding (run vs test cases), MCQs, exam flow, results, leaderboards, and staff tools to manage exams and questions.
I originally built it for normal campus use. Now I want real usage and honest feedback — especially from developers who work on real products (startups or bigger companies). I care about UX, reliability, and security (auth, permissions, exam integrity, anything that feels off).
check here: link in the comment.
Accounts
- Sign up as a student — you need an email you can verify (verification link is required; password reset also goes to email).
- Don’t want to use your real inbox? You can use something like Mailinator (public disposable inbox) just to grab the verification / reset email — fine for testing. Don’t reuse important passwords on demo setups.
Quick demo logins (shared — please don’t break or change passwords; I’ll rotate if needed):
- Student:
student@demo.com/123456 - Teacher:
teacher@demo.com/123456
What would help most
- First 5 minutes: what confused you or felt broken?
- Would you use this for practice? Why / why not?
- Compared to LeetCode / Codeforces / Moodle / HackerRank-style tools — what’s missing for you or for running a class?
- Bugs: browser + steps to reproduce.
- Security / abuse concerns: if something looks wrong (access control, exam flow, weird API behavior), say so — responsible heads-up is welcome (no need to hammer production).
I’m one dev; I’ll read everything and triage. “Not for me because X” is still useful.
Thanks for your time.