Answer the question
In order to leave comments, you need to log in
JavaScript, jQuery and AJAX support in mobile browsers?
I am compiling a TOR for the development of a slider, an order / feedback form and a lightbox for a website using HTML5 and CSS3. With the definition of compatibility for desktops, everything is quite clear: support for IE9 + (IE8 - if only it is not too laborious to implement the functionality indicated in the TOR). With regard to mobile platforms and the browsers used on them, it is very difficult for me, to be honest, to determine the scope of compatibility of the site elements that I have previously designated due to the lack of knowledge in this area. Is there any relationship between the version of Android/iOS, the version of the mobile browser being used, and the functionality that can be implemented using JavaScript, jQuery, and AJAX? All this, of course, in relation to the beginning of 2017. That is, is it reasonable, for example, to designate compatibility in the TK, starting with Android 2.3, Or is it more reasonable to designate version 4.4 as the lower limit of compatibility? It is clear that both mobile platforms are developing much faster in relation to their older desktop counterparts, and for the most part, the latest versions of the browsers used by the user are installed on devices, with an eye, of course, to the OS version. However, it must be admitted that not everyone changes their devices every six months or a year, but they use what they purchased 3-5 years ago (that is, by now, the manufacturer of these devices has officially stopped supporting OS updates on these devices) . that both mobile platforms are developing much faster in relation to their older desktop counterparts and, for the most part, the latest versions of the browsers used by the user are installed on devices, with an eye, of course, to the OS version. However, it must be admitted that not everyone changes their devices every six months or a year, but they use what they purchased 3-5 years ago (that is, by now, the manufacturer of these devices has officially stopped supporting OS updates on these devices) . that both mobile platforms are developing much faster in relation to their older desktop counterparts and, for the most part, the latest versions of the browsers used by the user are installed on devices, with an eye, of course, to the OS version. However, it must be admitted that not everyone changes their devices every six months or a year, but they use what they purchased 3-5 years ago (that is, by now, the manufacturer of these devices has officially stopped supporting OS updates on these devices) .
Based on this, is there any methodology for determining the lower limit of compatibility of the solutions I need? Perhaps personal experience of specialists in this field?
Answer the question
In order to leave comments, you need to log in
1. Find statistics on the prevalence of android versions, such as this , but preferably for your region or target audience.
2. Decide for yourself whether you are ready to lose 13% of the audience (or more, depending on which target audience) by setting the lower bar at 4.4 or you can pay extra.
3. Check with the developers how difficult it is for them to implement support for 2.x, compare this with the expected profit from the extra 13%.
Also, keep in mind that this lost interest is not only "not our client" but also a source of negative feedback about your site.
Didn't find what you were looking for?
Ask your questionAsk a Question
731 491 924 answers to any question