Silk relies heavily on web APIs, like Scroll snap and WAAPI. While building it, I also took care to anticipate new ones, like the Scroll-driven animations API.
For each feature, I reviewed and experimented with the existing APIs to see how well they fit. I also had a look at upcoming ones, and sometimes took part in the conversation to try and improve them before they shippedālike I just did with the interactivity CSS property.
Every time, I tried several solutions, sometimes deciding to go with web APIs, sometimes holding off because I realised they were not yet ready, like <dialog>. I considered performance, accessibility and flexibility to arrive at a solution that enabled the use cases I wanted Silk to cover.
Silk isnāt just about appearanceāit's unstyled by default. Its design is the result a lot of thoughtful work and experience with the web, aiming to be flexible, robust, and long-lasting. As new web APIs become viable, Silk will continue to evolve to make the most of them.