Bringing Dropbox’s Frontend Engineers Together

Dropbox recently hosted its first JS Guild Summit at its San Francisco headquarters, gathering frontend engineers from offices in San Francisco, Seattle, New York, and Tel Aviv. The two-day event was designed to break down silos between teams and encourage the free exchange of ideas across the company’s four engineering hubs.

The JS Guild itself is a grassroots group focused on improving frontend engineering at Dropbox through community, culture, and code quality. Over the past year, the guild has driven foundational changes such as the large-scale migration from Underscore to Lodash and initial work on moving from Flux to Redux. The group also publishes a biweekly newsletter written by rotating engineers, covering frontend best practices and recent projects.

A Conference Built Around Knowledge Sharing

The summit brought together 115 frontend engineers for two days of talks, workshops, and open discussions. The goal was straightforward: promote knowledge transfer, highlight the variety of frontend work happening across offices, and identify opportunities for deeper collaboration.

Attendees presented on a wide range of topics, including:

  • The merits of React
  • The intricacies of the JavaScript event loop
  • Building accessible and inclusive web components
  • Unicode and emoji handling

The organizers accepted proposals from engineers with varying levels of speaking experience, and while a talk by VP of Design Nicholas Jitkoff drew a large audience, several presenters delivered their first-ever technical talks at the event. The summit also included an unconference, where more than 50 engineers led sessions on subjects like the future of automated UI testing, expanding Dropbox’s open-source presence, the Dropbox Chooser component, web accessibility, and the internal UI component library.

Office Highlights: Hot Reloading

David Goldstein from the San Francisco Web Platform team used the summit to demystify hot reloading, a utility central to many frontend workflows. Hot reloading lets the browser apply code changes without a full page refresh, preserving state and speeding up iteration. Goldstein explained how his team made their implementation compatible with RequireJS and discussed which components of a React/Redux application can be hot reloaded, emphasizing that the technique’s feasibility is tied closely to frontend architecture.

Office Highlights: Rondo and Redux in Practice

Assaf Kamil, an engineer from Tel Aviv working on tools for Dropbox Business admins, ran a workshop on Rondo, a framework that tightly integrates reusable business behaviors with Redux. Rondo provides an interface for encapsulating the actions, state management, and side effects needed to support a business flow. Kamil demonstrated how Rondo has sped up his team’s development and offered practical training for other engineers.

Staff Software Engineer Josh Zana from Seattle, an early contributor to the Redux migration, shared lessons from his team’s transformation of legacy Flux stores. That migration originated in a Web Enhancement Proposal and was intended to create a standard repository for shared UI data, reduce technical debt, and improve test coverage. Zana’s team has migrated about 80% of their legacy Flux logic to Redux. His advice included planning thoroughly before starting, breaking work into manageable tasks, parallelizing across team members, testing every reducer in isolation, and experimenting with both Redux Thunks and Sagas to see which fits the use case.

Office Highlights: Rapid Prototyping

Mike Lyons, a software engineer and tech lead in New York, discussed how rapid prototyping contributed to the launch of Dropbox Showcase. His team accepted tradeoffs to get the product to market faster, but found that the approach reduced the cost and frequency of missteps by anchoring development to real-world use and customer feedback.

Strengthening Connections After the Summit

Since the summit, engineers have noted that meeting in person made it easier to collaborate with colleagues they previously knew only through chat. One attendee said the most valuable takeaways came from hearing other teams present problems similar to their own, offering insight into how they might implement analogous solutions at home. The summit served its purpose: sharing knowledge, breaking down silos across offices, and investing in the frontend engineering community.