App Builder

Overall: As a business analyst, my main aim is to make sure that clients and developers share a common understanding of the requirements and functionalities. Indigo Studio has been an invaluable tool to define and refine requirements and interactions with stakeholders and communicate these requirements to the development team. I started using Indigo Design while it was still on beta at a previous job and had a great experience with it. When I got the chance to select a prototyping tool at my new job, I chose Indigo Design, knowing it would allow to quickly and easily create prototypes and be easy to learn for future team members regardless of their technical or design background.

Pros: - Easily create interactions: Indigo's greatest strength is indubitably the ease with which it allows to simulate interactions. You can create simple interactions by creating states triggered by events in just a few minutes without having to be an expert UX/UI designer or a developer. - Easy to share with stakeholders and team: The link sharing capabilities allow stakeholders and team members to access the prototype, interact with it and comment. - Easily reuse elements with screenparts: Screenparts allow to define elements once and reuse them throughout the project whenever applicable instead of having to redo the element over and over. - Useful icon library: The icon library allows to better illustrate some concepts as well as to add some style to prototypes without having to look for images.

Cons: - No versioning capabilities: There is no direct way to save a version of the published prototypes and be able to share a working version with other people as functionalities and tweaks are added by a stakeholder while the development team is working on the previously defined scope. - Collaboration functionalities: the collaboration functionalities are essentially limited to publishing and downloading, meaning everyone is using a copy of prototypes and "screenparts" instead of having a common base. It would be great to be able to build a library of reference elements shared with a team. - Limited text formatting options: This is a less critical issue but being able to format table cells would allow to show that some elements are hyperlinks for instance.

Alternatives Considered: diagrams.net and Visio

Reasons for Choosing App Builder: The ability to easily create interactive prototypes.

Overall: It makes working with clients and developers much easier and makes us look a lot more professional.

Pros: Integration with Sketch makes it easy to share wireframes and prototypes with clients and for developers to get the specific information they need to build the UI.

Cons: I love the code generation concept. However, it is limited in what it can code. Some of the features we want to use (basically aspects that adjust the screen in some ways like a side navigation bar and accordion) are not supported. Would love to see them expand the list of supported components.

Alternatives Considered: Sketch and UXPin

Reasons for Choosing App Builder: We were already using Infragistics' Ignite UI for Angular, so it was a natural fit.