1) Make sure your business logic and data are decoupled from the presentation so that you can be flexible in the presentation based on which device is rendering the page. 2) Create content service APIs to allow for greater flexibility in terms of the rendering client picking and choosing what content to grab.
On Jun 26, 10:42 am, JP <[email protected]> wrote: > On Jun 26, 9:16 am, OldAndInTheWay <[email protected]> wrote: > > > Google's various web sites/pages are perfect examples. They're light > > on graphics even for screens that are "normal" sized > > Yeah on the newer stuff perhaps more driven by their heavy use of > native JS/AJAX, than consideration for the mobile environment. With > Wave they seem to have put more emphasis on style (and consequently > heft). > > <opinion>The earlier you get over the "scalable" idea, the better. > Mobile and desktop/notebook environments are too different for such an > approach. You'll have to walk the mile and develop multiple > incarnations of your site(s) that are appropriate for each medium.</ > opinion> --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Android Discuss" 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/android-discuss?hl=en -~----------~----~----~----~------~----~------~--~---
