In coding and by extension in ProtoPie variables are typed, that is to say there are rules as to what type of value you can put inside them. You can think of a variable as an empty container that can hold certain pieces of information. Many times you will want save certain pieces of information to use elsewhere in your prototype, be it to replay information someone has typed or to make logic decisions displaying differing scenarios and variables are your way of doing those things. ProtoPie, whilst doesn’t expect you to code does require you to understand certain code concepts and variables in the first and most important one. Remember when I said earlier that you are required to use some coding? Well, this is the first function that goes anywhere near the code paradigm. It’s important to state that it’s these features existing in one tool together with the ease of use of the tool that make ProtoPie so powerful so here we go. To set the stage as to why you should consider ProtoPie, I want to draw your attention to what I consider some key features that sets ProtoPie apart from other tools on the market. If that’s something that interests you then read on. So, in a nutshell, ProtoPie enables you to build a realistic prototype of your native app that will be indistinguishable from the real thing without you learning and writing any code. The only tool that comes close to what ProtoPie can do on the market today is FramerX and that tool requires you to get your hands dirty with code pretty quickly if you want to build anything meaningful. It’s amazing with the capabilities that ProtoPie provides that you don’t need to write any code (or hardly any but we’ll come to that later). One of the things that ProtoPie considers that sets it apart from many of its competitors is its ability to control the sensors in the modern-day device such as your device’s accelerometer but it’s selling point is much more far reaching than that. ProtoPie is an interaction design tool that enables the construction of some very realistic prototypes. I have used most of the prototyping tools out there at one point or another but currently, I’m hanging my hat with ProtoPie. It doesn’t require me to buy into a single companies ecosystem (unless the designer worked for a company that already has).It’s easy to integrate into existing workflows.It can do the basics but also advanced interactions.So here are the criteria I consider when thinking about recommending and training designers in any tool: Designers need to be able to get up and running as quickly as possible. We all want one tool that we can use that can do everything we need and we want that tool to have a fairly low learning curve. There are of course many different needs and levels of skill among the design community and this has a bearing. The process of vetting the right tool to use for a whole team is rigorous and lengthy. Time is precious and also companies are not in the habit of paying out for every design tool that comes along. Speaking to designers there is a fair amount of confusion as to the best tool to learn. For the last few years, I’ve spent a lot of my time training designers in prototyping at the various places I have worked. A simple search on prototypr reveals 32 results. Over the last few years, there has been a huge surge of prototyping and interaction design tools.
0 Comments
Leave a Reply. |