Balsamiq Dev Update for August 2018
Happy August, friends of Balsamiq!
As cliche as it sounds, I'm really excited to tell you what we have been up to development-wise this month. We had two really cool releases!
First, on the Balsamiq Cloud front, we released one of our most requested features, Project History.
When we launched Balsamiq Cloud last September, we still weren't sure how to best implement project history. We knew we wanted to do it (because it was something our myBalsamiq customers got a lot of use out of) but we still had to figure out how to make it awesome in Cloud. We're really happy we can finally share it with you. You can read more about how Project History works in our documentation.
In addition to Project History, we fixed a lot of bugs in both Balsamiq Cloud and the Balsamiq Wireframes editor. We have another big cool feature coming soon - stay tuned for that!
The other (and completely unexpected) release this month was an update to Mockups 3 for Desktop. We are heads-down on building Balsamiq Wireframes for Desktop, so Mockups 3 for Desktop hasn't gotten a lot of attention recently (if it ain't broke, don't fix it). However, when a user named Tristan let us know they had found a fix for one of our longest standing bugs, we immediately started working on a release. I cannot tell you how long this crash bug has plagued Mockups 3 for Desktop - it's in the top 5 for the most reported bug - and we are just so happy to have it fixed. A big thanks to Tristan for helping us finally fix this bug. You can download the updated version (3.5.16) now. 😉
Besides that, we are getting ever closer to our beta releases of Balsamiq Wireframes for Desktop (our forthcoming native desktop applications). We should have more on that soon...
Until next month, friends. Happy Wireframing!
Brendan for the Balsamiq Team
Comments (2)
Hey there great to be looking at Balsamiq again! Question: I am working in an environment where we have to keep track of project, project screens, project screen tab names and data fields … the issue is we have is the names and positions frequently change as we gather the user requirements. We then need to update developers (to do list) they need to make a change (name or location) and all the requirements documents with the changes. I realize besides needing a nice wireframe this would require a database to keep track of the changes and updates and workflow reporting to dynamically generate the user requirements and testing documentation. Any suggestions?
Hi Bert and thanks for getting in touch!
Since our tool is more of a low-fidelity wireframing tool, those specific needs might be hard to fulfill in the app. Symbols will help you to replicate changes in multiple wireframes but those will be hard to track. Another option you might want to look at for keeping different versions of a wireframe is the Alternates feature.
In case you’d like more information about our tool and how it compares to other ones, you might want to take a look at this page.
Hope this helps! Don’t hesitate to reach out via support@balsamiq.com if you have more questions. 🙂