I have one app in which users may go entire sessions without accessing some places (I use Places & Activities pattern), and in such cases code-splitting helps a lot. I have another app, in which users are expected to visit all places. In this case code-splitting helps to reduce the initial load, but ultimately the entire compiled code has to be loaded. It is not a big deal for desktop apps (assuming good connection speeds), but I was planning to use GWT for mobile versions of these apps, and the compiled size scares me. So far it looks to me that GWT is not the right choice for a mobile app. I hope to be convinced otherwise. A native app with the same functionality will be many times smaller, but it's a lot of extra work to write a native app for each mobile platform.
-- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
