All of the normal apps you would get when you buy a new computer or smartphone. Email, calendar, maps, news reader, word processor. Technologies would include things like css transforms, transitions, animations, application cache, indexeddb, file api, canvas, video, full screen... the things that make web apps feel like apps and not web pages.
Gmail, Calendar, Maps, Reader, Google News, and Google Docs aren't enough?
What do CSS transforms have to do with making an app feel like an app? They all work full screen, or you can open them windowed, with no chrome controls. They don't need local file access (though many use it) because they're beginning to store files in Drive. Some of the apps may already use appcache to speed up startup.
> Gmail, Calendar, Maps, Reader, Google News, and Google Docs aren't enough?
No, they're not. Aside from Maps using WebGL, I don't believe any of those are using anything that can reasonably called "cutting edge", and most of them are relatively unchanged in the last 5 years. Since Google wants developers to built for Chrome, and wants users, companies, and educators to spend money on Chrome, they should show that they themselves are dedicated to Chrome as well. The first party app support is equivalent to releasing Android without a Gmail app, but a shortcut to the browser version.
Huh? Gmail is the Chrome app. There will never be a separate Chrome version of Gmail. Over time Gmail is using more HTML5 features, but those work on other browsers too.
