While he is talking about Java ME applications, what he describes really applies to (local) mobile applications in general, and not only to Java ME. The emphasis on focusing on highly usable, great user experience on the handset, and leveraging or pushing more complex functionality to the network while understanding and minimizing the cost of ownership is the way to architect and design mobile applications.
I describe mobile applications as occasionally connected, end-to-end applications, consumers of services on the web, but I really like the iceberg metaphor that Jason uses to explain not only where development takes place, but also explain the distribution of (quantify) the work related to developing mobile applications…
ceo
P.S. Jason, if you don't mind, I would like to borrow the iceberg metaphor for my own presentations :-)