Mobile Version of the website
David R. Lane (77) 766 posts |
Can we have a version of the ROOL website adapted for mobile phones? |
Stephen Scott (491) 38 posts |
I would support this. However, given the site’s size, I’d imagine there would be two approaches to this – the quick and dirty method (hide assets, change font size, rearrange the sidebar), or a more measured approach. Areas such as the forum will require a fair amount of tweaking to work properly on mobiles. The quick and dirty may end up being entirely adequate for some parts of the site, but I’d imagine having a great user experience all round is paramount. And it needs to load fast. I’m using a three year old Blackberry, which doubles as a hand warmer when viewing resource heavy websites :-) |
patric aristide (434) 418 posts |
Not a problem on my eight year old 240×320 HTC phone. Having a decent browser helps, Opera Mini in my case. |
Rick Murray (539) 13840 posts |
Looks as good as a PC in an iPad Mini. That’s usually how I come here now (no waiting forever for the antivirus, Firefox, and a dozen other things to apply updates to their internals). Is also usable on an 848×480 Android mobile using the stock browser. You have to squint a bit as the screen is small, but it is clear. On my phone, at least, one can pinch out to zoom. |
Steve Fryatt (216) 2105 posts |
Works fine on my Android phone, which isn’t exactly high spec. It’s easier in a decent browser (such as Firefox) which has the ability to zoom in to areas of text, than the default Android offering, but I could read this site just fine in both. I assume that the “Fairphone” is running a sufficiently clean version of Android 4.2 that you can install your own apps on it? |
David R. Lane (77) 766 posts |
It has Android version 4.2.2 and kernel version 3.4.5. Even with high resolution, tiny text is not going to be readable. |
Rick Murray (539) 13840 posts |
I think the ease with which it can be done depends a lot on the back end. Compare regular: http://www.heyrick.co.uk/blog/index.php?diary=20141128 Thankfully as the content is built in a more traditional way (styles give attributes, not markup and layout), it was a simple matter of switching the header and footer content for something adapted to mobile phones. The rest, such as the image scaling (it is a reduced scale rather low quality (60% if I remember) JPEG designed to send and load quickly on low bandwidth networks like EDGE) was done with php on the fly as the main content was loaded and sent. Something very important to remember is to always provide a method of accessing the desktop version of the content. Some mobile devices are quite capable of doing it (and some do a better job than the likes of MSIE!). So if you use browser sniffing to determine which version to sent, don’t make it a fixed choice. Mobile invariably means reduced functionality, so at least let the user trade off what they want to do. |