
How BugSmash automates website screenshot rendering
How and why BugSmash uses ScreenshotOne for critical screenshot rendering tasks.
- Written by
- Nabil Kazi, Dmytro Krasun
- Published on
Dmytro Krasun
With more than a decade of experience in software engineering, I share the best practices and solutions you can apply to your problems in the space of headless browsers. You can also find me on Twitter and LinkedIn
How and why BugSmash uses ScreenshotOne for critical screenshot rendering tasks.
Check out how to use the external identifier to improve tracking of webhook executions.
Check out how to get notified about rendering errors when using webhooks.
We added support of Slack notifications to ScreenshotOne. Now you can set up and get Slack notifications when you reach your quota limits.
We improve UI/UX of rendering numbers in the dashboard for better readability.
We added more algorithms for screenshots by selectors.
It is a good milestone to make a compact snapshot of the insights that (maybe?) led to it.
Improved code examples in the playground and added all official supported ScreenshotOne SDKs.
We updated the design of the authentication pages to make them more user-friendly and consistent.
Learn how to render screenshots with different emoji styles in Puppeteer using emoji-js in a few lines of code.
OpenAI 4o image generation is a really good model that can change the way you automate marketing
How and why "Magic Pages" used ScreenshotOne to showcase how their customers use their product.
Exhaustive documentation, ready SDKs, no-code tools, and other automation to help you render website screenshots and outsource all the boring work related to that to us.