This question is locked. New answers and comments are not allowed.
Patrick Barranis
Top achievements
Rank 1
Rank 1
Patrick Barranis
asked on 09 Feb 2011, 03:47 PM
Hi. Our team is regular users of all the Telerik products in all of our apps. However, we're developing our first new MVC web application that's specifically targeting mobile devices. To what extent have the MVC extensions been tested on those platforms, such as IE mobile, Safari mobile, etc? Are there any known issues, guidance, etc? I'd like to avoid any known pitfalls.
Thanks!
Thanks!
3 Answers, 1 is accepted
0
Hello Patrick,
Frankly, the components are not extensively tested on mobile devices. The basics work, but we do not claim that we support them. That said, here are some problems that we are aware of:
Regards,
Alex Gyoshev
the Telerik team
Frankly, the components are not extensively tested on mobile devices. The basics work, but we do not claim that we support them. That said, here are some problems that we are aware of:
- the editor renders as a plain textbox on mobile webkit. This happens, because there is no contentEditable for these browsers.
- the drag&drop (for grid grouping, treeview reordering, etc) should not work, since we are using mouse events rather than touch events.
- hover styles will not be applied on touch devices, since there is no hover state. This renders the menu component unusable unless you use the OpenOnClick(true) property.
- scrolling containers (i.e. the grid with scrolling enabled) are not really usable, since they do not show a scrollbar and need to be scrolled using a two-finger gesture.
Regards,
Alex Gyoshev
the Telerik team
Do you want to have your say when we set our development plans?
Do you want to know when a feature you care about is added or when a bug fixed?
Explore the
Telerik Public Issue Tracking
system and vote to affect the priority of the items
0
Patrick Barranis
Top achievements
Rank 1
Rank 1
answered on 10 Feb 2011, 02:12 PM
That's great; thanks very much!
If you think of anything else to add in, please do so. I'm sure I won't be the last person to ask this question.
Patrick
If you think of anything else to add in, please do so. I'm sure I won't be the last person to ask this question.
Patrick
0
Dan Ware
Top achievements
Rank 1
Rank 1
answered on 20 May 2011, 11:18 AM
It's worth mentioning that ASP.NET websites with AJAX (the managed kind, such as using RadAjaxManager or RadAjaxPanel), will not be reliable on Android, iOS, Symbian or Windows Phone (before 7, at least). Occasionally similar unreliablity is encountered with Apple Mac Safari as well.
It's understandable if the controls don't work due to having rich feature-sets but I get a huge number of viewstate issues with these clients, often preventing them from even logging in (these can be random and difficult to reproduce on demand). I get around 30-60 of these errors a day on my main Telerik web app, but I do get over 3,000 logins each day.
Also, Windows Phone 6.5 decides to attempt to download webresource.axd and scriptresource.axd (without any querystring), meaning that it's particularly useless on these types of website.
I'm not saying they don't work, they're just very unreliable. It's usually best to redirect phone users to a cut-down basic version of your site, but keep it simple for future updating.
I haven't tried the Telerik Windows Phone UI controls because 80% of our phone users are not using a Windows phone. It seems poor to support such a small segment of the phone market, but then for Telerik I suppose it's a matter of support.
It's understandable if the controls don't work due to having rich feature-sets but I get a huge number of viewstate issues with these clients, often preventing them from even logging in (these can be random and difficult to reproduce on demand). I get around 30-60 of these errors a day on my main Telerik web app, but I do get over 3,000 logins each day.
Also, Windows Phone 6.5 decides to attempt to download webresource.axd and scriptresource.axd (without any querystring), meaning that it's particularly useless on these types of website.
I'm not saying they don't work, they're just very unreliable. It's usually best to redirect phone users to a cut-down basic version of your site, but keep it simple for future updating.
I haven't tried the Telerik Windows Phone UI controls because 80% of our phone users are not using a Windows phone. It seems poor to support such a small segment of the phone market, but then for Telerik I suppose it's a matter of support.