Duke's

Prototyping is an essential part of Software developing. But we have so many options while choosing a prototyping tool. If you just make a choice among them with the idea that one is for all, well, you are terribly wrong. In fact, you will need these tools all the way through the entire design process. Draft/Wireframe: Paper and Pen, White Board, Balsamiq , Mockplus There are Art design, UX design, and UI design. But, no matter which kind of design you're focusing on, you always need to draw a draft or wireframe. When you are picturing your product as the most beautiful star in the sky, just leave the recording works to them. Don't even mention the greatest inventions for designers: Paper and Pen. The tools created in 21 century are also pretty good. The wireframe tools like Balsamiq and Mockplus are the gifts from technology. With the sketch style, Balsamiq has gained a lot of users. Even though there are rarely big moves in recent years, it still has a fir

With the development of information industry, software development has gained more attentions. Of course, prototype design also has become more important than before. When we are designing a prototype, usually there's two ways: First one is to set all the interactions based on State (some may call it Layer), like Flinto for Mac and Priciple. The other kind is based on components (or widget), such as Axure and Mockplus. But, which way is better than the other one? Let's find out! 1. Based on State Tools like Flinto for Mac and Priciple have one thing in common: most of them don't have the ability of creating a component. In other words, they can't creat a wireframe by themselves. All the components and pages are coming from the files imported from Image editing tools. Flinto has a great sense, it grabs an opportunity, the opportunity is the rising of Sketch. They have successfully developed a version that almost adheres on Sketch. The truth told us, it&

Everyone says that it is hard to be successful design master. Well, you think this is easy to be a completely failed UX designer? To be honest, I don't think that would be easy. So, how to be a completely failed UX designer? At least, you need for these things below. 1. Never care about users' feedback Everything's tough in the beginning. But, it is a great start when you choose to ignore users' feedbacks. So, how to completely ignore users' feedback in details? First of all, don't do any user research, none of them. User-research is one of the most important ways of getting users' feedback. It's like a guide for new product designing and improvement. If you want to be a completely failed UX designer, then please don't do any research. Also, please stay away from any kind of testings. Testing is the examination of your prototypes and your designs, especially when the testing has included the advice and suggestions from the

In our daily software design, it often involves the prototype design. There are always three purposes for prototyping: 1. Prototyping for yourself, for further design. 2. Prototyping for developing team, for developing. 3. Prototyping for client, for getting paid. However, sometimes we have lots of newbies take the developing prototype to the client , leading to customer dissatisfaction, then the negotiation process will be extremely difficult . Some people take the prototypes which are made for customers to the developing team, the result is inefficiency of the developing , and might be rejected by the team. In a few cases, it may lead to more serious communication problems. In few situations, some may take the prototype for himself to the developing team or even the clients. What happens next, would be really terrible. So, for whom, which kind of prototypes shall we make with what tool? Please allow me to explain . 1.  For yourself What matters: Draft