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

[DA-LION-619]

When front end devs fight
/grabs popcorn

 

[[)roi(]]

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.

No worries, apologies for the confusion. I did quite a bit of work in that space, a few years back, primarily in the backend switching of transactions (inter-client / inter-bank) hence I used the term pennings (seemed to be quite a common term for that sector).

Personally I'd hate to have to support old tech: the testing alone must be a nightmare; just how many devices do your QA teams have to keep in stock?

Thankfully most of my clients are using iStuff so standards support and upgrades are common place; have some Android users, but fortunately nothing that can't be hit with 4+

 

[[)roi(]]

When front end devs fight
/grabs popcorn

you missed something http://www.badum-tish.com

 

[kanzen]

No worries, apologies for the confusion. I did quite a bit of work in that space, a few years back, primarily in the backend switching of transactions (inter-client / inter-bank) hence I used the term pennings (seemed to be quite a common term for that sector).

Personally I'd hate to have to support old tech: the testing alone must be a nightmare; just how many devices do your QA teams have to keep in stock?

Thankfully most of my clients are using iStuff so standards support and upgrades are common place; have some Android users, but fortunately nothing that can't be hit with 4+

We set up the frontend to work as a mule for an XML web service so it's very basic. Every button is linked a server request (may sound a bit much) but it works well. The QA team actually only tests on the web version because of how well it was setup to begin with. Think of it as a prettier version of USSD. The USSD app is Java based and uses the exact same XML as the mobile site.

All the freelance work I do is for the latest tech so I can see why you chose so wisely. If a client mentions legacy IE support I tell them so take a hike

 

[[)roi(]]

We set up the frontend to work as a mule for an XML web service so it's very basic. Every button is linked a server request (may sound a bit much) but it works well. The QA team actually only tests on the web version because of how well it was setup to begin with. Think of it as a prettier version of USSD. The USSD app is Java based and uses the exact same XML as the mobile site.

All the freelance work I do is for the latest tech so I can see why you chose so wisely. If a client mentions legacy IE support I tell them so take a hike

Yeah you can't get too complicated with the old stuff, simple is often the only way.

Lol, now that sounds like me; long past the need to chase clients for work; they either take the solution I propose or go elsewhere.

FYI for testing I reverted to using Travis primarily for the CI bits; most of the devices hooked up and technical testing by in large is automated, barring the final UX bit. Similar for you?

 

[kanzen]

Yeah you can't get too complicated with the old stuff, simple is often the only way.

Lol, now that sounds like me; long past the need to chase clients for work; they either take the solution I propose or go elsewhere.

They never like the solution to use something else or to upgrade to a browser that's more relevant. They spend millions paying for development work on legacy browsers that could have been used to upgrade their office PCs still using old browsers.

Distell still makes me develop their product websites to support IE7 I'm considering saying no, but they really do fork out enough to keep me quiet.

 

[[)roi(]]

They never like the solution to use something else or to upgrade to a browser that's more relevant. They spend millions paying for development work on legacy browsers that could have been used to upgrade their office PCs still using old browsers.

Distell still makes me develop their product websites to support IE7 I'm considering saying no, but they really do fork out enough to keep me quiet.

Yeah some of my corporates still have Windows XP running in the POS area; I generally steer clear of new developments; although I have been known to fund an extended holiday or two off the back of a "quick and dirty".

As they say, even in the middle ages, there was money to be made in shovelling turds; with a nose plug you hardly notice it .

 

[Pixelbender]

Please don't stop my from zooming whenever I want. Surpressing viewport soom is not an option....

Just make the fields text size 16px or 1em or 12pt. please, it's simple. Why stop people from what they want to do instead of using a simple css class?

 

[[)roi(]]

Please don't stop my from zooming whenever I want. Surpressing viewport soom is not an option....

Just make the fields text size 16px or 1em or 12pt. please, it's simple. Why stop people from what they want to do instead of using a simple css class?

Thanks for the clarification. Yip taking the easy way out is never good. Pinch to zoom should not have to be sacrificed when standardising for DPI.