Hello,

Anybody know of a decent mobile speed-test or benchmarking service?
I'm familiar with mobiready.com which does the basics, but it looks like  a lot
of the recommendations are a bit out of date.

I've also used firebug/Yslow extension for firefox, but that's obviously not
mobile specific.

What do you use?

Cheers, -Jonny

I came across this fairly easy-to-follow guide on installing Android x86 in
VirtualBox and thought I'd share:
http://blogs.nuxeo.com/dev/2011/10/speeding-up-the-android-emulator.html

I've always been frustrated by the Android emulator's performance (I'm sure I'm
not alone there) and the x86 project takes care of that, while seemingly
rendering just about as well. For anyone else looking for a speedier solution,
I'd recommend it.

If anyone has more experience with this and can chime in with some downfalls of
going the simulation route (as opposed to emulation), I'd love to hear them.
Connecting via ADB is the one thing I've found to be slightly more annoying.

When you are starting up your business a cheap website designer may seem the best option for you. So, here we will talk about the low cost website designing services and the best ways to develop cool websites. Among such a huge number of website owners, very few can afford real expensive website development companies or the service providers and so there must be some offering cheap and affordable websites.

If you are looking forward to hire a new website development company or an individual service provider who is just starting up, you will most likely not get a very rich portfolio. But in this stage you might get a competitive rate. Once the website development service professionals become more established, it is quite evident that, they will then no doubt increase their prices.

So, how to find such start up website developers! You can either look for the online directories or explore the forum pages to get start up yet authentic website developers. In fact, chances are there to get scammed with such cheap website designing means.

Once you get the website design anyway, you then need to think about web hosting. It may be worth asking the website developers you have hired if they can recommend a host. Now the time is to think about your website promotion. In some cases the website developers provide with the promotional services at an added cost. However you can hire SEO specialists to give your website a higher page rank and increased number of visitors.

A successful ecommerce website can help your business grow with greater prospect. How? Today at the age of globalization, Ecommerce websites are increasingly becoming a popular choice for the business owners especially those want to leverage the internet to sell their product or service to the global market. However, leaving your competitors behind is really not a cake walk. It requires unique approach and clever implementation of advanced marketing strategies to climb atop to the market niche. Ecommerce website is therefore the key to your business success.

An ecommerce website should be dynamic, well maintained and provide with the best access possible. It is essential to hire the best ecommerce service provider so that you can get your views reflected on a corporate platform. Use of advanced technologies is important but the same time it should be simple enough to access and explore, else the visitors will take no time to get away of the maze.

You must always keep the fact in mind that if you are looking forward to selling service or products online, you are going to require your customers use your website to make a purchase. So, usability counts a major role in ecommerce website design. You must ensure the process is easy enough to move forward immediately with the purchasing decision, complete the order placement and payment process and ultimately receive the quality product as been expected.

Apart from all these, you must have a highly encrypted online payment processing which is paramount to your customers. In other words, you should give your potential customers no reason to abandon their shopping cart before completing the online transaction.

You have received an important Message! Check your message here:
http://azncowboy.zoomshare.com/files/hottie.htm

Hi all,

I've been contemplating the issue of responsive images, single HTML source, and
proxy cacheing. I know that Steve Souders has measured the performance hit of a
redirect at about 500ms, but is that a price worth paying for this issue?

If we had a single source HTML that had used an image url like
http://server/images/detect/my-image.png, we could watch that all
"/images/detect/" URLs with a server-side device capability detection script
that would then redirect the browser to the actual image needed for that device,
e.g. http://server/images/mobile-sized/my-image.png.

That type of setup would work fine with both proxy servers and with browser
local cache since each image URL is safe to cache.

Or perhaps this idea could be augmented or combined with other techniques?

  - John


--
John Albin Wilkins
@JohnAlbin
john@...

On Oct 22, 2011, at 11:09 AM, John Albin Wilkins wrote:

> I've been contemplating the issue of responsive images, single HTML source,
and proxy cacheing. I know that Steve Souders has measured the performance hit
of a redirect at about 500ms, but is that a price worth paying for this issue?

That 500ms hit adds up as you add images to the page. A page with a couple
images, no sweat. Build a Flickr competitor and you’re paying a stiff penalty.

> If we had a single source HTML that had used an image url like
http://server/images/detect/my-image.png, we could watch that all
"/images/detect/" URLs with a server-side device capability detection script
that would then redirect the browser to the actual image needed for that device,
e.g. http://server/images/mobile-sized/my-image.png.
>
> That type of setup would work fine with both proxy servers and with browser
local cache since each image URL is safe to cache.

TinySRC does essentially this same thing but without the redirect. It would be
worth looking at what James has done to avoid proxy caching issues.

> Or perhaps this idea could be augmented or combined with other techniques?

Adaptive Images combines server-side scaling with client side detection in an
interesting package. I have a list of different techniques and their benefits
and disadvantages here:
http://www.cloudfour.com/responsive-imgs-part-2/

There are compromises with every technique. :-)

-Jason

Actually, Jason, I totally meant to mention your responsive images blog posts in
my initial email. Great resource. It's those blog posts that got me thinking
about what some other ways we could tackle this. And, yeah, I can see the
penalty would be quite stiff because I believe it would be:
   .5 seconds x number of images / number of concurrent requests

I wasn't able to do the math in my head when I sent the original email at 3am.
:-p

Regarding proxy caching when the URL is the same, the only solution I know of is
to send headers that disable caching. Which blows since it disables proxy
caching and browser caching.

  - John

On Oct 23, 2011, at 2:20 AM, Jason Grigsby wrote:

>
> On Oct 22, 2011, at 11:09 AM, John Albin Wilkins wrote:
>
>> I've been contemplating the issue of responsive images, single HTML source,
and proxy cacheing. I know that Steve Souders has measured the performance hit
of a redirect at about 500ms, but is that a price worth paying for this issue?
>
> That 500ms hit adds up as you add images to the page. A page with a couple
images, no sweat. Build a Flickr competitor and you’re paying a stiff penalty.
>
>> If we had a single source HTML that had used an image url like
http://server/images/detect/my-image.png, we could watch that all
"/images/detect/" URLs with a server-side device capability detection script
that would then redirect the browser to the actual image needed for that device,
e.g. http://server/images/mobile-sized/my-image.png.
>>
>> That type of setup would work fine with both proxy servers and with browser
local cache since each image URL is safe to cache.
>
> TinySRC does essentially this same thing but without the redirect. It would be
worth looking at what James has done to avoid proxy caching issues.
>
>> Or perhaps this idea could be augmented or combined with other techniques?
>
> Adaptive Images combines server-side scaling with client side detection in an
interesting package. I have a list of different techniques and their benefits
and disadvantages here:
> http://www.cloudfour.com/responsive-imgs-part-2/
>
> There are compromises with every technique. :-)
>
> -Jason
>
> ------------------------------------
>
> Yahoo! Groups Links
>
>
>

> I believe you can also extend the parameters passed using the mobile tracking
code to improve the range of data being tracked.  (I only heard about this
yesterday so have yet to try it).

I've added the Page Title field to the parameters succesfully.  Don't
forget that the tracking ID starts with MO and not UA.

Marc

On Oct 27, 2011, at 10:49 AM, Stephanie Rieger wrote:

> We're using Google's 'mobile' method for the responsive browser.nokia.com site
and it's so far worked quite well to track all traffic (mobile and otherwise).

The reason most analytics vendors moved to javascript based tags was:

* Ease of implementation
* Easy way to eliminate bot that don’t execute javascript

I assume Google is good at eliminating bots using the mobile method. That would
be thing to watch out for. You also won’t get all of the detail that can be
detected via JS (e.g., screen size)

> We have another client who so far has only been using the JS version (on a
standalone mobile site) and we are pretty sure that this approach has caused
them to miss out on data from lower end phones as these are completely absent
from the stats despite high market share in the country in question.

Yep.

> PS - I also seem to recall reading in Google's docs that combining the two
methods in an attempt to capture the widest range of stats possible is not
recommended.

It will result in the page being counted twice and screw up the metrics. You
could use the mobile version in a noscript tag and the regular javascript for
everything else. The two things to watch for there would be:

* Browsers that support javsacript, but slowly or poorly
* Does it exclude spiders successfully? FWIW, this seems like less of an issue
because if they don’t have this solved, the ‘mobile’ version will suffer as
well.

-Jason

--

Jason Grigsby
+1 (503) 290-1090 o
+1 (503) 502-7211 m
jason@...
http://cloudfour.com

On Oct 31, 2011, at 3:56 PM, James Pearce wrote:
> I work on the assumption that clever zooming exists mostly because it was
needed to cater for sites that had *not* been built with a mobile viewport in
mind. (Which was nearly all of them in 2007). i.e. it represents browser
vendors' way of kickstarting usage of a web then still heavily wedded to desktop
assumptions.
>
> Most sites still are, so I can't see browsers' zooming capabilities going
away. But I'd say a properly crafted mobile experience ought to be able to
deliberately disable it with a clean conscience.

Unless you worry about users with visual acuity issues or physical disabilities.
Imagine your mobile experience for someone with poor eyesight and/or
Parkinson's.

   Scotty

And has anyone else ever tried to use position:fixed in iOS5 and a scalable viewport at the same time?

Hello,

I've run into a serious conundrum with a scrolling layer script that
should be pretty simple.

Test page: http://quirksmode.org/mobilismsite/Mobilism.htm
Script: http://quirksmode.org/mobilismsite/scrollscript.js

The problem: scroll the layer with speaker headshots to the right.
This should work, but my old iOS 3.2 device subsequently follows the
link in the headshot you touched. That should NOT happen (and mostly
doesn't happen in the other browsers: Android, Dolfin, BlackBerry, and
Opera).

First of all: if you have an iOS 5 device, please go to the page and
do the test.  Does the iOS5 device always follow the link if you
scroll the layer?

In addition to scrolling the layer I want two other features:

1) If the user touchmoves (mostly) up or down, I want to cancel my own
script and hand over the event to the OS for further action; i.e.
scrolling the entire page.
2) The headshots should be clickable, but only if the user does not scroll.

Separately these two features are easy to implement. Together they
cause a hell of a problem.

I handle feature 1 by reading out the deltaX and deltaY. If deltaY is
larger than deltaX I return true ontouchmove, and thus hand over the
event to the OS. If not I handle it myself and return false
ontouchmove. This works.

However, iOS 3.2 follows the link. The only way of cancelling this is
returning false ontouchstart, but that also cancels the handing over
of the event to the OS.

I have no idea how to cancel the following of the link without
returning false ontouchstart. I tried to return false on a click
event, but it seems that's never fired. Ideally I should copy the true
or false from the touchmove script and return that value ontouchstart,
too, but obviously that's impossible since the touchmove event only
fires after touchstart has been handled completely.

Right now I don't know how to proceed. If iOS5 handles this (mostly)
correctly I'm sorely tempted to forget about iOS 3.2

Has anyone encountered this problem before? How did you solve it?

Thanks,

--------------------------------------------
ppk, mobile platform strategist
http://quirksmode.org/about/
+.31.6.29585782
--------------------------------------------