tag:blogger.com,1999:blog-31452346.post1420523219257588839..comments2023-08-01T16:38:30.996+01:00Comments on The Doofer Call: Mobile thinkingJeremyhttp://www.blogger.com/profile/11209315592056360247noreply@blogger.comBlogger4125tag:blogger.com,1999:blog-31452346.post-60995623434672259492012-09-23T11:44:21.235+01:002012-09-23T11:44:21.235+01:00@ Mike L: Thanks for your thoughts Mike, that soun...@ Mike L: Thanks for your thoughts Mike, that sounds like a useful distinction. I might personally add some other things into the design part of "responsive", particularly some content. Conditionally loading media can be as much about design as functionality but is not generally achieved with CSS alone. You're also right of course about needing to go native for some functionality, but I can also imagine scenarios where your mobile experience works quite differently to your desktop one but without requiring anything a mobile browser can't do. For instance one might allow for some customisation of the home page (perhaps hiding most content but letting users add it back in). On the whole, though, I suppose it's either a case of removing fancy stuff from the mobile version or wanting to offer something that only an app can do.<br /><br />@ Monique: This is a really important problem, isn't it? I'm sure there are ways that one can build/manage a single site/set of content that can be put together so that an appropriate portion of text is shown for the platform, but it would require well-behaved authors and might still have its limitations. Perhaps it would end up pushing you to have separate sites or sets of content for different users or contexts in the end. It's such a tough thing to balance, how much extra work we want to make for ourselves and for authors, and how much we want to dictate what users experience. Always for me we come back to that problem: how will we know what's the right rendition to show a user, how much choice can they have, and how much of a management nightmare will that give us?<br /><br />*****<br /><br />PS Here are a couple of references I should have put in the post. Here are a couple of posts by Jeremy Keith (@adactio) on the <a href="http://adactio.com/journal/5414/" rel="nofollow">conditional loading of content</a> and <a href="http://adactio.com/journal/4997/" rel="nofollow">"responsible responsive images"</a>. And here's <a href="https://github.com/WickyNilliams/enquire.js" rel="nofollow">enquire.js</a>, a library that looks interesting for letting you do more with media queriesJeremyhttps://www.blogger.com/profile/11209315592056360247noreply@blogger.comtag:blogger.com,1999:blog-31452346.post-73618159838303413132012-09-23T11:41:57.376+01:002012-09-23T11:41:57.376+01:00This comment has been removed by the author.Jeremyhttps://www.blogger.com/profile/11209315592056360247noreply@blogger.comtag:blogger.com,1999:blog-31452346.post-4018112275930177942012-09-21T22:52:47.770+01:002012-09-21T22:52:47.770+01:00I recently came across an issue I had not consider...I recently came across an issue I had not considered before, namely that scaling content for all viewports is not just a consideration for devs and designers but authors too.<br /><br />Recently completed a completely adaptive site and technically it adapts and responds extremely well. The only real flaw is the authors' desire to fit whole paragraphs into titles and captions. Yes we can reduce font size but it still needs to be readable/accessible. If we restrict the character count of titles, captions and teasers authors complain. We can't just truncate sentences and expect that they will make sense. We can only point out that these elements ideally suit one or two short sentences and not an essay. Not many authors are in the habit of checking their content on different devices. Seeing our neatly fluid layout being stretched out of shape as it tries to contain far, far too much text at small sizes is a bit sad!Moniquenoreply@blogger.comtag:blogger.com,1999:blog-31452346.post-75660896912765813522012-09-21T11:00:18.063+01:002012-09-21T11:00:18.063+01:00Hi Jeremy,
Couple of points to add. When people t...Hi Jeremy, <br />Couple of points to add. When people talk about 'responsive design' I've started to use the phrase 'responsive functionality' to make them think about the boundaries. Responsive design _should_ essentially be 'make this site work on small/different screen sizes' and perhaps 'take account of touch'. Nothing else IMO. It should be mostly doable with CSS.<br />Beyond that is functionality. If you want wildly different functionality, right now you have to consider going Native. <br /><br />Secondly, one of the main themes to emerge regarding 'why go native' is bandwidth and internet access - the return to the world wide wait we all suffer using our phones. Some apps are being built essentially so web content can be cached on client devices (and presented via neat slideys). <br />Some interesting stuff is being devloped in this area e.g. PouchDB. Client-side databases accessed via js could provide the right half-way house.Mike Lhttps://www.blogger.com/profile/03891665022836480538noreply@blogger.com