We are happy to announce that Pixo now fully supports the WebP image format, both in the Image Editor and the REST Editing API. You can now send a webp image to Pixo Editor or the REST Editing API and get the final result again in webp or any other supported output format (png or jpeg).
According to caniuse.com all modern browsers support webp format nowadays. Although older versions of Microsoft Edge browser does not support it, our usage statistics for the past 3 months show that none of our users use the non-Chromium Edge anymore. So using webp format should be safe.
We haven’t posted anything for a very long time. This does not mean that we did nothing, though 😉 There are plenty of new APIs & features that we implemented and released since the beginning of 2022. Here are the most interesting ones.
Although Pixo Editor does not provide native SDK for iOS, Android, or Flutter, it can be easily integrated into a native application, thanks to the WebView component, supported by both platforms. All you need is an embedded HTML page that integrates Pixo, a WebView instance rendering that HTML page, and a communication controller. Here is the flow:
Any Image is converted to base64 string
The WebView component renders a static HTML page that integrates Pixo
The static HTML page gets the base64 string and opens it in Pixo
A watermark is a logo, a piece of text or signature imposed onto an image. Watermarks are typically transparent, so those viewing the image can still admire it. Watermarking images can also protect the copyright – ensuring others don’t use the image without the owner’s permission.
With this example you’ll learn how to impose watermarks on end-user’s images – a simple text. You can also insert custom sticker images as watermarks.
Everything you need to do is to:
Overwrite the default Save action, in order to insert the watermark when the end-user clicks “Save”, using the Custom Actions API;
To insert the text watermark before saving the image, using the Text Editing API.
Our Editing API is finally out now! With it, you can manipulate images server-side. It supports most of the features of the Editor, and guarantees you the exact same result as if the image was edited in Pixo Editor.
This project was the biggest one for this year. We are very happy that we managed to release it, even though in the very last day of 2021. The past two years were extremely hard for all of us. Let’s hope that 2022 will be a much better one. We will continue our work on exciting new features. Stay healthy, and have a happy New 2022!
We’re extremely happy to announce a new feature we’ve been working on for quite so long! Let us present to you our new exciting end-user tool – Background!
Removing background of images using machine learning (ML) is very popular these days. Our brand new Background tool does exactly this. But that’s not all! End users can not only remove the background of photos, but also can replace it with a solid color, or with another background image. They can browse a rich stock image collection (powered by Unsplash) as well as to upload their custom image to be used as a background of the edited photo.
Removing the background
Background removing is possible thanks to ML. This is expensive operation and takes some time, usually a couple of seconds. During this time end users see a progress message.
Is it a Premium feature?
Yes. The Background tool is a Premium feature, which means that it is available in all paid subscriptions as well as during trial period. FREE accounts do not have access to this tool.
Will it cost extra?
At the moment of the release – no. However, down the road we may decide to make this feature cost extra, one way or another – either apply some pay-per-use, or create extra subscription plans on top of the current ones.
Will I get extra charged without notice?
Definitely not! If we ever decide to make the Background tool cost extra, you will have the choice to upgrade your subscription and start using it, or to keep your current plan and not use the Background tool respectfully.
We wish you a Merry Christmas…
…and a Happy New Year! As usual, our Christmas Stickers pack is now available to end users.
After the announcement that we dropped support of Internet Explorer, we did a code clean-up, removing all polyfills and compatibility code blocks. As a result, our integration file bridge.m.js (the one that you include in your web pages) got reduced with 21%, and the script resources that are loaded when the Editor is opened got reduced with 10.5%.
Also, we noticed from our logs that some customers were experiencing huge load delays. Sometimes the Editor took 5+ seconds to load. We investigated the delay, did some server optimizations, and now every customer should open the Editor in less than a second.
We are monitoring performance constantly, and we constantly work to make Pixo blazingly fast, for better user experience.
Although Pixo Editor does not provide native SDK for iOS, it can be easily integrated into a native application, thanks to the WKWebView component. All you need is an embedded HTML page that integrates Pixo, a WKWebView instance rendering that HTML page, and a communication controller. Here is the flow:
Any UIImage is converted to base64 string
The WKWebView component renders a static HTML page that integrates Pixo
The static HTML page gets the base64 string and opens it in Pixo
The onSave callback of the Pixo.Bridge instance sends back the edited image as base64 string as a WKScriptMessage
We’re really happy to announce the official release of our most wanted and long awaited Editing API! It is available right now!
You can check our Editing API docs and see what can be done via this API. Basically it allows you to programmatically manipulate Pixo Editor and the image. You can define settings in each Feature’s Property Panel; or you can manipulate the image, by inserting stickers, text, or applying a filter, shape or frame.
The magic happens thanks to the new exec method of Pixo.Bridge.
You can check the API docs, or you may have a look at this example in order to see the new Editing API in action. In the example you will see Pixo Editor with hidden internal controls (Actions Menu, Edit Menu, Property Panel); instead, the end user is able to draw on the image and crop it from external controls that live in your application!
The Editing API is something that will be constantly extended with new cool API commands. Stay tuned for updates!