so many features missing to be considered Canva-like, hopefully it can evolve into fitting that description but now I think it is a stretch and a little misleading to make the comparison.
The Studio tool appears to be a showcase for their paid graphic library (https://polotno.dev/). As a designer/dev the library is definitely addressing a hole in the market where libraries like fabric.js and konva aren’t serving: customer support (esp enterprise) and feature requests.
Coming from Teespring and recently at Figma, I’ve seen both sides of this problem: home rolling a teeshirt maker in canvas and also trying to use parts of an editor at Figma for marketing (wasn’t decoupled enough). I’m excited to see where this team takes this and grows.
From my view, the hole in the market is not customer support and features requests. Fabric.js and konva (that is used inside Polotno) are "low-level" libraries. They are providing a DOM-like API to the canvas. That is it. In order to make a full canvas editor, you have to write a lot of code on top of fabric, or konva, or any other library, or SVG.
https://polotno.dev/ - is designed to solve a very narrow business need. So you can build a full editor with much less code (almost no code at all). It may be less flexible, but it is the tradeoff for solving one problem in a good way.
Potentially a bug that I found. When I add an icon and click "Flip Horizontally" or "Flip Vertically", the icon appears very blurry and a little pixilated.
Very nice. However, it took a moment to realise that you cannot drag objects to the canvas but have to click on them first. Then you can move them around.
34 comments
[ 3.7 ms ] story [ 85.1 ms ] threadComing from Teespring and recently at Figma, I’ve seen both sides of this problem: home rolling a teeshirt maker in canvas and also trying to use parts of an editor at Figma for marketing (wasn’t decoupled enough). I’m excited to see where this team takes this and grows.
Thanks for the kind words.
From my view, the hole in the market is not customer support and features requests. Fabric.js and konva (that is used inside Polotno) are "low-level" libraries. They are providing a DOM-like API to the canvas. That is it. In order to make a full canvas editor, you have to write a lot of code on top of fabric, or konva, or any other library, or SVG.
https://polotno.dev/ - is designed to solve a very narrow business need. So you can build a full editor with much less code (almost no code at all). It may be less flexible, but it is the tradeoff for solving one problem in a good way.
> Fof non-commercial or development usage only
Consider (down the dev road) export options that optimize the image, like https://tinypng.com/ (I have no affiliation w/ them, other than as a user).
error -> pdf export doesn't work as intented when canvas size changed. scales page elements to fit predefined (I think) page size.
Using Firefox on Manjaro.
One thing I found myself needing: Is there a way to manage the z-index of your layers? (e.g. send layer to back, etc)