Prof. Ben keeps emphasizing that CS3216 is not about hard coding, but about solving problems and making a difference.
1. What is the app that we are going to build?
We are trying to build a HTML5 reader that works on different platforms including desktop/laptop browsers, tablets (ipad,etc) and smartphones (iphone /android). I initially came up with the idea of making a HTML5 ebook reader when Hu Qiang and I discussed with an ebook retailer who are currently making a native ipad reader. We think that more people will be able to explore the app if we make it a cross-platform one despite of their physical devices limitations. We also would like to take the advantage of HTML5 and the cloud to allow content synchronization and offline reading.Yingbo enjoys reading novels on her ipod touch and she finds the idea pretty interesting. Aldrian also thinks it's a good project, then we four decide to work together and make it happen:)
2. What is the exact problem that our app is trying to solve?
Depending on situations, readers have their own preferences on the reading devices. For instance, they may love to read on their phones when they are taking a bus. But when they are at home, they may like to read on their laptops or tablets. When the reading devices changes, they would like to continue reading on the new device the same page where they left last time. Readers are also sometimes lazy to download ebooks and then import to their devices. They would prefer a ebook reader that directly get the resource from the internet and view the book on the ebook reader. Another supply-demand problem: China is said to have a mobile ebook reading market of more than 0.8 BILLION RMB/quarter year and we are build this HTML5 to meet the huge demand...
3. Are there similar apps with a similar idea?
One very new HTML5 ebook reader is the Kindle Cloud Reader by Amazon which was launched a week ago. It's very elegant. Kindle Cloud Reader allows bookmark synchronization, offline reading, too. They assigned different tags on the html passage tag<p> to do book marking.The ebooks are mostly in epub format, too. One big disadvantage for the Cloud Reader is that it only allow kindle users to access the contents. So far, only Chrome, Safari(desktop/ipad) are supported. Another disadvantage for Amazon is that they do not open up their services in China yet due to copyright and cloud service registration issues. Whereas, our app is mainly targeted in Chinese Ebook Readers which is said to be a 0.8 BILLION dollars' annual business(We're afraid not to implement monetization on that).
A good news for us is that there is no HTML5 ebook reader found in Chinese Market yet. We are the pioneers!
4. Job Allocation.
I personally love Kindle Cloud Reader and think it's not hard to build a UI like it using JQuery Mobile. But we need different layout for different screen size devices, the UI may not be suitable for all. By the end of the day, we agreed to build a prototype with the similar UI as QQ reader first for the first version.
For text display, I think it would not be nice to take the HTML file out and render it on Canvas, but as my team mates say we would be able to standardize all the text format and layout if we render all the text on our own way instead of directly use the HTML file in EPUB. Prof. Ben suggests that Canvas would be too slow to render and not so stable. I think I'll try on both and figure out what's the best way.
5. Very good suggestions.
Prof. Ben suggests that we can allow users to provide a url for the ebooks they find interesting. This not only provides other readers with the access to the books they love to read(not in our library yet), but also prevent copy-right problems. That's a very good suggestion. We may try it out. Kok Wee also finds it a good idea to synchronize among different devices, but the big competitors seem to be very challenging for us.
If you have any other suggestions, please feel free to comment on the blog. Thanks:)
Last but not the least, we'll attract more than 10,000 users for the project, fairly big number ha.