CETIS 12 Conference: OpenMic Session

Posted on by

Hello. Long time, no see! I’m terrible at this blogging lark. I really need to get into it as I do have stuff piling up in my head.

However … for now I’m going to simply point you to somebody else’s blog.

I ‘chaired’ the OpenMic session at last month’s CETIS Conference in Nottingham. Very much enjoyed it. Nice and relaxed, fun and informative with 6 short talks and discussions around a clutch of random topics.

There was the MIMAS Landmap Geospacial Resources project, a discussion around the role of the “learning technologist” in today’s tech environment, the XCRI validator and mashups opportunities, a pondering on whether there was a standardised ways to exchange forms across systems, HESA’s Redesigning the Higher Education Data and Information Landscape and yours truly did a quickfire thing around where I see Augmented Reality right now.

But anyhoo … thankfully, the JISC’s very own David Kernohan attended the session and very kindly live-blogged the whole thing.

So … for coverage and links and stuff, go see David’s post at http://followersoftheapocalyp.se/cetis12-open-mic-session

Now then. I best start thinking about getting some more posts done. See you soon!

Open Source Junction 2 – Context-aware mobile technologies

Posted on by

I’ve just spent the last couple of days in Oxford, at the OSS Watch event focused on context-aware mobile technologies…and most interesting it was too!

And packed with talks. Too many to properly go into here as I’m one of those people that believes blog posts shouldn’t really end up the size of a report…or books ;)

Naturally, there was a lot of focus on geolocation implementations – the use of Open Street Map data, mashed with twitter streams, media, social networking & tagging, crowdsourcing and even a spot of augmented reality. Some cool stuff. In fact, quite a lot of cool stuff.

Two pieces of work in the Edu Institutional space, both benefitting from JISC funding, which are big favourites of mine, were presented – MyMobileBristol and MOLLY – both open source solutions for institutions to deliver key services to students through their mobile devices. Access to local travel information such as bus times, library services, PC availability, news, events, contacts…you know…all the kind of stuff you would expect when it comes to service delivery. Over the coming months I’m going to be looking at ways in which CETIS can help to raise awareness and advertise these tools to institutions and – hopefully – help uptake and roll-out across institutions and engagement with the open source community that can then assist sustainability of these frameworks. I would strongly advise institutions that are considering and developing their mobile strategy (for I sincerely hope most, if not all, are doing!) to check these out. Stay tuned for an upcoming event organised by yours truly over the next few months.

There was also a load of great advice on building open source communities, processes and tools for open development collaboration, open source business models and open development & IPR. All while – across both days – allowing plenty of slots and time for folks to do the self-pitch, speed date and general interactive sessions where we all mingled and spoke to people we identified as potential collaborators. There seemed, to me, to be quite a bit of joining up happening and relationships & network building.

All the talks were filmed but, given they have quite a few to deal with, they’re not available as yet. In the meantime though you should check out some of the resources like the recorded live blog feed, the programme with links to session details and a couple of presentation slides…and keep an eye on the site for more landing. That’s available on the Open Source Junction site on Posterous – http://opensourcejunction.posterous.com/

For a look at the wider work of OSS Watch, visit their site at http://www.oss-watch.ac.uk/

 

“Top Tips” for the Mobile Web in JISC Inform 31

Posted on by

I recently had the great pleasure of collaborating with Brian Kelly, at our fellow JISC Innovation Support Centre–UKOLN, on a short piece for the latest issue of JISC Inform (#31…online at http://www.jisc.ac.uk/inform/inform31/)

Top Tips for Mobile Web

There is no such thing as the Mobile Web...at least that bit makes sense!

The piece was a kind of follow-on from the Mobile Web Apps briefing paper and Brian and I looked to produce an easily digestible, ‘Top Tips for the Mobile Web’, that we hoped would serve as a nice jumping point for those people in institutions working on delivering services and content to mobile devices.

While I’m very pleased to see the article rendered so nicely and published in Inform I must confess to be kicking myself at how badly I’ve actually worded the first tip (the FIRST one!! So it’s immediately noticeable! Eek.)

You can see the piece at http://www.jisc.ac.uk/inform/inform31/MobileWeb.html

What appears is this:

There is no such thing as the Mobile Web
Design for the usual internet and then make your site adaptable for mobile devices for example decreasing the screen size using CSS media queries and then scaling up for larger devices like tablets and PCs by progressively enhancing access for larger audiences.

Now…poorly written, right? “usual Internet”? Decreasing screen size using media queries”? Crikey. Not quite sure what happened here but let me have a stab at making it a bit clearer (and sensible).

“There is no mobile web” – I think this is true from the POV that many people in education have jumped on the buzzwordy feel of the Mobile Web as a cool topic and then fall into the trap of thinking that the web on mobile devices (ie. smaller screens) exists as a separate entity. My view is that there is simply “The Web” and that we view it through different windows–desktop monitors, laptops, phones, tablets, television sets, etc–and we should simply see it as that. After all, we don’t call it the “Desktop Web” or the “TV Web” do we? No. Ok…let’s move on.

“Design for the usual Internet” – possibly the most nonsensical sentence I’ve ever written. And that’s saying something. What I actually *mean* is–as outlined above–think about your overall approach to developing content for the web in general and then look at how you adapt that content for the screen sizes we’re talking about when we talk “mobile”. Don’t think, “we’re going to make a mobile website because mobile is where it’s at now”. The web is where it’s at. Always has been, always will.

Decreasing for screen size? – A botched job of saying “take your website, make it adaptable and responsive to it displays properly in mobile browsers, then use CSS Media Queries to make the same content adapt to different devices: flexible layouts that respond to the browser capabilities and screen real estate on offer.

Larger audiences? – Wider audience…those that aren’t viewing on a mobile device. Again, one web that adapts to the different canvases we view it on.

So…hopefully that clarifies that tip somewhat. I think where I went wrong was in trying to pack 2 thoughts and 3 tips into one tip, while keeping it short (hence not mentioning <meta name=”viewport”>) but ending up with something that I read back and thought, “Good god, man…you’ll never work again!” ;)

I *think* I’m happy with the other tips though.

 

 

Sencha Touch v. jQuery Mobile. What gives?

Posted on by

Some of the web development tools that are getting quite a bit of attention when it comes to the topic of optimising websites for mobile and developing mobile web apps are JavaScript frameworks – as I mentioned in my [*shameless plug alert*] briefing paper on Mobile Web Apps

Two of the biggest names in this space are Sencha Touch & jQuery Mobile (which has now been built-in to the latest version of Adobe’s Dreamweaver CS 5.5). Both are freely available and enable developers to enhance the user experience by quickly and easily adding the kind of smooth transitions, animations and interactions that we have all come to associate with using our fancy touchscreen smartphones and their powerful mobile web browsers.

So…which one to use? Well, that very question has come up and garnered some feedback on Quora. So I thought I’d flag it up for you here (I’m nice like that, see).

The general consensus seems to be that Sencha is more robust and performs better than jQuery Mobile, with richer and smoother interactions and animations making for a cleaner – more “native feeling” – UI. However, it also seems to be agreed that Sencha involves a much steeper learning curve and is a bit lacking in the documentation area. One summation was, “If you’re simply looking to enhance a mobile delivered website, go with jQuery. If you’re looking at developing a richer web *app* then Sencha is the way to go, particularly if you’re looking at developing your app using web technologies and then wrapping it up for deployment as a native app using something like PhoneGap.”

So, like I say, I thought I’d flag it up. You can read the discussion on Quora at http://www.quora.com/Were-deciding-between-jQuery-Mobile-currently-in-alpha-and-Sencha-Touch-What-are-the-pros-and-cons-for-each and you’ll find that some of the comments link to other – possibly useful – resources.

But while I’m here I may as well point out a couple of other – related – things. First up is a “Quick Introduction to jQuery Mobile” that I spotted on Twitter.

http://www.coldfusionjedi.com/index.cfm/2011/6/29/jQuery-Mobile-Quick-Start-and-new-jQuery-class

And, secondly, is a topic of conversation that has started up around the whole business of mobile apps…native apps…web apps…(!!!) which I think is interesting. That revolves around the thinking in some quarters that if you’re building a web app for mobile you actually SHOULDN’T go trying to make it look like a native app at all. I think this is one for the designers and those interested in UX (I don’t think we really have any UX experts working in web teams in UK Edu do we?)…

http://cvil.ly/2011/06/19/pretenders-why-mobile-web-apps-should-stop-trying-to-act-like-native-apps/

Oh and my thanks to Mike Jones at MyMobileBristol for the above link :)

HTML5 and what it means for mobile

Posted on by

VisionMobile, a leading market analysis and strategy firm in the mobile market, have recently published a report on HTML5 and what it means for the mobile industry. While its primary target audience seems to be operators and commercial players in the mobile market there are still some key points that can be taken from it that are useful for those in educational institutions to bear in mind. For example…

  • The web has evolved through two major phases: Web 1.0, the era of dumb terminals and Web 2.0, the era of smarter terminals, where users are both consumers and producers of content.
  • The web is both a technology paradigm (HTML) and a business model paradigm for the unfettered distribution [and monetisation] of content.
  • HTML5 is pushing the capabilities of web applications to the point of making web apps as engaging as Flash applications and as integrated with the device as mobile applications.
  • Despite the adoption of WebKit as the de-facto browser engine on over 500 million handsets to date, mobile browser implementations remain consistently fragmented. Even standards bodies W3C and the WHAT WG show fragmented approaches to HTML5 completion, which is not expected before 2014.
  • The web is winning in developer mindshare, but it will not replace native platforms; instead web applications will co-exist with native applications that maintain an edge in terms of device and cloud integration capabilities. Web applications will retain an edge in use cases such as business applications, mass-market services and cross-screen experiences (mobile, TV, PC).

VisionMobile have given an overview on their blog, where you can also download the free report.

http://www.visionmobile.com/blog/2011/06/html5-and-what-it-means-for-the-mobile-industry/