The community was part of the product
I wrote about Sketch in a November 7, 2020 First 1000 issue as a shortened adaptation of Sketch’s own ten-year account. That distinction matters: the historical company details come from Sketch’s blog material, not from a new interview or my own product use.
The account says the early team was small and collaborative, with design and development lines deliberately blurred. As people adopted the Mac app, they shared icon sets, interface kits, plugins, tutorials, meetups, and integrations.
The community did not just promote Sketch. It expanded what the product could do and gave the team a stream of detailed feedback.
Say no without leaving users stranded
The team’s challenge was feature pressure. Users asked for more, but Sketch did not want every request to become core product work. The source describes a boundary: build the common product, while extensions cover the last mile for particular workflows.
That is a better version of “listen to customers.” Listening does not mean building every requested feature. It means understanding whether the request points to a universal problem, a missing extension point, or a workflow the product should intentionally leave to someone else.
A plugin is not a way to ignore users. It is a promise that the product will make the edge possible.
Open the surface that others can extend
The source highlights Sketch’s open file format and plugin architecture. Developers could build tools around files they owned, and a close group formed around the Sketch-plugins mailing list when public documentation was thin.
The account names early meetups in San Francisco, Paris, Mexico City, and Beijing, along with resources built by designers and developers from individual creators to large product teams. The point is the ecosystem mechanism, not a claim about every contributor.
An open format also changes the relationship with developers. They can build around the product without waiting for the core team to approve every idea. That creates useful competition at the edge while the core team keeps a smaller surface coherent.
The ecosystem boundary
If I were deciding whether to build a feature or open an extension point, I would ask:
- Which workflows are universal enough to belong in the core product?
- Which requests are valuable but specific enough for an extension?
- Can users move their data out in a format they control?
- What documentation, events, and examples would let the first plugin author succeed?
- How will you avoid copying a healthy extension without giving users a better native path?
The takeaway
Sketch’s community was not a marketing layer attached to the product. The open format, plugin architecture, meetups, and feedback loop made the edges useful while the core team stayed focused.
Sources and original research
Adapted from Sketch, published November 7, 2020. The issue identifies itself as a trimmed version of Sketch’s ten-year company blog account; the collaboration, community, open-file-format and plugin claims come from that historical material. No current Sketch metrics or personal product trial is claimed.
Updated September 21, 2026. Based on original First 1000 reporting and the sources listed above.