CIO Happy Hour » Company

Wireframing Dialogue with ProtoShare

d.dolgorukov — Sat, 09 Oct 2010 14:26:01 +0000

Please meet a creative team, which brings you ProtoShare. Blake Johnson, Josh Chaney and Peter Uchytil tell us what collaborative prototyping is about, discuss advantages of pure HTML/CSS+Javascript solution, hint on iPhone app coming and future ProtoShare roadmap, give advice on how to select the right wireframing tool and much more.

Audio interview has a lot of bonus content packed!

Sasha Kovaliov (SK): Would you please introduce yourself and tell us in several words what ProtoShare is about?
Blake Johnson (BJ): Hi, my name is Blake Johnson, Vice President of Business Development and co-founder of Site9 company.
Josh Chaney (JC): I’m Josh Chaney, Managing Director of ProtoShare. ProtoShare is a collaborative web-based prototyping tool for web sites and web apps. And the keyword is here “collaborative”, it really facilitates the whole discussion not only on the prototyping base but throughout all the development process from brainstorming, wireframing, design work, and even on the actual build phase.
Peter Uchytil (PU): My name is Peter Uchytil, Product Manager. With ProtoShare we’re enabling discussion around the project so you could make sure that you’re building correct things.
BJ: We came from different backgrounds of Site9 which is a parent company of ProtoShare. We started as a web development company ourselves back in 1999, 10 years ago, and we did database-driven complex websites up till 2005 when we had developed a platform which we deployed ourselves, we called it “Launch Platform” and it helped to expedite interactive development. We decided to market that to get some venture capital and become a software company. We found some success, however, part of problem was it had a CMS built-in and a lot of larger companies wanted to have their own CMS solution. Our product also had some prototyping aspects built-in that a lot of people liked. So in 2008, last year, we broke out the prototyping aspect, and decided to make a SaaS application. That’s the short story how we came out with ProtoShare.

SK: ProtoShare is more a web development-centric solution, what are the modern tools of a web developer and what is the role of ProtoShare in this toolset?
BJ: If you get the tool you will see that it’s not just for web developers, it’s also for project managers, and art directors because you can review a creative concept online, project managers can come in and monitor where the project is, information architects can build out the prototypes, and stakeholders can be invited (management, marketing, clients) and participate in the dialog.
JC: There are really 2 parts of ProtoShare: the review process which is extremely simple, created for stakeholders, who don’t have time to learn the product (the number of reviewers is unlimited), and the developer’s part.
PU: A modern web developer certainly plays several roles nowadays and in larger organization these roles are going to be distributed among several people: user experience, design, information architecture, site structure, building the site itself. All those different roles can be fulfilled by a single person in a lot of cases or a couple of people, and ProtoShare addresses all those different roles.
You also can keep the client in the same system for other activities, for example for email campaign to review the message. If you need to look why the decision was made you also can go back to the history of the project and find relevant records, and we think it’s a great advantage.

SK: We are talking a lot about collaboration today. How does ProtoShare team collaborate with their users and gets their feedback for further development?
BJ: We’re on Facebook and Twitter, Linkedin and Youtube, and we do all the social media things that we can do, we monitor searches and anything about wireframing and prototyping. We gather feedback from all the users of the product, and a lot of the current features we have due to the feedback we have from the customers.
PU: When ProtoShare was still in beta we did usability testing. From the day one we were trying to get users’ and community feedback for better product design.

SK: You’ve just mentioned that you’re one of the oldest wireframing web app. Web is changing constantly – what emerging and existing trends do think influence the process of wireframing and prototyping and how do you reflect them in ProtoShare?
PU: The trends in wireframing right now are all about “doing more with less”, things that let you save money, make sure you can move the project forward. Tools become easier to use and access, which is especially important for customers. Regarding web trends in general we’re not really chasing the trends, because that’s the way to stay behind them. If you’re trying to build your own wireframing application you can do very sophisticated web actions, but then the problem is that you are going to spend a lot of time working with it. It’s a really a hard place to play. We think that we did tools so that people can describe the behaviors that they want on the web site and push the project forward.
BJ: If we were in any trend right now, which we mentioned earlier, our product does fit well with agile project development philosophy, rapid prototyping, and involving users.

SK: Peter, here I hear it again “more is less”. A lot of online applications are getting really popular because you don’t have to install or upgrade anything, just go to the web page and you have your working application. However, a lot of people nowadays still prefer to have an offline application. Do you think that you’re going to make an offline version of ProtoShare?
JC: Earlier we had it on our roadmap. Right now we’re a web-based application and to make it offline requires serious development work. We wouldn’t like to spend development time on those features instead of building a more sophisticated product and reaching more customers.
BJ: Technologies are emerging, they are still immature, the idea is awesome, and we have a request for that. But you have to be careful with this trade-off between online and desktop apps.
PU: I think that it’s also something that people are getting more and more comfortable with: online apps and cloud computing. Web developers and design agencies are going to be early adopters of the whole cloud methodology so it seems like a good fit for us.
JC: Before developing an offline application we may to prefer to develop iPhone version to allow reviewers to comment on wireframes.

SK: Being a totally online application has limitations on browsers. As we checked yesterday the browsers that are supported right now: Firefox, IE, and Safari. Do you plan to support any other browsers (e.g. Opera, Chrome)?
PU: There are 2 sides of ProtoShare: for developers and for reviewers, and review side is sort of client-facing and there are no any browser limitations. The reason we haven’t done extensive testing in Opera, for example, is simple: we take into account market numbers too. Each browser that we have in testing rally increases testing time, so if we are going to support it will take a lot of efforts. Unfortunately, there are still browser differences between PC and Mac. Our long-term goal is to have 4 browsers support for everything as soon as it’s viable to do: we have limited resources. For example IE’s and Firefox’s Javascript is just one huge difference. Our customer base of web designers use primarily Firefox and that makes a lot of sense to develop with Firefox in mind, making sure that review can be handled in all the browsers.

SK: At the very beginning you mentioned that your product is built in CSS/Html/JavaScript. If you have built it in Flash or Flex it would work in all the browsers. Why did you make that choice?

PU: The original technology is based on other product “Launch” and at that time it was Html/Flash hybrid application. We pulled Flash out and left HTML, we really feel that the html nature of ProtoShare allows us to do things that others don’t do or just can’t do easily. For example, we can use CSS to do the styling of components, and we were told that web developers just love that. It takes a little work to get there, but if you’re an advanced user this is not a problem.
BJ: We can reveal what we’re planning for our next release: we call it html sand-box.
PU: It will allow users to extend ProtoShare in any way they want. If they want to support a certain component they don’t have to wait us to build it, they can build it themselves. And that’s not kind of thing you can get from Flash-based application.

SK: Are there any other innovations which are coming with the new version?
BJ: We’ve just had a release but we’re planning to improve review and project management aspects of application, to make the processes more robust and suitable for larger companies.
JC: With the last release ProtoShare 3.5 (August 23^rd, 2009) we’re really facilitating collaboration throughout the whole web development process.
http://www.protoshare.com/ProtoShare-Benefits/

SK: Here is a bit tricky question. There are so many players popping up in the wireframe apps market. You’re not a new player here. Can you give any tips to our readers how to select the best wireframe application for their needs?
JC: The reason that you build a prototype is that you so can get feedback and start a discussion so you can make refinements during prototyping phase, rather than doing rework at the backend, which makes it more expensive. When it comes to choosing the right tool everybody has different needs so I’m not saying that one tool can fit everyone. But my only suggestion would be, when evaluating these tools ask yourself some questions: am I creating a prototype to generate a discussion and gather feedback, is access easy for my stakeholders at all the points of the process, what this tool offers now, what’s its potential for future.

SK: Guys, thanks for the great interview and ideas you’ve shared with our readers. Protoshare is truly and amazing product, and we are sure you’ll make it even better!

Experience Functional Wireframing with Justinmind

d.dolgorukov — Wed, 22 Sep 2010 09:28:19 +0000

Today we are discussing prototyping with Xavier Renom, CEO and co-founder of Justinmind. The company is quite different from our previous participants – Justinmind Prototyper is a desktop solution only. Bundled with a comprehensive set of features makes it a great tool for pros. Xavier shares his vision on wireframing market, hints that online version is to come soon, and tells some intriguing user-experience stories.

CIO Happy Hour (CHH): Please briefly introduce yourself and your product Justinmind.
Xavier Renom (XR): Xavier Renom, CEO and co-founder of Justinmind.
Justinmind Prototyper is a productivity tool that allows the prototyping, simulation and validation of applications and websites. It covers the entire process, from the navigation flowchart creation to the usability testing, as it allows creation of fully functional simulations.
In a nutshell: you can visualize and test your web application before you code it. This way, you’ll minimize changes on later stages and risks involved.

CHH: Only a couple of years ago wireframing tools were associated with pen and paper, Visio or PowerPoint at the maximum. Could you tell us more about the evolution of Justinmind from its very first concept till today?
XR: Justinmind started as a software development company, founded by two engineers. During its initial phase, we discovered that using a high-fidelity simulation, it was possible to reduce time and re-work in project development, so we started the development of Justinmind Prototyper.
Our products allow the creation of hi-fi wireframes, and then simulate the application, with advanced features such as data behaviour, conditional events and templates.
Justinmind Prototyper is not just wireframing software, it also allows stronger and more powerful prototyping. We intend to provide a software that allows people to visualize their concepts before long coding phases, and have it all documented before building the real software or a website.
Besides, it is intended to help visualize the changes during application development projects.

CHH: Justinmind is desktop software. A lot of your competitors offer online versions of their solutions. Is there a particular reason why JP sticks to desktop or are you planning on releasing a web-based version as well?
XR: Most of the web competitors allow you to just design a mockup or a wireframe, but not much more. Justinmind Prototyper is a full drag&drop tool for rapid prototyping and we believe that a desktop environment is perfect for productivity tools … by the moment.
On the other hand, sharing and validating prototypes online is very important. That’s why we are about to launch Justinmind On-Demand, which is a platform where a user can share, test and annotate a prototype without additional installations.

CHH: Who stands behind Justinmind? Please tell us more about your team and your inspirers?
XR: Justinmind is a Barcelona-based spin-off from Universidad Politécnica de Cataluña. It was founded by Xavier Renom and Pablo González, and is backed up by venture capital. Today, it’s composed by a team of engineers, researchers and a marketing and selling team.

CHH: Please describe your typical clients/users. Is there a dominant geographical market? If yes, why?
XR: We have government, banks, insurance, small IT consulting companies and several UX designers around the world. Nowadays our bigger clients are in Europe, but we’re selling online to the whole world. It’s impressive the amount of users we get from India.
We have some distribution partners around the world, and our potential marketing is not restricted geographically.

CHH: Justinmind is a powerful prototyping tool with an extensive set of features. Do you have statistics on their usage: most used, least used, etc.?
XR: It always depends on the client and/or project being done. Big enterprises need and use the Requirement Management features, personalized documentation and the capabilities of data management. UX designers are more interested in dynamic interactions, events and simulation.

CHH: Taking into account your vast experience on the market, do you have any plans for going into the niche for individuals with light version of the product for a lower price or even for free? Why or why not?
XR: We received some feedback from users about this. We cannot say we won’t do that, and if too many users were interested in a version without datamasters or business logic prototyping (just for drawing wireframes), we’ll think about it.
Nowadays we’re working full time trying to improve our main product, Justinmind Prototyper.

CHH: JP covers full cycle of prototyping making it time-consuming to start using it right away. How do you assist JP newbies? What is an ordinary implementation phase duration?
XR: We think it’s very important to help users to understand better our tools and the powerful of application prototyping. We have a support portal, with people always willing to help and assist our users, that’s not just marketing talk. We have people to be online talking to consumers, solving problems and generating tutorials. Our blog’s main objective is to talk, solve questions and give some usage tips.
Besides, we offer training courses for customers, and try to use internet to leverage the help for our customers.
For our users or future users that have any problems or doubts:
http://support.justinmind.com
http://www.justinmind.com/blog
The implementation phase duration depends on the customer. It can take just hours for small companies with small teams and easy development process, and 2-3 days for a large company with complex development processes and methodologies.

CHH: How do you differ from your competitors and what innovations have JP brought to the market?
XR: Justinmind Prototyper has features competitors still don’t have, and some that were copied soon after launching.
Most of our competitors allow you to simply draw wireframes. Justinmind Prototyper is meant to be a full working suite. You draw the Navigation Flowchart, create the screens, manage requirements, and generate documentation for final production, with all the elements interconnected via drag and drop.

Bi-directional drag and drop – you can link objects, comments or requirements dragging them both ways around;
Templates, which can be imported and exported;
Instant simulation without the use of a browser;
MS Word document generation customization.

CHH: How easily can JP be integrated in the business process of a particular company? Can you describe a usual case-study?
XR: It is possible to go from idea to full simulation of software or a website using only Justinmind Prototyper. Justinmind recommends adapting our Agile Prototyping Methodology to the business processes of a particular company.
As for usage, some corporate clients use it to prototype applications and create their own product libraries. Software companies use it to simulate future products, and even it was used in a pre-sales stage for a client of ours.
There’s the case of Innoget, in which an entrepreneur had the idea of a portal, but he was a biologist. So he used JP to create the whole portal to explain to investors and programmers what exactly he wanted, after a 2-hour crash course!

CHH: You’ve contacted us via twitter yourself. This means you have a great monitoring net. Do you have any tricks you can share with other readers on brand monitoring?
XR: We intend to use the tools offered to contact and provide a better service to our users. We started twittering, blogging and contacting bloggers, because it’s a more simple and honest way to approach and reach them.
We hired a copywriter who is an information junkie and is always testing websites and tools for tracking what’s happening online, via twitter or blogs. A good feed reader and the ability to fine-tune it are a must.

CHH: How successful is social media as a channel for generating new clients? What is your experience in the social internet field?
XR: Nowadays, it’s a great tool for engaging into conversation with our customers, and it helps to know what really users want and expect from our software. And, of course, it is very helpful. We acquired great insights from some blog posts and some encouraging tweets.

CHH: Xavier, thank you for a great interview. You’ve done a great job with Justinmind and we wish you to stay on track and remain an example of a great functional wireframing solution!

Our readers, companies and we would love to hear the questions you have or share your praise to your favorite wireframing products!