Also you can get opera mobile emu for pc or mac :) http://my.opera.com/chooseopera/blog/2010/04/22/get-the-opera-mobile-emulator-on-your-mac-or-pc
and the info for the Samsung Emu is here (think this is the appropriate link for what Tee mentioned) http://innovator.samsungmobile.com/galaxyTab.do#02 - S On 7 January 2011 17:21, tee <[email protected]> wrote: > > > On mobile strategy: > > Bruce Lawson > > <http://dev.opera.com/articles/view/the-mobile-web-optimization-guide/> > > [Personally, I think media queries is the way to go.] > > > Media Queries for Mobile Web is nothing but kool-aid nevertheless :-) I > admit though, I <i>drink</i> it very often. > > http://tripleodeon.com/2010/10/not-a-mobile-web-merely-a-320px-wide-one/ > http://www.cloudfour.com/css-media-query-for-mobile-is-fools-gold/ > > > > On Jan 6, 2011, at 8:10 PM, Mike Kear wrote: > > > [A] a link at the top of the normal page, linking to a mobile version of > the page. (yuk) > > [B] javascript detection (but there are thousands of mobile devices > to detect. YUK ) > > [C] Use CSS @media handheld (but many mobile phones don't support the > handheld media type ) > > [D] server side detection using CGI.User_Agent (but there are so many > user agents to detect) > > [E] screen resolution detection (but is that reliable?) > > > IMHO, you should evaluate each option on case by case basic, for small > brochure site or a weblog, Media Queries would be the answer; for sites that > are heavy with many variations such as NYTimes, BBC, Amazon and other > eCommerce sites, serve side detection with content negotiation/adaption is > the way to go - and for this, Mobile First approach may not be the > one-and-end-all answer. > > On a not so related note, I was following closely the touchscreen devices > that manufacturers showcase at CES (2011 International Consumer Electronics > Show) as I wanted to get a better idea what widths I should take into > consideration for a mobile website I was building. > > Speaking of Mobile Web, do you consider iPad, Samsung Galaxy alike the > mobile devices? Should you treat the site on these devices desktop or > mobile version? iPad could be easier long as the touchscreen issue are taken > care of, but for devices that the widths are smaller than iPad wider than > 320 x 480, do you give it mobile version or desktop version? Media Queries > could be the best answer, yet one needs to be reminded that these devices > are sold by wireless carriers that uses 3G or 4G network (I am curious if > they are to be used as giant mobile phone as well), and therefore there is > bandwidth and cost concerns too. > > By the way, for those who are unaware of, you can download Samsung Galaxy > simulator as a Andriod 3rd party add-on. Not sure if it's the first version > though (too many bugs!), it runs very slow on my machine. > > tee > > ******************************************************************* > List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm > Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm > Help: [email protected] > ******************************************************************* > > ******************************************************************* List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [email protected] *******************************************************************
