The main differentiator and focus of the post is &quot;we&#x27;re making this run in the browser&quot;. But nowhere does it explain <i>why</i> that&#x27;s better for designers. You don&#x27;t need it to power collaboration features.<p>This echoes Asana and a lot of the &quot;HTML native&quot; product efforts. Which have mostly failed as a technical approach and resulted in a return to platform native apps.[1] What&#x27;s different this time?<p>Meanwhile this prompts amazed reactions from folks who are technically impressed with how far it pushes the browser. But that was the case with prior HTML native efforts too. It distracts from a critique of the actual product features.<p>I&#x27;d like to see a more head to head comparison with popular tools like Sketch. Maybe the built in team collaboration is better than, say, a companion app like Zeplin. But the implementation details don&#x27;t really matter to customers.<p>[1] <a href="https:&#x2F;&#x2F;blog.asana.com&#x2F;2014&#x2F;07&#x2F;mobile-plans&#x2F;" rel="nofollow">https:&#x2F;&#x2F;blog.asana.com&#x2F;2014&#x2F;07&#x2F;mobile-plans&#x2F;</a>