I didn't realize the real problems our app is going to face until Zit Seng shared his thoughts on Monday's lecture.
Loading time is critical. We won't meet a user's satisfaction if it takes too long (say more than 2seconds) to load. That's pretty disastrous for a HTML5 app as the app may include heavy framework js/CSS files. On one hand, we shall do as many computation as possible on the server side and cut down clients' JS files to reduce the loading time. On the other hand, we can hardly make it as we need these files to perform offline functions. This challenge will unfortunately happen in our new HTML5 app. Even people in China will be accessing it. What if it takes 10 seconds to load the page?!
I also felt worried when Zit Seng said that we shall avoid .htaccess and reduce http requests. Thanks to him, we can at least avoid some of the bad designs in our app. We previously thought to use more javascript to process the ebook reader. Later we decided to utilize the power of cloud to process the ebook data in the back end and do less work in the front end. Thanks to Aldrian, who is really thoughtful and bright to suggest a very scalable database design.
I feel pretty good on our app. Though it's still very rough, I find our team mates are getting more involved now. Hu Qiang has made a pretty nice design. Yingbo processed the json object on the client side. I'm doing pretty well with the database and API. Aldrian is also doing good at the book format processing and some high level designs. Compared with the previous two assignments, we seem to be more specified and dispersed in the job allocation. I find it good and time-saving.
Am updating IOS5 on my Itouch:) Need to do other projects tomorrow as well.
Stay Hungry, Stay Foolish--Steve Jobs
Loading time is critical. We won't meet a user's satisfaction if it takes too long (say more than 2seconds) to load. That's pretty disastrous for a HTML5 app as the app may include heavy framework js/CSS files. On one hand, we shall do as many computation as possible on the server side and cut down clients' JS files to reduce the loading time. On the other hand, we can hardly make it as we need these files to perform offline functions. This challenge will unfortunately happen in our new HTML5 app. Even people in China will be accessing it. What if it takes 10 seconds to load the page?!
I also felt worried when Zit Seng said that we shall avoid .htaccess and reduce http requests. Thanks to him, we can at least avoid some of the bad designs in our app. We previously thought to use more javascript to process the ebook reader. Later we decided to utilize the power of cloud to process the ebook data in the back end and do less work in the front end. Thanks to Aldrian, who is really thoughtful and bright to suggest a very scalable database design.
I feel pretty good on our app. Though it's still very rough, I find our team mates are getting more involved now. Hu Qiang has made a pretty nice design. Yingbo processed the json object on the client side. I'm doing pretty well with the database and API. Aldrian is also doing good at the book format processing and some high level designs. Compared with the previous two assignments, we seem to be more specified and dispersed in the job allocation. I find it good and time-saving.
Am updating IOS5 on my Itouch:) Need to do other projects tomorrow as well.
Stay Hungry, Stay Foolish--Steve Jobs
Comments
Post a Comment