Have you noticed something different about Iconfinder in the last few weeks? No? You weren’t supposed to. But, in fact, everything, other than what you as a user actually see, has changed. In the last month almost half of the code base running Iconfinder has been swapped out for a completely new structure in what is arguably the biggest refactor we’ve done since we switched to a brand new code base in late 2012. Continue reading
On the modern web, we almost take a well designed RESTful JSON-based API for granted. But what actually goes into designing a good API? Is it really just one simple formula or are all APIs not created equal? Following is some of the thoughts and considerations we went thru, designing the new Iconfinder API.
Grunticon is good alternative to icon fonts. It uses SVG files and embeds them in a CSS file that makes it super useful for web project. It’s a bit tricky to set up, so we created this guide to help you get started.
As you might have noticed, we rolled out a new notification system a couple of weeks ago. I’m not going to write about its interface, but rather one of it’s cool backend feature: auto-discovery of notification modules and self-registering of notification classes. What do I mean by that? Well, lets take a practical example.
In the last five years, the focus in front end web development in general has shifted from a world of “making it work” to “making it fast.” One way of speeding up the front end and optimise load times is asset compressing using Base64 encoding. But as with all tips and tricks, there are both up- and downsides.
A while back I gave a general talk about how we decided to pull the plug and move Iconfinder to Django. One of the parts of the presentation, which got the most attention, was about how we reduced the page generation time for an average search from 91 to 20 milliseconds without fiddling with our caching layer, database or search engine. By popular demand, I thought it was worth walking you through exactly what we did. Continue reading