16px or I'll leave your site...

[Pixelbender]

There's nothing more annoying than when you're on mobile and trying to login to or register on a sitee and every time you select the field to enter your details, starting to type and the damn page zooms (however so slowly) and you click other links or banners unintentionally.

This will make me leave your site, unless you're gmail or a site i can't live without. So please, make your field/textarea text at least 16px and you won't have this issue.

Especially if you think or brag about your site being mobile optimized.

 

[Thor]

There's nothing more annoying than when you're on mobile and trying to login to or register on a sitee and every time you select the field to enter your details, starting to type and the damn page zooms (however so slowly) and you click other links or banners unintentionally.

This will make me leave your site, unless you're gmail or a site i can't live without. So please, make your field/textarea text at least 16px and you won't have this issue.

Especially if you think or brag about your site being mobile optimized.

Random rant.

Note taken regardless. Did not know this was pixel related. Then again my default html is 16px and then I rem it from there from there so never noticed it.

 

[[)roi(]]

Way too small.

iPhone Human Interface Guidelines recommends a minimum target size of 44 pixels wide 44 pixels tall.

 

[kanzen]

This HTML tag should prevent the zoom from happening

<meta name="viewport" content="width=device-width, user-scalable=no" />

They should be implementing that for mobile devices.

 

[Thor]

This HTML tag should prevent the zoom from happening

<meta name="viewport" content="width=device-width, user-scalable=no" />

They should be implementing that for mobile devices.

This what I do yes, was to afriad to say it cause I was scared I'm wrong.

 

[[)roi(]]

This HTML tag should prevent the zoom from happening

<meta name="viewport" content="width=device-width, user-scalable=no" />

They should be implementing that for mobile devices.

That is the most irritating thing to do; screwing with expected mobile UX behaviors is a sign of a lazy programmer.

 

[Thor]

That is the most irritating thing to do; screwing with expected mobile UX behaviors is a sign of a lazy programmer.

Mine looks like this:


<meta name="viewport" content="width=device-width, initial-scale=1">

 

[Darko]

That is the most irritating thing to do; screwing with expected mobile UX behaviors is a sign of a lazy programmer.

Not really sure what you're implying here. The viewport meta tag just stretches the viewport to the device width. It has got nothing to do with laziness.

 

[Darko]

Way too small.

Those guidelines are for navigation icons / buttons and not text size.

 

[[)roi(]]

Those guidelines are for navigation icons / buttons and not text size.

Point size != pixel size
It's still a touch zone: translation between point size vs. pixel size is still relevant re varying DPI

 

[kanzen]

That is the most irritating thing to do; screwing with expected mobile UX behaviors is a sign of a lazy programmer.

How do you suppose you would correct this on a feature phone that doesn't support javascript and has limited CSS support?

 

[[)roi(]]

How do you suppose you would correct this on a feature phone that doesn't support javascript and has limited CSS support?

Obviously you wouldn't, but those phone are far greater issues than textfield sizes. Guess it really depends on the customer segment to trying to pitch to; I certainly don't bother to build for that.

 

[kanzen]

Obviously you wouldn't, but those phone are far greater issues than textfield sizes. Guess it really depends on the customer segment to trying to pitch to; I certainly don't bother to build for that.

Now that's being lazy

 

[[)roi(]]

Not really sure what you're implying here. The viewport meta tag just stretches the viewport to the device width. It has got nothing to do with laziness.

Sorry missed your reply. It deactivates pinch to zoom, an expected behaviour for a mobile browser.
http://www.iheni.com/mobile-accessibility-tip-dont-suppress-pinch-zoom/

 

[[)roi(]]

Now that's being lazy

Really if that's the market segment you're focusing on, then you're used to doing a lot of work for pennies.

Ps. it's not laziness, I just pick my clients well, can't be bothered "panel beating" for old devices.

 

[kanzen]

Really if that's the market segment you're focusing on, then you're used to doing a lot of work for pennies.

Ps. it's not laziness, I just pick my clients well, can't be bothered "panel beating" for old devices.

I deal with financial products for African countries and I can tell you now, I don't earn pennies. You're making an assumption that it's lazy, but you know very well that it works.

If you really want to backup your argument you would provide a better solution instead of making the assumption that it's lazy. There's a reason why it's there.

Stick to your bootstrap templates or provide constructive feedback.

 

[[)roi(]]

I deal with financial products for African countries and I can tell you now, I don't earn pennies. You're making an assumption that it's lazy, but you know very well that it works.

If you really want to backup your argument you would provide a better solution instead of making the assumption that it's lazy. There's a reason why it's there.

Stick to your bootstrap templates or provide constructive feedback.

Lol you've surely heard about an argument and making it personal...

Back to the argument:
You based your standards on old devices, and that's probably your clients. The penny argument which you missed is in reference to the customer segment and not your income (I don't care either way). e.g. Your client's business is probably something like micro-lending, micro-payments i.e. penny transactions.

Designing the internet around the lowest common denominator is foolish; nobody but the penny chasers are doing this, hence adjusting for user experience it's not considered good practice to fix elements by pixel size, because unless you're in the penny game, the stats show a significantly large enough pool is covered by JS, CSS and the like.

My corporate clients upgrade their mobile devices on a 2 year cycle, and many of these receive software upgrades i.e. it's ok to ignore the guy in Kenya with an old Nokia.

 

[kanzen]

Lol you've surely heard about an argument and making it personal...

Back to the argument:
You based your standards on old devices, and that's probably your clients. The penny argument which you missed is in reference to the customer segment and not your income (I don't care either way). e.g. Your client's business is probably something like micro-lending, micro-payments i.e. penny transactions.

Designing the internet around the lowest common denominator is foolish; nobody but the penny chasers are doing this, hence adjusting for user experience it's not considered good practice to fix elements by pixel size, because unless your in the penny game, the stats show a significantly large enough pool is covered by JS, CSS and the like.

My corporate clients upgrade their mobile devices on a 2 year cycle, and many of these receive software upgrades i.e. it's ok to ignore the guy in Kenya with an old Nokia.

Thank you for clarifying that.

If only you had a real idea of the earnings in my segment you would understand that it's a LOT more than you're thinking. Most of our customers don't have bank accounts and this allows us to take advantage of that market. If $15million in revenue is pennies then we differ on that matter. We basically provide the tools for tellers to transact so that people can move money around.

I understand your market is different, but that hasn't stopped agencies and development houses around South Africa from developing for lower end devices. Personally, I would prefer to not support those devices but it's a reality in this country.

Agencies I've worked for (one of them was Digitas LBi) have always used that method and it has worked wonders every time. All I really want to say is that the tag would have made a difference and there's no denying that...even if it is the bare minimum.

 

[kanzen]

Mine looks like this:


<meta name="viewport" content="width=device-width, initial-scale=1">

Your method is actually a better alternative. This works better for screen rotation.

 

[Thor]

Your method is actually a better alternative. This works better for screen rotation.

I know