The latest articles on DEV Community by siddarthpatelkama (@siddarthpatelkama). https://dev.to/siddarthpatelkama https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4003834%2F5b7c10be-984c-41f4-9e6e-5705458fce67.jpg https://dev.to/siddarthpatelkama en siddarthpatelkama Fri, 26 Jun 2026 12:10:14 +0000 https://dev.to/siddarthpatelkama/building-an-anti-proxy-offline-first-attendance-platform-with-nextjs-express-firebase-15io https://dev.to/siddarthpatelkama/building-an-anti-proxy-offline-first-attendance-platform-with-nextjs-express-firebase-15io <p>Traditional attendance systems seem simple until you look at how they work in practice. Manual roll calls consume valuable class time, paper attendance sheets are inefficient, and many QR-based systems can still be exploited through proxy attendance.</p> <p>I wanted to explore whether a better solution was possible.</p> <p>This project is my attempt at designing and building an <strong>offline-first anti-proxy attendance platform</strong> from scratch as a solo developer. The goal wasn't just to digitize attendance, but to create a system that remains reliable in real-world environments while prioritizing security, scalability, and a smooth user experience.</p> <p>The platform is built using <strong>Next.js 16, React 19, TypeScript, Express.js, Firebase Authentication, Firestore, Firebase Admin SDK, Tailwind CSS, Capacitor, Progressive Web Apps (PWA), Sentry, and dynamic QR-based authentication</strong>.</p> <p>Rather than focusing only on features, this article explores the engineering decisions behind the project: why I chose an offline-first architecture, how dynamic QR validation improves security, the reasoning behind the technology stack, the challenges I faced during development, and the lessons I learned while building a production-style application that is already being used in my college club.</p> <p>The project is still evolving, and I continue to improve it whenever I have time. My aim is to keep documenting that journey by sharing not only what works, but also the mistakes, trade-offs, and architectural decisions that shaped the system.</p> <p>If you're interested in <strong>full-stack development, system design, Next.js, Firebase, TypeScript, or building software that solves practical problems</strong>, I hope you'll find something valuable in this article.</p> <p>⭐ <strong>GitHub:</strong> <a href="https://github.com/siddarthpatelkama" rel="noopener noreferrer">https://github.com/siddarthpatelkama</a></p> <p>💼 <strong>LinkedIn:</strong> <a href="https://www.linkedin.com/in/siddarthpatelkama" rel="noopener noreferrer">https://www.linkedin.com/in/siddarthpatelkama</a></p> <p>I'm always open to feedback, suggestions, and discussions with fellow developers. If you have ideas for improving the project or questions about the implementation, I'd love to hear from you.</p> webdev computerscience development vibecoding