In this episode of my Solo Startup Series, I’m keeping it very real: I’m juggling my full-time job (two laptops life), building this edu-tech platform in every spare 15-minute window, and still trying to make meaningful progress. I walk through what I shipped over the last two weeks—especially around authentication and the signup flow—and I also address a security concern you guys pointed out. Even though I’m not sending sensitive data back to the client (mostly just status codes/booleans), I do currently show “email already exists,” which is great UX but can be abused via brute force. My plan is to handle it with rate limiting (I’m not a fan of reCAPTCHA UX). I also talk about my internal CSS dilemma: I’m an SCSS fan, and I genuinely hate how Tailwind looks inline… but responsiveness finally sold me. Once I started building mobile-first and using consistent sizing, everything snapped into place and the UI became way easier to scale across devices. The big highlight is the “super sexy” Stripe payment details UI. I’m using Stripe Elements (card number/expiry/CVC) inside the Elements provider, plus a GSAP animation that adapts based on screen size. Payment details are optional, but if users add a card, it’ll make future purchases smoother and still secure because Stripe stores it on file.