I think this will be a mute point as there is a major release waiting for myBalsamiq. Just in case someone else stumbles upon this until then (or if the Balsamiq dev team want to keep an eye on this on the next release)
We made the mistake of using site-assets for our first major implementation. Now, 50 odd detailed mockups later using the same Symbols from the Site Assets over and over again… our clients can’t view it.
What I mean is, they can see the mockups but all symbols that came from Site Assets are error symbols saying the symbol can’t be found.
It’s quite a nuisance. For now, I think we can make our clients “Staff” members and they will be able to see it. However, I am a paranoid person around security, have done a lot of role based stuff and whether there is a functional difference or not, I just can’t put a non-staff person into a “Staff” category. So I sought a work around.
Copying and pasting the symbols to the project assets does not work.
I even went as far as doing the following (there might be easier ways):
- Download the zip of the project you want to share
- Change the name of the zip
- Extract the zip file into a folder
- Download the site assets you want to share
- Copy them into the asset folder of the project folder you just created
- Use Notepad++ to open up one of the BMML files
- Do a “Find in Files” and find
and replace with
also choosing “Follow current doc.” but don’t select “In all sub-folders”. Then click “Replace in Files”
- Zip up all the files in the folder and give it a name that you want the new project to take (no spaces)
- Upload the zip file as a new mock up
If you give it a try, make sure you take backups and, well, I can’t guarantee this will work an it might break things. It worked for me.
As an aside, I think the balsamiq people have done an outstanding job keeping things simple. I think about 5% more in features will give it 100% more flexible usage, and in my opinion, that’s all that is needed (apart from the obvious refresh and catching up to the desktop version).
At the end of the day, we chose it because it is so simple. If that simplicity causes a few headaches and lessons learned like this one, then it’s worth it.