Home / Companies / Clerk / Blog / Post Details
Content Deep Dive

Refactoring our frontend API key: Familiar DX is the best DX

Blog post from Clerk

Post Details
Company
Date Published
Author
Colin Sidoti
Word Count
536
Company Posts That Month
6
Language
English
Hacker News Points
-
Post removed?
No
Summary

Clerk initially used a hostname as a frontend key for their SDK to optimize performance, which confused developers due to its unfamiliarity. Despite the performance benefits, this approach led to frequent developer misunderstandings, prompting Clerk to adopt a more conventional key format similar to those used by other companies like Stripe. By base64-encoding the original hostname key and adding a stop character, Clerk created a new publishable key that maintains performance while improving the developer experience. This change has resulted in smoother integration and setup for developers without sacrificing the efficiency of their authentication API.

Trends Found in this Post
Trend Post Mentions Total Month Mentions Posts Companies MoM
Developer Experience 3 163 95 56 -14%
Vector Search 1 307 67 38 +12%
Use This Data

Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.