We agree that an Android pack would be very handy. Sorry about the wait. As you all know we are constantly working on and release new features in each of our updates.
We want to allow anyone to create screenpart libraries and to share with the Indigo Studio user community. While each of you can create a custom screenpart library today (for Android or other), our intention is to create a space where you can simply search and download screenpart libraries. As in, if one you creates a library, others can benefit from it. This does not mean that we won't offer a native pack.
As part of this effort, we are also introducing search in the screenparts toolbox and surfacing screenparts inside the alt+click search suggestions. In the near future, you will find features to help you manage screenparts within a project and also use a common/global screenpart library across projects.
It will be worth the wait!
We feel your urgency, and sorry that we haven't had time to work on this. Partly the issue is that unlike other products in this space, the packs we offer are controls (e.g, drop downs and tabs) and not just stencils. Hence it takes us longer to get it working correctly. We really wish we would work faster, but we are slaying other dragons at the same time. For instance, reusable design elements (screenparts).
However, there is an area where y'all can help us. Is there a good Android UI library (Kitkat) that you know of?
There is already an idea for iOS (http://indigostudio.uservoice.com/forums/185426-welcome-to-indigo-studio-product-ideas-/suggestions/3393563-add-ios-platform-pack), so I edited this to be specific to Android.
Are you referring to including Agency branding on every page of the output, or is it just the cover sheet?
Assume we provide a “picker” that will let you add PDF cover sheet you have already prepared using whatever tool, and every time you export, Indigo adds this as the first page. Would that suffice?
The PDF export is alphabetical only if there are no interactions present connecting the screens.
If there are navigate-to interactions present, the PDF ToC organizes it by user-flows such that even when you are flipping through that PDF you can experience what the user-flow would be like.
Image showing how table of contents is organized:
Would you care to share some examples that we can consider? We understand the need to brand your work.
About the cover sheet, would you consider creating a coversheet in Indigo as a .screen (or a screenpart) which we can try to add in front of the table of contents? Optionally, you could create the cover sheet as an image in another tool and add it to the screen/screenpart.
Nicholas, you mentioned more granular control over which states are exported in the PDF. About selecting which states get exported, we feel you can already do so by selecting the screens you like to export, and then deselecting states that you wish to skip.
See here: http://indigo.infragistics.com/help/exporting-your-designs.html
Were you looking to re-order them manually or alphabetically?
we agree that this behavior should be available for any element, and not just something that is used as a header.
We added support for triggering interactions based on changes to the text input. Check it out in the latest version of Indigo Studio. You should see an in-app update mid next week.
Check the following blog post to see a summary of what’s new: http://goo.gl/ymMWNT
Yup. It's been a year. Gosh!
We kind of understand the ideas as you have stated them. Thank you for listing them out clearly. In the list you mention, is there anything that's more important than others? We are about to start on conditional rules. Will keep y'all posted on this thread.
Also, I don't want to misunderstand your expectations of data-persistence. Can you point me to some prototyping scenarios that we can use as a reference?
If you are interested in seeing what's been happening with Indigo Studio the past year, check out our release notes:
Thanks, Anonymous. I totally agree--for more app like prototypes, having some amount of conditional control (and some amount of data persistence) is important. We'll get there in time. :)
Looking ahead, we have some plans around sharing storyboards on the web, like you do screens. And be able to present a storyboard. Would you prefer this over exporting storyboards to PNG?
Yes. Every project folder should contain a single (dot) proj file. If you want to organize the screens you create into folders inside that project, with update 5 you can do that. Create new sub-folders in the project tree and add screens into it.
The model we have in place is to have a folder per project. If you want to duplicate screens to use across projects, you can use presently do it outside of Indigo in the file folder structure.
myProject 1 folder
* myProject 1. proj
* Product Details.screen
myProject 2 Folder
* Home.screen <---- copied and pasted this from the other project
* Product Details.screen <---- copied and pasted this from the other project
The only caveat is that you will need to create and save myProject2 with a blank screen so that Indigo can create the myProject2 folder for you.
Hope that helps. We will look into improving this process and making it easier. Thanks for your suggestion!
This sounds like maybe you set up a project in your root projects folder? Can you look there for a .proj file?
Thank you for mentioning this. Can you point us to an example which is requires improvement? We are revamping the help doc experience very soon. Just wanted to be clear whether you were referring to the content or presentation.
Thanks for the suggestion.
Is there any particular topic that we should improve or are there new topics you would like to suggest. We are in the process of improving help, so your suggestions will be a big help.
Are you referring to storyboards in particular?
I only ask because Indigo Studio allows exporting screens to PDF. Something missing in that feature? It's not available in Indigo Lite (v1).
We have tried to de-clutter a lot. Were you referring to the project tab?
The only "toolbar" we cannot collapse right now is the project tab and open screens tab. Were you referring to those? You can collapse the UI elements panel and timeline.
If this is important to you, please comment with details of what you’d like to see.
We understand that need, Jenni! Just haven't gotten around to doing it coz of all the other great ideas people want us to work on. We may tackle this as an add on to the table/grid control as opposed to the broader story of integrate with my data.
Based on the comments below it seems that getting all the yummy data into the grid is on top of everyone's mind.
We have started working on this—basic extraction of these code assets. If you would like to review/provide feedback on this, please let us know.
If online pattern library is the goal, which can contain snippets of functionality, we may not need to export any HTML. As in, create a searchable/organized repository of UI patterns which are in fact Indigo Prototypes.
We recently introduced a BETA feature as part of update 2 for Indigo Studio (not Lite).
Let us know how that works.
Stefano, that is covered by this idea: http://indigostudio.uservoice.com/forums/185426-welcome-to-indigo-studio-product-ideas-/suggestions/3393549-support-html5-viewer And we are working on both the HTML aspect and the self-host aspect.
Note: We simplified this idea's title/description.
We don't think it is feasible to generate complete apps due to the disconnect between the requirements of a prototype and the requirements of apps, not the least of which is particular dev preferences for how they structure their apps and code. Each dev has a distinct idea of what constitutes quality production code. Beyond that, we would have to ask a lot of technical details in the prototype to do it well and/or have a dev provide those when generating.
So our proposal is instead to be more targeted about what code you can get from an Indigo prototype, chiefly what are considered "views" (so it would be primarily HTML and CSS for a current state, or element). We can look at what we can do for transitions. At least we can provide timeline details so that there is little guesswork for reproducing them in code.
OK. Since you are looking to export HTML for reuse and tweaking, we will leave this idea here for others to vote on, and not merge with HTML viewer. Thanks for your suggestion!
When you say keyboard input, are you referring to using the TAB key to jump between text fields? If you are referring to specifying keyboard shortcuts, that's a whole lot messier, AFAIK. Only coz the following situation:
[ Operating System [ Browser [Prototype]]]
There may be other shortcuts that may interfere with the keyboard shortcuts in the prototype :(. Do you have a solution that we can consider?
The default hover style for the buttons is very subtle to begin with, and when we test prototypes users never notice it. However, if you provide a custom hover style for the button by adding a hover interaction, it will be preserved.
But to dig a bit deeper, are you looking to add icons inside buttons? Is that the primary use case? I only ask because you mention "element above elements." It would be better if we address your concrete use case first before generalizing it as a pattern for how Indigo Studio should work. At least that way we know for sure that the major usage scenario is met and then we can continue to explore improvements.
Any reason for not making it a group first, and then adding an interaction to the group?
We will improve this. Just trying to make room to add this feature. Thanks for the explanation. You were perfectly understood :).
Ah! May be we misunderstood. We thought the question was about exporting open screen tabs within an Indigo project. It seems the question was more about when using the tab control, how does one export the content shown in all the tabs.
Right now the approach is to export visible content. In addition to this, it's exporting the interaction flow across screens and screen states. Such that, even when using a linear document format like a PDF, you could conduct a paper prototyping session right away.
Similar approach applies to drop-downs, but for that you could potentially set it as open in the designer before exporting.
In either case, let us know whether we understood your comment correctly, and I'll change it's status.
You can export any screen or a collection of screens in the project home view. Select screens you wish to export, right click and export. You can also use the "Export Selected" from the project home toolbar. This is the custom export option.
Since the you are exporting via the context menu for the screen tab, only that screen is exported. Invoking the context menu (right click) on the project tab will let you export all screens in the project. With this, we attempted to capture three scenarios
* Export everything in project
* Export just the current screen
* Export selected screens
Do you feel it's insufficient?
We will fix this.
We recently changed default colors for the arrows in the most recent version of Indigo Studio. Does this address your need?
See an example here: http://bit.ly/198DsOj
We do plan to add support for splitting out states into new screens. Glad to know we’re not the only ones who think it is needed. :) Thanks!
Let me see whether I understood this right.
You created a detailed user flow in one screen using states. And now you wish to add more flows to the the same screen, however, each new "flow" you wish to add is not very different from each other, except that some critical UI elements will be changed. Naturally, you don't want to create these flows manually. You wish to copy paste these flows on the IX explorer itself, and go in to make tweaks.
Any reason you would duplicate an existing screen and then make tweaks? It may help reduce potential complexity of the prototype. Looking forward to learn more about your design situation. I am assuming you are already using states pretty heavily coz this really helps in making small changes across states.
You can ping us at Indigo AT infragistics.com for a private conversation.
Love this idea. We had a prototype of it at one point. Will probably make its way back in at some point if enough people ask for it.
Definitely a cool idea. Have you seen the Denim prototyping tool? http://dub.washington.edu:2007/denim/
Hi Boris, thanks for the kudos. :)
Would you please consider submitting individual ideas for the specific widgets/controls you would like to see added. This makes it much easier for other people to vote on specifics and helps us prioritize more effectively.
We are adding some frame type stuff in V2, which is shipping very soon. Menus are something that just got cut due to time constraints from v1. I agree they are useful, but we still have to prioritize when they get done.