Useful link: http://balsamiq.com/products/mockups/plugins/ :)

What is the use case here? There are two things off the top of my head:

• It is easy to export and add Balsamiq Mocks to Pholio Mocks (I do think now)
• Or extend Maniphest with Custom Fields linking to your web-based Balsamiq mock

Besides those two, I don't know what else we'd add. It seems to cover all cases.

@chad: Mockup are XML based files interpreted by balsamiq software as images. Besides possibility of saving mockups as image in Pholio Mocks, Phabricator should also store this XMLs, to be able edit those mocks, and save them again in Pholio Mocks as new version. Paste application can be used for that.

I created few mockups showing how this can be done :)

M88 Balsamiq integration

61

What problem are we solving by building a Balsamiq editor? Why would you want to edit it in Phabricator instead of their webapp or desktop application?

In a general sense, we never build deep integrations. They are significant to build and support in the upstream and we have a very small team. See T4778: When will my feature get built, or my bug get fixed? for specifics.

What problem are we solving by building a Balsamiq editor?

Nobody wants to build a new balsamiq editor!

Why would you want to edit it in Phabricator instead of their webapp or desktop application?

First of all, I believe a typical user don't want to install anything, so that's way desktop application is worse than webapp.

As far as I know, http://webdemo.balsamiq.com/ cannot store mockups/images... and even if it does, I want to keep everything in one place - in phabricator. Of course, now I can do this manualy:

1. create mockup in webapp
2. export image
3. upload image to Pholio Mocks to get review and feedback from team members
4. export XML balsamiq file
5. create a Paste from XML to have possibility of editing in the future
6. Link somehow created Pholio Mock with created Paste with xml

and if I will need to create new version of mockup, because my team member suggest me a great idea, a would have to:

7. Find a proper Paste with exported XML
8. upload this XML to balsamiq webapp
9. edit mockup
10. export new version of image
11. find created pholio mock, and update it
12. export new updated version of xml
13. create new Paste
14. update link to XML in pholio description.

Integration with balsamiq can simplify this process. Saving XML file can be done under the hood, user would not have to know or remember about that.

M88 mockups presents whole "user story" with balsamiq web editor in the middle. I wanted present, that it can be integrated in that way, that balsamiq webeditor can save image and XML directly to Phabricator. Exactly in this same way as Balsamiq and JIRA: https://www.youtube.com/watch?v=nLNdx9kI7OM

Balsamiq plugin for JIRA is quite popular:

I believe, that with great Pholio Mocks and inline comments, Phabricator can be popular even more :)

In a general sense, we never build deep integrations. They are significant to build and support in the upstream and we have a very small team

I don't know details of your code (I am a Python programmer, so I can help you :( ), but I think this integration can be pretty easy. I believe everything what Phabricator needs to do is to make a request to proper address of balsamiq server, with additionall parameters

and have possibility of receiving produced image and xml by request from balsamiq server. I am sure, that guys from Balsamiq will happily describe how this can be done in the easiest way :)