Lead Source
Lead Status
Mini Navigation


Expectations Vs Reality

| Category: How do we do it    

Every customer who is at the door of a mobile application firm is like a teen who has married a girl whom he saw yesterday at a shopping mall; both of them have great dreams about future!

But, talking customer specifically as this blog is indented to be,

Either we have to change the customers dreams into reality or make them dream about their ideas or product.

Whatever the channel is, the objective is to make them do two things with their ideas or dreams about mobile applications they have in mind!

                                      Make them dream the feel and feel the dream!

Well, it is no simple task to make your customers feel good on the designs that we do on their dreams; alas it is easy to make them feel bad though! :-P

One major giant leap and also a shortcut to make them feel good about their dreams is, provide them with good probably the best UI and UX.

If you question me, “Is that, that simple to do, to make the customer happy?” well, the answer is a big NO!

The customer should never have a feel that their product is less than what was expected; instead it is super great to exceed their expectations in reality!

When the project is approved, the very next step would be to “listen” to the customer. When you hear more, you design more and when you design more obviously you do more.

After listening and defining the “Spec” document, the next would be the crucial step that we are talking about- Visualizing their ideas!

When we read bad reviews or sometime #$**%!@@ these words in the application stores about the UI or experience of a particular application, this lamentation cry of a customer often strikes me,

                                        UI, UI everywhere but no good UI to touch and feel!

One of the points where most of the developmental firms fail is that they don’t focus on the UI and UX. How much ever the code may be organized and structured, it is the UI and UX that speaks more than them.

The users are not bothered to know or even think or discuss about the complex technical and technological jargons but they are more inclined to know how the app look and feel in their hands.

It is wise to remember that it is near impossible to get back the glory once you lose it!

When talking specifically about the mobile application, the underlying concepts may sound simple but the overall architecture may be little harder than what we think.

I have often compared my cooking skills with UI and UX designing skills as both of them need envisioning the look and feel about the end product.

Both of them once lost its glory, will always remain even after you better it thousand times!

So it is better to start cooking our UI and UX and start prototyping our cookery dishes! 

Consider the following ingredient that makes your application and customer look happier! :)

Ingredient #1: 

The conventional way and probably one of the simple ways of reflecting the requirements, is to have either a “Wireframe” or a “Paper-Pencil diagrams”.

Though it is not a final verdict on the UI or UX of the application, it is merely to showcase our understanding on the requirements or specs and probably to show others that we have done “something” about their ideas! :-P

Once you do them, share them with the customer, get his feedback, better it and re do it until and unless the customer is satisfied with the “abstract” layouts of his ideas or dreams about the product.

But remember to set an expectation on the customer that the wireframes and the Paper pencil ingredient is a minimalistic reproduction of images from the words. 

(Just have a look at the below image, this is what I was talking about.)

Image source: https://popapp.in/#design-on-paper

Or a wireframe which looks something like this,


The next step after every UI design is to add flavours and spices to it called the “User experience” factor.

NOTE: If the time frame to cook an application is less, then don’t spend much time on ingredient #1.

Ingredient #2:

Unlike a wireframe, a prototype is a persuasive story teller and “the great recipe” to add in our cookery!

The prototype reveals the depth and range of decisions and it does not just stop with layout it also carries motion, animation and transitions.

It’s all of these sub ingredients that contribute to the impression that a product or a dish as we call it here is “the great” which is useful, engaging and something you’d like to use or probably keep using.

With this UX ingredient in our dish, probably most of the design issues or miscommunications during requirement analysis can be minimized to the maximum extent possible.

It can help to advance a brilliant idea with a fraction of the effort of complete development. Sketches and wireframes are perfect early on in a project, but once they’ve served their purpose, prototypes enable the design to advance, and push thinking towards clarifying other important details including transitions.

Hence, as a step ahead in the industry we @Hakuna matata use @FLUID UI, a complete prototyping tool that has been a successful experiment in the industry wherein only few have turned towards User focus which more important rather than an application focus.


The conclusion is very simple, either use ingredient #1 and ingredient #2 and make a grand dish that looks and feels good and yes definitely it won’t smell good :-P

Or use the ingredient #2 with special care and create magic in every app you design!

Have a App-ie  time!

comments powered by Disqus

Follow Us