Time to Write a new Book: Enterprise HTML5 and Going Mobile

Yesterday, I was talking to my business partners (and former co-authors) about writing a new book. So far, the working title of the book is “Enterprise HTML5 and Going Mobile”. In this book we’ll explain different approaches to creating desktop and mobile Web sites and applications while developing  various versions of a sample Web site “Save the Children”. Below is the current version of TOC:

Enterprise HTML5 and Going Mobile

Part 1. HTML5 On The Desktop

Chapter 1. What’s HTML5?
Chapter 2. The Web Site “Save The Children”: UI Design and Specification
Chapter 3. JavaScript Basics
Chapter 4. JavaScript Objects and Functions
Chapter 5. JavaScript in the Browser
Chapter 6. JSON
Chapter 7. AJAX
Chapter 8. Websockets
Chapter 9. Intro to JQuery Framework
Chapter 10. Intro to Ext JS Framework
Chapter 11. Test-Driven Development with JavaScript
Chapter 12. Save The Children: Working with the Data on the server
Chapter 13. Securing Web Applications

Part 2. Going Mobile

Chapter 14. Responsive Design: One Site Fits All
Chapter 15. Intro to JQuery Mobile framework
Chapter 16. Save The Children. Take 1.
Chapter 17. Intro to Sencha Touch framework
Chapter 18. Save The Children. Take 2.
Chapter 19. Accessing Native API with PhoneGap

We may include another chapter on going cloud. Did we miss any subjects useful for the enterprise developers? Your feedback is appreciated.

8 thoughts on “Time to Write a new Book: Enterprise HTML5 and Going Mobile

  1. May be you miss this topics:
    – Canvas and SVG
    – Multimedia objects: audio, video, geolocation
    – Web storages and Web SQL databases
    – Cache manifest
    – Web workers

    or it’s not intresting for enterprise?

    1. Vitaly,

      You’ve listed the right topics, but we’ll try to cover whatever is the most practical for the enterprises. After we’ll write the spec for this Web site/application it’ll be clearer what to cover.


    1. It’s rather Modern Enterprise Web Development, but if HTML5 won’t be in the title, it’ll sell less copies. Gotta play by the rules – five years ago Web 2.0 was the buzzword, and today it’s HTML5.

      I’ll try to keep the size of this book under 600 pages regardless of the number of chapters.

  2. 1. Consider going with 14-15 chapters at most. Most modern textbooks try to align a book to a semester in college and chapters to a week of study.
    2. Combine chapters 3 & 5 – This book should not be introducing JS but rather quickly dive into HTML5-related specifics.
    3. Consider adding a chapter on CSS3
    4. Switch to cover AJAX first, JSON next as more advanced/compact format compared to XML.
    5. Use of Eclipse or other IDEs for HTML5 development, other tools for HTML5 & JSON testing/validation.

  3. Because an enterprise apps may get complexe, how about a chapter on architecture ?
    While Flex is slowing down, it’s still relevant in Enterprise RIA.
    Among many factors which I can think of in favor of Flex, there is the Cairngorm 3 architecture and Parsley I use for desktop applications.
    Another subject may be the issues of the multi-screen application development (mobile, tablet, PC) : code sharing between multi-screen apps and beyond (ide and framworks sharing).

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s