June 2021 Summaries

The modern web prioritizes speed, a trend highlighted by Vercel's launch of Next.js 11 with a focus on Google's Core Web Vitals, which influence search rankings. Clerk, however, emphasizes the often-overlooked speed of user sign-ins, discovering that Social Sign In options, initially placed below email sign-ins, should take precedence due to being faster by an average of three seconds. This change resulted in a shift where Social Sign In began to outpace traditional email and password methods. Despite the growing interest in making passwordless flows a primary option, Clerk recommends keeping them as a fallback due to their slower average completion time of 35 seconds. Clerk also addresses the common yet underestimated "edge cases" of Social Sign In, ensuring seamless user experiences regardless of sign-in method, which often involves users switching methods over time. Clerk's prebuilt Sign In UI offers developers a way to integrate customizable and efficient sign-in forms into their applications, aligning seamlessly with company branding while continuously seeking to enhance user experiences through data analysis and technological advancements.

User management systems are essential for consumer-facing applications, responsible for creating, managing, and removing users, and enabling authentication while allowing administrators to manage users effectively. Applications can either build their user management system in-house or use solutions from third-party vendors, but the decision depends on specific needs, resources, and priorities. In-house development offers customization and control but requires significant expertise, time, and resources, which can divert focus from core business operations. Conversely, buying a user management system is often quicker and more cost-effective, providing scalability, security, and technical support, though it might limit customization and control over the data. The system must offer features like authentication, user profile management, session management, and integration capabilities, alongside a user-friendly interface, to ensure both security and a seamless user experience. Ultimately, the choice between building or buying hinges on the application's requirements, budget, available expertise, and long-term strategic goals.

At Clerk, the use of End To End (E2E) testing has become essential for creating reliable authentication flows across different browsers, addressing the growing need for effective validation in agile development cycles. Initially a domain of Quality Assurance Engineering, E2E testing has gained popularity among software engineers due to the rise of tools like Cypress and Playwright, the latter of which Clerk selected for its flexibility and robust community support. Playwright's ability to seamlessly execute workflows across multiple browsers, combined with its stellar documentation, made it the platform of choice for Clerk’s E2E suite, which is designed as a separate Node.js application written in TypeScript. The suite incorporates components like Jest for test running and Faker.js for API fixtures, promoting ease of use and quick onboarding for new team members. Integration with GitHub Actions ensures that all tests run successfully before any production merges, safeguarding against accidental regressions. Clerk’s decision to open-source a template for E2E testing with Playwright underscores their commitment to sharing knowledge and advancing the field.