Justinmind’s New Release: CSS view, multi-target events and online comments on scenarios

justinmind-new-release-header-7-8.png

What’s New

New major features in version 7.8.0

  • New palette to see the CSS code of UI elements.
  • Events can now be targeting more than one element in the same action.
  • Events can also be targeting elements in templates.
  • Comments can now be placed and replied in Scenarios from the online service.
  • New tooltips in color dropdowns showing the hexadecimal color selected.
  • Now you can paste hexadecimal colors with the hashtag included in color inputs.
  • New button in image properties to save the image to your computer.
  • And also several bugfixes, including:
    • Fixed ‘Too many sign-ins’ bug related to account activations.
    • Fixed simulation issues in iOS prototypes that prevented click events from being executed.
    • Dynamic panel hierarchy can now be modified in the Outline tab.
    • Fixed a bug related to images displayed in Set Value events.
    • Problem related to reverting delete actions on screens has been fixed.
    • Fixed issue with JIRA and TFS plugins where issue types were always converted to ‘task’ – they now remain as in source.
    • Fixed style of iOS checkboxes in simulation.
    • Fixed crash related to fonts and styles when not available.
    • Fixed HiDPi issue with drop downs.
    • Fixed copy and paste issue when clipboard was empty.
    • Fixed issue with datagrids’ pagination when datagrids were nested.
    • The drag and drop of links between components in your scenarios has been improved.
    • Upon exporting documentation to MS Word, the order will reflect that of the Screen’s panel, instead of alphabetical order.

 

 

via: https://www.justinmind.com/blog/wireframe-tool-prototyper-7-8-0/

 

7 reasons why you should always make a web or app prototype (or at least a wireframe)

WhyProto.png

  1. Get everyone speaking the same language
  2. Visualize the future product
  3. Share ideas
  4. Read the article if you want to know the rest.

via: Justinmind 7 reasons why…

Justinmind is a high-fidelity prototyping tool, not to be confused with wireframing.  Wireframing is a great way to quickly mock up some pages of a website for review and discussion.  Justinmind can take those static pages and bring them to life so the users, developers, and designers can all feel the flow between the pages.

Justinmind has data-driven simulations of what the content on the pages will look like.  Import a few Excel spreadsheets and you can see data that changes as you interact with the prototype.

Skip the email madness and collaborate with direct feedback on the design that everyone gets to share.  When you are at the point of needing documentation Justinmind can produce many reports as you can dream up using Word Templates.

 

Justinmind Version 7.7 released

7.7-new-release-Justinmind-prototyping-tool-header.png

The Justinmind (JIM) folks are keeping up the heat with improvements to the best prototyping tool around.  Don’t confuse prototyping with wireframes.  They have added training wheels to allow those who don’t use it regularly to be “Stepped” through how things work.   These training wheels can be taken off for those who already ride the JIM bike.  They have improved Scenarios with the ability to add images and a full-screen editing.  They have improved Requirements by allowing a single requirement be attached to multiple elements of a page.  Last they added a real Bootstrap UI no more using a user-created widget library from 4 years ago.   Keep your eyes open for some “Techniques” videos on JIM from our training branch.

Rapid Prototyping web applications.. the best way

rapid-prototyping-software-development-life-cycle-header.png

I have been doing rapid prototyping for web and mobile applications for a few years now.  The answer to the question above is a definite YES!  If the user can “play” the prototype on the device it will be used on; they will be more likely to see things that need to adjusted.  “Play” includes viewing pages, entering data into forms, interacting  and navigation.  This article from Justinmind’s  E explains better than I can, more of the justification for real Rapid Prototyping web and mobile applications.  As a designer, I’m a big fan of Justinmind and use it  every day.     As a developer, I could write prototype scaffolding that could become the framework for the actual application.   While this may save a little time; Justinmind adds a collaboration layer that makes interaction with the user simple.  Recently Justinmind and Atlassian’s JIRA announced requirements integration which allows the prototype to feed the requirements to the developers via of JIRA’s.  If you’re going to be agile then you have to seriously consider rapid prototyping.

 

Justinmind vs. Protoshare Prototyping

When doing the design for a web application one of the considerations will be if the site is“Content” centric, “Commerce” centric  or “Data” centric.  Content centric sites have a fixed number of pages with very little data (ie: Blogs, Information sites, Wiki’s).  Commerce centric sites have a lot of data, images and a method for buying things (ie: Amazon, eBay).  A Data centric site is typically one that has lots of data and servers a specific purpose (ie: Monitoring Health Care Beneficiaries, Viewing Court Cases or reviewing store sales)  The prototyping tool you chose will have an impact on how your prototypes appear to the shareholders.

I’ve used Protoshare for the last 2 years and taught may others.  GeeMustHave has some tips and techniques for getting the most from Protoshare.  Recently a new prototyping tool has come to attention called Justinmind.  Justinmind is a Windows based tool that saves your prototypes locally in a file and optionally publishing them to the web for others to view and collaborate on.  If your web sites are “Data” centric you are going to love this application even if it doesn’t run on Apple Mac or Linux.

I’ve just begun an analysis and comparison of the two prototyping tools and will continue to do so for the next year or so.  I’m going to maintain the chart below as I discover different aspects of the 2 tools.

Created with Compare Ninja