@Palo G.: I agree that there battery consumption on mobile devices is an issue and I wasn't actually referring to "traditional" web-applications. However there are some special use cases (scientific field) where it does make sense to use the available computational potential of the client machines (which are idle most of the time). In these special use cases mobile devices only play a minor role. I also think that to some extend there is no way around having separate implementations of parts of the application for different devices. At a minimum different view implementations are necessary in order to cope with different screen sizes. Take the mobilewebapp from the last I/O as an example. Theoretically one could have a fallback mode for mobile devices where the algorithm is run on the server.
-- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To view this discussion on the web visit https://groups.google.com/d/msg/google-web-toolkit/-/btvMiTvWERsJ. 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.
