Hi house,
Just finished the code construction phase of Web app for a services my company is about to launch. I used Ajax extensively for major functionality of this app. Testing the app now on mobile it horrible. The key press event I used to disable alpha characters still working on chrome, worst of it all.. Is opera mini. It doesn't even load the Ajax at all.. I switched away from data saving still same..


Expert opinion only.
Thanks in advance

Rubyist:
Hi house,
Just finished the code construction phase of Web app for a services my company is about to launch. I used Ajax extensively for major functionality of this app. Testing the app now on mobile it horrible. The key press event I used to disable alpha characters still working on chrome, worst of it all.. Is opera mini. It doesn't even load the Ajax at all.. I switched away from data saving still same..


Expert opinion only.
Thanks in advance

Opera mini gives developers headache so I am not surprised

Most mobile browsers (except those that tend to allow desktop experience) strip down features so at the end of the day, lot's of functionalities of a website are lost.



You can try browser detection techniques and taking appropriate actions.

@ Rubyist
its not a bug, its the way operamini was intentionally designed. how do you think operamini is able to achieve its amazing data saving rates? the browser doesnt load contents from your server directly, it routes its requests through opera's dedicated proxy server, the proxy loads the response, after which it performs some novel page compression, scripts downgrading, content reincarnation. the response is what you see on your phone. the rules of script downgrade include replacing ajax's "async" with something less useful. this is done to prevent ajax galleries, background services and dynamic DOM mutilation - all of these which would be useless since the proxy usually already alters content so much so that document appears very different in browser.
.
I Hope the mystery is a bit unravelled now

Olyboy16:
@ Rubyist
its not a bug, its the way operamini was intentionally designed. how do you think operamini is able to achieve its amazing data saving rates? the browser doesnt load contents from your server directly, it routes its requests through opera's dedicated proxy server, the proxy loads the response, after which it performs some novel page compression, scripts downgrading, content reincarnation. the response is what you see on your phone. the rules of script downgrade include replacing ajax's "async" with something less useful. this is done to prevent ajax galleries, background services and dynamic DOM mutilation - all of these which would be useless since the proxy usually already alters content so much so that document appears very different in browser.
.
I Hope the mystery is a bit unravelled now

Bro thanks alot, so much appreciate this. What do u think can be the solution. I am thinking browser detection and reduce Ajax usage

Rubyist:

What do u think can be the solution. I am thinking browser detection and reduce Ajax usage

dont reduce ajax usage, instead design your app to in a way that it doesnt rely heavily on ajax(improving code design, not reducing service quality, hope u get this?). i do advice coders not to be too trigger-happy with ajax; over-usage of ajax may result in rough backend codes in the hands of a less experienced developer; and unless u're a very talented web developer, you wont like the results of your segregated client js codes in the long run.
.
simply ensure the core functionality of your webpages doesnt rely heavily on ajax...that way, you wont have to work through unnecessary headache of browser detection and adaptation.
.
you can work with these rules
1. content first, chrome later. (study twitter.com)
2. your js should be useful and useful only. (dont write js for fun and show-off)
3. and off-course...avoid reinventing the wheel. use frameworks!
.
u can add yours

Olyboy16:


dont reduce ajax usage, instead design your app to in a way that it doesnt rely heavily on ajax(improving code design, not reducing service quality, hope u get this?). i do advice coders not to be too trigger-happy with ajax; over-usage of ajax may result in rough backend codes in the hands of a less experienced developer; and unless u're a very talented web developer, you wont like the results of your segregated client js codes in the long run.
.
simply ensure the core functionality of your webpages doesnt rely heavily on ajax...that way, you wont have to work through unnecessary headache of browser detection and adaptation.
.
you can work with these rules
1. content first, chrome later. (study twitter.com)
2. your js should be useful and useful only. (dont write js for fun and show-off)
3. and off-course...avoid reinventing the wheel. use frameworks!
.
u can add yours

Hello, pls can you contact me with the number on my sig?

ypeace:


Hello, pls can you contact me with the number on my sig?

i would contact you but i don't wana make that promise cos i might get carried away with something else (i'm sorry), but i'm an active email and telegram user (alphageek@southernwellslimited.com, @adedamy)

In addition, I'd like to state that you should not sacrifice your functionality for compatibility.

It's good practice to always use links (...'a' tags) and overriding default browser behavior in javascript than letting a non-hyperlink element clickable via js.

If you are too far down your dev-cycle to change your code, a simple redirect will suffice for non-js browsers.


I feel Nairaland should have syntax highlighting for codes. It's mature enough