November 20, 2008
· Filed under Uncategorized · Tagged is ebiz, O0A
This is the end of the chapter of Getting Real.
This chapter discuss that everyone can make a program because of internet. It taught us to use the advantages of having internet and web. We must have the passion to do things in order for us to be successful. The difference of us and other people is how well we execute a program. It don’t need for us to memorize codes because there are open source in the web. There is no excuse for making an application.
We need also people who are also passionate in doing applications. Getting Real is about building great software.
-end-J
November 11, 2008
· Filed under Uncategorized
Chapter 15 suggests that we should show our product is alive by way of updating it. We can have a blog update every week so that your users will know that there are also administrators that are checking frequently the site.
Try not to use beta. By having beta, it shows to the customer that tries to use this but it is not perfect. There is no commitment in developing a software, There is no perfect thing in developing software. Thus, we don’t need to have beta in order for the people to test it.
We must not panic if we encounter bugs in our software because there are actually bugs in our application. Also there are bugs that can’t be fix by ourselves.
This chapter also says that if you introduce a feature, try to change the look and content of your application so that it looks new again. Also, if you encounter negative comments, try not to care about it because we can’t do anything to it.
Have a subscription with news feed so that you will be updated with stuff. Having a RSS will deliver instantly the information to you. It will not be hard time for you to discover what’s new.
Go with the flow. It means that if there are changes happening try to know if it suits with you. And if does, we must try to adapt to the changes. Having innovation will make our software outstanding from the rest of our competitors.
November 11, 2008
· Filed under Uncategorized · Tagged getting real, is ebiz
Chapter 14 suggests that the developers should also feel the pain of their users. That means they need to understand well what the needs of the people are. To be able to understand the situation of the users, I think it is better to have some experience and be a user some time.
There must be zero training. This means that keep your product simple so that it doesn’t requires the user to read manuals. If I am a user and I find the software hard to use, I will not continue using it. As a user, I will not read manuals for me to use software because that will waste my time.
Your application should have a different and good response compare to your competitors. Also, what you promise to your customer must be fulfill because that will show your sincerity to respond to them. The customer will be loyal to you if you have a successful response to them.
We don’t need to follow what customer really wants. We must first analyze if we can do it or not. This chapter says that the customer is not always right. I agree with it because we know what’s best in our software.
Use forum in order for the customers to help each other. It does not only need you to answer all the questions of your customers because having a forum will help each other. There would be an open communication so that any problem that will encounter by the user will be answered by also the other user.
If there are problems encountered by the developer, try to say it to your user that you have encountered problems. You must not worry of the reactions of your customer since everybody makes mistake. We must try to be honest to our customer and they will appreciate it.
November 11, 2008
· Filed under Uncategorized · Tagged is ebiz, O0A
November 4, 2008
· Filed under Uncategorized
One of the suggestions of getting real is making sure that you will market your software before launching it. It is useless if you already finished your product and no one used it. The programmer makes a software, not only for his benefits but especially the benefits that the user will get in using that software.
In addition to that, the software that you must posses features such as forum for your customer concern and etc so that the people will not have a hard time on solving their problems.
Moreover, this chapter also discussed we as a developer need to find what the people really likes. If they don’t like what we are offering, they talked it in their community until the whole community will not like what we are doing. Thus, we need to know what is important for people.
This chapter also talked about is to promote an upgrade version of the free version. The developer must not only stop with the free version because he will not get money to it. What he can do is to make an upgrade version or premium services to it that might other people like. And you can also make a brief explanation why this feature is not available because if customers will not know the reason why, they will not like what you are offering because of the restrictions.
Another, this chapter explains why there is a need for an application to have a good name. First, the name should be easy to memorize and understand because if the name is easy to remember, then he can go with the website. Second, the name must be short but catchy. There must be an assurance that the people will be strike with that name even though it is short. It must be short so that we don’t need to waste our time on typing the complete name just to visit the page.
One thing, share what you know. We must share what we know to our community as a sign of our gratitude of using the software we develop. Having customer service in our application would be suitable for this example. The users will be happy that we will respond to their problems since they are using our application.
