Dynamic TypeAhead

My TypeAhead

Click Here!!!!

MIDTERM EXAM

Check my Social networking Site click

here

!

DRUPAL

Check my

My drupal

Ajax CRUD

AJAX CRUD

Session

Exercse

For my Exrcses sir,

digg digg, Adsense, Theme switcher, about, blogroll,feedburner, Gravatar, Postratings

http://janinetanko.site90.com/wordpress/?p=15 - COntact Form
http://janinetanko.site90.com/inettuts/
http://janinetanko.site90.com/wordpress

Final Exam

http://janinetanko.site90.com/wp-coda-orange/index.html

-Favicon

-Plugins Used

http://janinetanko.site90.com/wordpress/?p=20

-BackUp -Email – Install to my WOrdpress

BackUpWordPress http://janinetanko.site90.com/wordpress

	Inbox		X

BackUpWordPress http://janinetanko.site90.com/wordpress to me

show details 4:14 PM (25 minutes ago)

Images are not displayed.
Display images below - Always display images from janine_tan_ko@yahoo.com

Your requested Backup10485760:101090 – /home/a7685471/public_html/

wordpress/wp-content/backup/2008-12-16-08-14-39-sql.tar.gz
Backup file is readable.

iNettuts

Check out myiNettuts!

iNettuts

Shopping Cart

My Shopping Cart

 

My Shopping Cart… visit here MY SHOPPING CART

Getting Real : Conclusion

Chapter 16

In this last chapter it only tells about what this book has bought to us. In conclusion, i have learn a lot from this book. It’s not all about how to build an app but it also tells how we can appriciate our app by seing it as more than a software. And the people who should be involve in your app. And some other things that we should remember whether we’re building or editing our application.

Getting Real (Chpater 15)

Chapter 15:)

This chapter tells about Post-launch, it’s said that after you have launch your product make sure to have a major update 30 days after it. So people would know that you listen to them. It gives buzz to people to talk about and blog about it. Keep your product alive by keeping an ongoing product development and a blog post about the launch. Make sure you update your blog so people would be aware to the changes or updates you are working with. Here are some that you we should include on the blog that you’ll post Faq, How-tos, Tips & Tricks, new features, updates & fixes and buzz/press.

And make sure if your building your app do not use Beta.  Beta are use only for those app who is not a finish product and would say to their customers that if it’s not perfect it’s not their fault. That is not a good idea. Perfection never happen but you should take responsibility for what you’re releasing.

And when problem come accept it. And prioritize each bugs because some bugs are just annoying not destroying. Not all bugs must be fixed because some are just bugs. Except if it’s destroying your database already. Prioritizing each bugs would make your life easy. And remember to be honest with your customer, if they complain about it be straight up with them. Tell them you’ve already issue and dealing with it.

And lastly go with the flow, make sure you update your app as fast as possible. You can change as you go along. And be open to the fact that your original idea may not be your best one.

Getting Real : Support

Chapter 14 : Support

In this chapter it tells about the support that you could give to your customers, at the first part of it tells about breaking the walls between the developers and the customers. Because like what example they give in the kitchen the chef are the one who cook the food and the waiters are the one facing the customers. The chef wouldn’t be able to know the response they get from the customers because he is not the one who’s facing them. Like in building and app sometimes those who promote the app are the one who face the people not the real developers. Walls should be break between them because it’s a lot better if the developers hear what their customers says about their app. So if their other things they could change at least they would know it by their self. In this book the 37 signals, the one who answered emails are the person who actually build this product. So they could provide support for customers and to get a response straight from the brain of someone who build the app. And they could also be keep in touch with them if they encounter problems they can personally solve it.

It also said that why build an app that would be hard to use, if you can use it without the manual. Like what is said on the previews chapter build and app that would be easy and by keeping everything simple. The less complex your app is the less you’ll need to help out the weeds. It would be more easier for you and your customers. You would receive less complain and less to your work. And people would love your app because it’s easy for them to use. And in having a response to them customers like when you quickly answer their question. Just say something so they would see that you really care about their concerns. And if you receive any complains it’s not always right to change everything they say because it would be a lot work for you and customers are not always right. Just provide a forum that your customer can answer each one question and you’ll see how they help each other.

And if problems came, let them know about it. Even if they don’t see it tell them. Be as open, honest and transparent as possible.