Mobile Browser Compatibility
Mobile Browser Compatibility
am 12.09.2007 18:58:46 von Paul Furman
What is needed for mobile browser compatibility? This is in regards to
Google ads. It seems the page in my sig just needs to be able to
reformat the table listing for each item into a stacked list rather than
the wide table, everything else will scrinch down to a tiny window and
there already is an option to turn off the long descriptions and
associated images or are images already turned off?
--
Paul Furman
Bay Natives Nursery
http://www.baynatives.com
Re: Mobile Browser Compatibility
am 12.09.2007 19:11:23 von TravisNewbury
On Sep 12, 12:58 pm, Paul Furman wrote:
> What is needed for mobile browser compatibility?
> Bay Natives Nurseryhttp://www.baynatives.com
You need to get a color wheel and choose colors that match for your
site. The green and the yellow do not compliment each other.
Try changing the yellow to one of these:
#dbdbb7
#cccc99
#dbc9b7
#b7c9db
Those are a few complimentary colors that match the green you choose.
Re: Mobile Browser Compatibility
am 12.09.2007 19:14:45 von Shion
Paul Furman wrote:
> What is needed for mobile browser compatibility? This is in regards to
> Google ads. It seems the page in my sig just needs to be able to
> reformat the table listing for each item into a stacked list rather than
> the wide table, everything else will scrinch down to a tiny window and
> there already is an option to turn off the long descriptions and
> associated images or are images already turned off?
Depends on which mobiles you want to support, we can make a simple definition
of mobile browsers, group 1 that supports wml only and group 2 xhtml browsers.
The 2nd group is quite similar to browser xhtml, but is a lot less forgiving
for microsoft type of coding (open tags may make the page not work at all,
even cause the mobile browser to crash).
The 1st group don't support much, only 2bit images, in best case and no clue
about things you have in xhtml.
You should check the cellular phone model and adjust the code to a level which
it will manage, or make the page so simple that any cellular should be able to
understand all the tags.
I can say I'm quite bored of mobile browser compatibility and would be happy
if I hadn't to care about those, but work is work...
--
//Aho
Re: Mobile Browser Compatibility
am 12.09.2007 19:40:55 von Paul Furman
Travis Newbury wrote:
> Paul Furman wrote:
>
>>What is needed for mobile browser compatibility?
>>Bay Natives Nursery http://www.baynatives.com
>
> You need to get a color wheel and choose colors that match for your
> site. The green and the yellow do not compliment each other.
>
> Try changing the yellow to one of these:
>
> #dbdbb7
That's possible... very similar to the beige we also use. I kind of like
it to have a little more life though, not tooo tasteful. Besides that
comes out as gray in 'web colors' and the yellow holds perfectly.
> #cccc99
I've already got that beige for 'shaded' items.
> #dbc9b7
Dirty pink???
> #b7c9db
Dirty baby blue is too cold, we like the warm friendly happy soft
yellow. This one does look nice if I needed another color though.
> Those are a few complimentary colors that match the green you choose.
The yellow isn't complimentary (opposite on the color wheel).
--
Paul Furman Photography
http://edgehill.net
Bay Natives Nursery
http://www.baynatives.com
Re: Mobile Browser Compatibility
am 12.09.2007 19:42:21 von Paul Furman
J.O. Aho wrote:
> Paul Furman wrote:
>
>>What is needed for mobile browser compatibility? This is in regards to
>>Google ads. It seems the page in my sig just needs to be able to
>>reformat the table listing for each item into a stacked list rather than
>>the wide table, everything else will scrinch down to a tiny window and
>>there already is an option to turn off the long descriptions and
>>associated images or are images already turned off?
>
> Depends on which mobiles you want to support, we can make a simple definition
> of mobile browsers, group 1 that supports wml only and group 2 xhtml browsers.
>
> The 2nd group is quite similar to browser xhtml, but is a lot less forgiving
> for microsoft type of coding (open tags may make the page not work at all,
> even cause the mobile browser to crash).
>
> The 1st group don't support much, only 2bit images, in best case and no clue
> about things you have in xhtml.
>
> You should check the cellular phone model and adjust the code to a level which
> it will manage, or make the page so simple that any cellular should be able to
> understand all the tags.
>
> I can say I'm quite bored of mobile browser compatibility and would be happy
> if I hadn't to care about those, but work is work...
Ow, sounds like a mess. It's not that important to us really. Is there
maybe a simulator to see what it would look like?
--
Paul Furman Photography
http://edgehill.net
Bay Natives Nursery
http://www.baynatives.com
Re: Mobile Browser Compatibility
am 12.09.2007 19:46:27 von a.nony.mous
Paul Furman wrote:
> What is needed for mobile browser compatibility? This is in regards to
> Google ads. It seems the page in my sig
Google ads? I don't see any google ads on the page in your sig (now
snipped because it was in your sig).
> just needs to be able to reformat the table listing for each item into
> a stacked list rather than the wide table, everything else will
> scrinch down to a tiny window and there already is an option to turn
> off the long descriptions and associated images or are images already
> turned off?
I looked at the page with Opera (press Shift-F11) and it works fine in
that pseudo-display. Could you phrase your question better? I am not
sure what you want.
If it were my site, I would not have such a loooong main page that takes
awhile to load. I would list links of Categories, each to a separate
page of particular plants fitting that category. There seems to be about
70
s of plants, well beyond convenient scrolling/reading.
--
-bts
-Motorcycles defy gravity; cars just suck
Re: Mobile Browser Compatibility
am 12.09.2007 19:59:00 von Shion
Paul Furman wrote:
> J.O. Aho wrote:
>> Paul Furman wrote:
>>
>>> What is needed for mobile browser compatibility? This is in regards to
>>> Google ads. It seems the page in my sig just needs to be able to
>>> reformat the table listing for each item into a stacked list rather than
>>> the wide table, everything else will scrinch down to a tiny window and
>>> there already is an option to turn off the long descriptions and
>>> associated images or are images already turned off?
>>
>> Depends on which mobiles you want to support, we can make a simple
>> definition
>> of mobile browsers, group 1 that supports wml only and group 2 xhtml
>> browsers.
>>
>> The 2nd group is quite similar to browser xhtml, but is a lot less
>> forgiving
>> for microsoft type of coding (open tags may make the page not work at
>> all,
>> even cause the mobile browser to crash).
>>
>> The 1st group don't support much, only 2bit images, in best case and
>> no clue
>> about things you have in xhtml.
>>
>> You should check the cellular phone model and adjust the code to a
>> level which
>> it will manage, or make the page so simple that any cellular should be
>> able to
>> understand all the tags.
>>
>> I can say I'm quite bored of mobile browser compatibility and would be
>> happy
>> if I hadn't to care about those, but work is work...
>
> Ow, sounds like a mess. It's not that important to us really. Is there
> maybe a simulator to see what it would look like?
There are tools, most of them are written for one phone, but CS3 has module
for quite many phones. But I do mainly my "testing" on browser and when at the
final stage with the real mobile phones, as tools usually are more forgiving
than the real things.
--
//Aho
Re: Mobile Browser Compatibility
am 12.09.2007 20:19:43 von Paul Furman
Beauregard T. Shagnasty wrote:
> Paul Furman wrote:
>
>>What is needed for mobile browser compatibility? This is in regards to
>>Google ads. It seems the page in my sig
>
> Google ads? I don't see any google ads on the page in your sig (now
> snipped because it was in your sig).
The goal is to qualify for advertising through google in their mobile
compatible listings. I never click the things but I guess people do. In
fact I've got them blocked, I can't even see them.
>>just needs to be able to reformat the table listing for each item into
>>a stacked list rather than the wide table, everything else will
>>scrinch down to a tiny window and there already is an option to turn
>>off the long descriptions and associated images or are images already
>>turned off?
>
> I looked at the page with Opera (press Shift-F11) and it works fine in
> that pseudo-display.
OK thanks. Assuming you are talking about a stripped down text only version.
> Could you phrase your question better? I am not
> sure what you want.
http://www.google.com/mobile/
http://services.google.com/adwords/mobile_ads?hl=en
They don't describe much there but we got this email:
> We are happy to announce a new feature that will allow you to
> easily reach additional qualified customers who are searching
> Google from their mobile phones.
>
> In the next few days, your search ads will be eligible to run on
> Google Mobile Search pages (like they currently do on Google.com).
> We are offering this feature - and any resulting clicks - for
> free through November 18, so you can experiment with the rapidly
> growing mobile platform while still reaching qualified customers.
>
> Each ad's eligibility will be determined by its landing page and
> only ads with landing pages that can be adapted for viewing on
> mobile browsers will be shown. You can monitor each ad's
>
> performance via a special performance tracking page within your
> account called "Performance Data: Search Ads on Google Mobile
> Search."
> If it were my site, I would not have such a loooong main page that takes
> awhile to load. I would list links of Categories, each to a separate
> page of particular plants fitting that category. There seems to be about
> 70
s of plants, well beyond convenient scrolling/reading.
Yes, it is a bear to load but at least you can start reading from the
top. Loading the full list is really a killer, the opening page is just
featured plants. Re-reading that email above, I think you are right, the
landing page will be way too large to be compatible.
--
Paul Furman Photography
http://edgehill.net
Bay Natives Nursery
http://www.baynatives.com
Re: Mobile Browser Compatibility
am 12.09.2007 20:43:29 von Bergamot
Travis Newbury wrote:
> On Sep 12, 12:58 pm, Paul Furman wrote:
>> http://www.baynatives.com
>
> You need to get a color wheel and choose colors that match for your
> site. The green and the yellow do not compliment each other.
Actually they do, using an analogic color scheme with the green as the
base. That yellow is around 60 degrees from the green, with a blue-gray
as the 3rd color. Likewise the two can come up in a split complement
scheme with a pinkish purple base. So there. :)
I love color wheels. :-)
--
Berg
Re: Mobile Browser Compatibility
am 12.09.2007 21:33:33 von a.nony.mous
Paul Furman wrote:
> Beauregard T. Shagnasty wrote:
>> Paul Furman wrote:
>>> What is needed for mobile browser compatibility? This is in regards
>>> to Google ads. It seems the page in my sig
>>
>> Google ads? I don't see any google ads on the page in your sig (now
>> snipped because it was in your sig).
>
> The goal is to qualify for advertising through google in their mobile
> compatible listings. I never click the things but I guess people do.
> In fact I've got them blocked, I can't even see them.
So do I (block them), but I looked through your source for them; found
none.
>> I looked at the page with Opera (press Shift-F11) and it works fine
>> in that pseudo-display.
>
> OK thanks. Assuming you are talking about a stripped down text only
> version.
Of Opera? No, the latest graphical version 9.23. Load your page and
press Shift-F11.
>> If it were my site, I would not have such a loooong main page that
>> takes awhile to load. I would list links of Categories, each to a
>> separate page of particular plants fitting that category. There
>> seems to be about 70 s of plants, well beyond convenient
>> scrolling/reading.
>
> Yes, it is a bear to load but at least you can start reading from the
> top. Loading the full list is really a killer, the opening page is
> just featured plants. Re-reading that email above, I think you are
> right, the landing page will be way too large to be compatible.
People not on broadband will get jerky scrolling if they try to start
reading while it is still loading.
According to: http://www.websiteoptimization.com/services/analyze/
your page is currently 493238 bytes (!), and will require two minutes or
more for someone on a (really good) dialup connection.
--
-bts
-Motorcycles defy gravity; cars just suck