h1

Getting Real – Chapter 9

October 9, 2008

In this chapter, the author discussed how we should design our interfaces. It is ALWAYS a GOOD PRACTICE to know first what is the BIG PICTURE of the project/application you are going to make. Determining how your program will look like would give you already the idea on what will be your scope – whether you need a full-blown project or a simple app to make.

Keeping the idea of knowing what will be the outcome of your design would help you focused more on the functions that you will be adding or creating. The designing of your program would also limit yourself – avoiding the idea of making projects that are not feasible to make. In designing, start first to what is really INSIDE your application. At this stage, you may eventually have the knowledge of what will be the primary purpose of your program/application.

What people see at your application/proect is what you get. Always start a good impression in making designs/layouts for your project. These designs would serve as blueprints for your work. As for the impression you’ll be getting from others, there are three ways, or should I say, three types of first impression – 1. regular, 2. blank, and 3. error. Having a ‘blank’ impression from your viewers would serve as an advantage, since it would help you more to motivate or to convince your viewers that your project/application is one of the best they could even see. Talk about marketing your apps to people for the first time!

Always remember that changes, even problems, are inevitable. Now, it is up to you whether you want to change you app – good or bad – which will eventually reflect you character as a developer of that program/app. Know what are your real capabilities and skills to develop and create an application. In every program/application you make, you learn more and you became mature – you now understand and experience what it feels like to create your own apps.

The author suggest that in making web sites, it is more advisable to focus on what customers or users REALLY NEED. Avoid DESIGNING too much on your website/s – thinking that compelling stuffs would help you. As you can see, too much design means too much maintenace to managed. The author recommends to use small-scale websites, which will help you and your customers navigate websites/links smoothly and efficiently.

Think before you act. To avoid too much cost or breakdown of your project/app, learn to analyze first what would help you as an individual – and what others can benefit with. By understanding what are ‘real conversations’ coming from your customers, this would aid you plan ahead to make and to design the specific needs of your customers. By managing what probable risk/s might happened, you can assure yourself that you are ready and prepared for it.

Advertisements

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: