Hi balsamiq dev team,
after the balsamiq cloud access is now gone from the desktop app, our team was forced to move to the web version.
Besides that everytime when opening a project we now have to annoyingly keep the loading tab and window active, otherwise the project will never load (because throttling the background processes is a standard browser behaviour), we now also receive the following rendering bugs:
The video was blurred due to legal reasons, in case you would like access to the unblurred version to analyse the behaviour, feel free to contact us directly.
The bug occurs when a group of elements is double-clicked and the screen view changes (zooming, panning but also on simple mouse movement).
System: MacBook Pro 15-Inch 2019
macOS: latest Ventura 13.2.1
Browser: latest Chrome Version 111.0.5563.64 (Official Build) (x86_64)
Screen: LG UltraFine 5120 x 2880 (recommended and sold by Apple)
We have more than 130 projects in your cloud and use your software every day, but we did not experience this problem previously in the desktop app.
The rendering errors occur, fortunately less often, but also when using balsamiq on the laptop screen (smaller resolution 2880 x 1800)
Oof, that’s brutal, @matejrajtar.
I can honestly say I have never seen that - and have multiple folks who are running into this?
Let’s try a couple of things, just to rule out the easy things.
Can you log into Balsamiq Cloud in an Incognito Window? If the problem persists there, can you try using Safari?
I have a 2021 MBP with that exact monitor, and I’ve never seen that happen. Is the LG a true second screen? Or is the laptop in clamshell mode, with the monitor being the primary (and only) display?
I’m sorry again for the trouble here. We will do everything we can to get it sorted.
Thanks for the quick reply. Chrome only, Safari shows no problems (apart from an extreme laggy zoom, during which the canvas elements sometimes disappear, which we got already used to also on the desktop version).
The incognito mode in Chrome unfortunately does not help, the symptoms including the green areas flickering back and forth are still there.
The MacBooks are used both modes in our team, clamshell and also true second screen, the videos were recorded while always both screens running.
Thanks for the update, Matej.
Unfortunately, this looks like a bug that Apple and Google have been fighting over since 2015. It has to do with the AMD chip in those Macbooks.
Let’s try this:
chrome://settings/system in the browser
Use hardware acceleration when available.
That’s the easiest fix. If that doesn’t work, we will try the next thing.
This indeed solved the issue for us, thanks @Brendan! With the acceleration off we noticed a further drop in performance in terms of how responsive (or unresponsive?) the interface is, especially with many elements on the canvas. However, there are no visual bugs appearing anymore.
Do you also experience a delay in terms of seconds when doing any action, e.g. moving an element on the canvas using keyboard arrows or virtually anything else? This has been the case for us already on the desktop version, but now in browser with the hardware acceleration off it has gotten worse.
Is the balsamiq team working on improving the performance to level with the tools such as Miro, Overflow or Whimsical? Can we expect an update for this in the future?
Thanks a lot,
We are constantly working on improving performance, @matejrajtar (in fact, this month’s release had a performance tweak in it). Of course, there is always more work to be done. We think some changes we are making over the next few months to trim things down will help.
The fewer things the app has the draw, the better.
I’m curious as to how the app runs in Firefox and/or a Chrome incognito window. There have been situations where certain extensions have caused the app to run slowly.
@Brendan Thanks for the tip, will try to work in the incognito window without the extensions as well.
I believe in our case it is the amount of elements we need in our wireframes (labels, icons, etc.) although that should definitely not be the reason with the current technologies and computing power available.
Looking forward to the updates in the coming months.