Very neat to see this! For the past year, I've been working on a very similar collaborative-design tool in an entirely different field (an aspect of transport p

Very neat to see this! For the past year, I've been working on a very similar collaborative-design tool in an entirely different field (an aspect of transport planning). Probably won't have anything to show until the summer, but it's reassuring to see others pursuing similar business plans, interaction models, etc. Helps to validate my feeling that the cloud and the browser are fundamentally the future of design. My own application provides relatively high-level collaborative design functionality, and does not attempt to replicate the functionality of existing tools that are capable of very low-level simulation, analysis, and engineering. I imagine that it's a similar situation for hardware design, although probably with fewer tiers of software -- presumably Upverter users are working at a level that's much closer to the end result of the hardware-production process. Still, there must be existing (offline) design platforms with low-level functionality that you don't want to replicate in its entirety; these are presumably embedded in the workflows of existing hardware design houses in a way that will be difficult to supplant. Have you considered eventually producing plugins for these 3rd-party platforms, which would keep their designs in sync with the cloud-hosted model? This way, high-level design could be done in the browser, and low-level simulation etc. can be done in existing applications, while still taking advantage of Upverter's collaboration functionality. This, of course, is my own long-range plan, although the web application is very much the initial focus. Just wondering if you've had similar thoughts, and if so, whether you've found such a strategy to have any particular merits or flaws that you'd care to discuss?