Mime-Version:
1.0 (Apple Message framework v1076)
Content-Type:
text/plain; charset=us-ascii; format=flowed; delsp=yes
Date:
Mon, 21 Sep 2009 10:18:03 -0500
Content-Transfer-Encoding:
7bit
|
This is where solutions like MIT's (m.mit.edu) shine so well. By
presenting a tiered design that replicates basic functionality across
a range of phones in the format that fits each phone best.
-Drew
On Sep 17, 2009, at 1:50 PM, Sara Hurley wrote:
> That's something I actually want to talk about sometime - one thing
> I've been concerned with as we do a redesign at SPH (getting us all
> on the same page, technology and design-wise) is that phones have
> such a range of support for how web pages are navigated and what
> they do, and from what I've tried on my corner of SPH in the past
> has looked good in some simple browsers (like on my truly awful
> phone), but is way too simple for an iPhone interface - and the
> mobile stylesheet in whatever form it exists in becomes the style
> sheet even for phones, like the iPhone, that do a great job of
> letting people browse the web as it exists for desktops.
>
> Does this make any sense? It's something I've been struggling with
> in my head - what the optimal compromise is for those style sheets.
>
> S
>
> Zachary Johnson wrote:
>> If we're going to have a group meeting themed around Mobile Web I'd
>> be happy to go over some of my notes on making websites mobile
>> friendly through source code ordering that I talked about a bit two
>> years ago at MinneWebcon.
>>
>> Zach
>
> --
> --
>
> Sara Hurley, MFA
> 612-625-7709
>
> Web Coordinator
> http://cpheo.sph.umn.edu
> Digital Learning Group (DLG)
> School of Public Health
> University of Minnesota
|
|
|