Week 57 | QR Code Join and Feature Freeze скачать в хорошем качестве

Week 57 | QR Code Join and Feature Freeze

This week was about scope and guardrails: Apple’s organization account migration paused my iOS publishing pipeline, I implemented RevenueCat billing so Shokken can have real cost boundaries, and I shipped a QR-code “self-join” flow—with the security/cost implications that come with exposing a public join link. 🧪 *Test Shokken:* http://shokken.rsvp 📱 *App Progress* 🔄 Apple developer account migration (iOS publishing temporarily paused) ✅ RevenueCat paywall implemented (billing guardrails before public release) ✅ QR code scan-to-join / self-service waitlist enrollment implemented 🔄 Ongoing bug fixing as testers keep finding new edge cases 🔄 Product website mostly done; screenshots + feature video still pending 🧠 *Highlights* Why “account migration” can block shipping Billing as a safety mechanism (cost control), not just monetization Why QR join is a security and cost design problem ⏱️ *Chapters* 0:00 Week 57 intro + current status 0:23 Why iOS updates are paused (Apple org migration/signing) 2:58 Product website status (screenshots + demo video still needed) 3:47 Feature creep vs. shipping: “freeze the features” 4:12 RevenueCat paywall implementation and why it matters 7:52 QR code scan-to-join: competitor research + implementation 9:49 Threat model: denial-of-service and cost-amplification risk 11:54 Defense-in-depth approach (keep it low friction, harder to abuse) 13:52 The promise: no more features for the initial release 14:19 Summary + next steps 🔗 *Resources* Blog Post: https://endian.dev/blog/2026/57/ Testing Resources: http://shokken.rsvp Project Site: https://endian.dev GitHub: https://github.com/endian-dev #Shokken #KotlinMultiplatform #RevenueCat #SMS #Security