

AVOCODE MIT DOWNLOAD
When you opened the design file on the client, Avocode would download the Octopus file (JSON object), bitmaps from the design, and also a rendered preview of the design.Īll of it needed to happen before you could start inspecting layers.We parsed its data structure and translated it to our universal design format Octopus so we could render it on any platform.Your design file was uploaded to the server.Until the 3.7 update, this is what would happen with every design you imported to Avocode: After we hit 99% design rendering precision across a sample of thousands of design files, we started to look more into a smooth zooming and rendering performance.

Our priority when building the rendering engine was precision. This brought in a wave of designers, stakeholders and agency clients who care very much about how crisp the design looks. However, this changed rapidly as Avocode has become more of a design file hub for teams, where you can not only inspect, but also store files with version history and discuss design feedback.

As long as the exported assets were rendered correctly, the design preview didn’t have to be crystal sharp after going over 100% zoom. In the beginning, Avocode was a developer-first tool that would help you inspect the design - get specs, code, and assets. When you zoomed in on a design file, it would become pixelated, since we have rendered the design only at 100% at 1x. Up until now, the design canvas in Avocode behaved similarly to the bitmap image editors like Photoshop. The new Avocode is finally powered by design processing and rendering that happens locally in the app and the reworked Monroe rendering engine that works like other vector-based design tools such as Sketch, Figma or Adobe XD.
AVOCODE MIT UPDATE
With that in mind, it’s our great pleasure to introduce you to Avocode 3.7 - an update that has cost us the most time, sweat, and merge requests to date. Would we start such a project again if we could travel back in time? Not sure.😅 Building this machine was quite a challenge. No really, it’s a design parsing technology combined with the Monroe rendering engine, written in C++ and compiled to WebAssembly via Emscripten, so the engine works on the server as well as on the client. Designers and developers work with all kinds of tools on all types of platforms, so a proper design hand-off tool needs to work with all primary design tools (Sketch, Adobe XD, Photoshop, Illustrator and Figma) and on all platforms (macOS, Windows, Linux, and the web).
