Tag Info

New answers tagged

0

I would say that a proptype has made up data on each page, often the data on different pages don’t relate to each other. E.g. it shows a concept in such a way that it is clearly not useable in reallife. But an alpha allows data to be saved and the next time it starts up it uses the saved data. Often an alpha will “do less” then the prototype, as the ...


1

tl;dr YES Versioning systems Semantic Versions is only one of many ways to version/name your steps to the final product. And alpha is only part of the Semantic Version idea. In other systems there is nothing like an Alpha version. Some version number systems aspire to merely label changes in an interface, but there is much in the human experience ...


4

Unlike nightning, I hope the answer to the question is always. On detailed designs What else do you give in your design deliverable to developer if not a full specced-out design that ideally has be the same one you've used in your user-testing using prototypes? My experience is that if you leave any stone unturned with your design - ie, any place for ...


2

I think this depends on your software methodology. This somehow reminds me to eXtreme Programming (XP), where you start with the simplest solution and keep adding new functionality through short development cycles. If you are following a methodology such as this one, then you can transition when the main features are included. I can agree with the previous ...


71

I hope the answer to the question is never. A prototype is meant to be a test. Built using the most "hacky" approach with the least amount of time to get initial feedback on whether a concept is viable. The alpha is something you give to actual users. This is the version, if successful, you hope to build upon to become the beta and eventually the product ...


-1

Prototype: Demo/Test version with some features still missing/incomplete Alpha: All features complete Beta: All features complete, no known bugs (At least in theory ;))


8

Mostly working self employed / freelancing on website related projects I would say it's the developer/designer's decision if it's a (working) prototype or a (buggy) alpha version. A prototype is never ment to be public while an alpha version robably is. The line between those two is difficult to draw – but for me / with web projects it's the moment when I ...


3

Speaking as somebody who occasionally sits on the interviewing side of the table I would not care at all what tool you chose to use. Balsamiq. Sketches on paper. Keynote. Whatever. What I would care about was that you could explain the design decisions to me, and that the deliverable does the job intended. If your not sure what kind of artefact and for ...


1

Honestly, it depends on if it's UI or UX. Interfaces are going to be more visual, and may require you to produce a more mid-fidelity prototype such as you would on Balsamiq, Moqups, or Froont. On the flip-side, if you're interviewing for UX, notes and scribbles may be more important to help describe your actions. Of course, some of those tools would still ...



Top 50 recent answers are included