Tag Archives: screen

Giving screencasting a thought

Following a session I gave on Friday on Using video in language teaching, I had an interesting conversation with some colleagues about screencasting.

As most of you probably know, screencasting (which I insist on writing in one word, despite my spellcheck’s best efforts) consists of recording what is happening on your computer screen into a video document. People will frequently add voice-over or captions to create tutorials and informative videos.

During Friday’s session, I mentioned a couple of screencasting solutions that may be of interest to tutors: Camtasia (Mac/PC, £73 to £220), Blueberry Flashback (PC, £59 to £132) and Quicktime X (Mac, free with OS X 10.7 or greater), although I had to admit not knowing much about other (and cheaper) solutions. So, better late then never, I went out and looked at what’s available.

I found that PC World has a very nice page summarising what’s available. If you’re looking for cheaper solutions than the ones mentioned above, try this page. Some of the software presented even allows to record your screen without software installation (provided you can get the Java applet to work).

I also realised that I had been using yet another screencasting solution myself, but hadn’t thought of including it in my session: Fraps (free to £25). Fraps is mostly popular among PC gamers due to its light CPU footprint and benchmarking ability. But on thinking about it, it is also an affordable, easy-to-use screen capture software package that can very well be used for educational purposes.

Examples

So, what would you use screencasting for in education?

I’ve given it a try myself a couple of times, to:

As you can see, I haven’t used screencasting in my language teaching practice yet. If any of you do, I’d be delighted to hear about it – feel free to comment in the box below. Thanks for reading.

Great design for easy learning

Once in a while when using a device of some kind, you need to learn a new functionality. It was the case for me the other day when Apple updated the iPhone operating system iOS to version 5.1.

Changes brought to the system were mostly minor and required little adaptation, if any, but one of them caught my attention. The button allowing the user to quickly access the phone’s camera from the lock screen had changed slightly.

Firstly, the camera button was now displayed permanently on the lock screen. Beforehand, the user had to double-click on the home button for the camera icon to appear. Secondly, it now presented some horizontal lines above and below it:

iPhone Lock screen iPhone Lock screen camera button close-up

Prior to the changes, you had to tap on the icon to access the camera, but the newly appeared lines now suggested that some change had been brought to the way the button worked.

So I tapped the button to try and access the camera, as I would have done before. This did not open the camera application. Instead, it made the entire screen bounce up and down slightly, briefly revealing the camera app underneath it:

iPhone Lock screen bounce

So pressing the button no longer worked, but the device gave you a clue as for what else you might want to try.

So quite logically, looking the lines suggesting that the camera icon might move up or down and now knowing that the camera app was “hidden” underneath my home screen, I came to the conclusion that pushing up the camera icon would make the lock screen slide up and reveal the camera app. I tried and it did.

iPhone Lock screen arrow up iPhone Lock screen slide up iPhone Camera app

What’s truly remarkable about this piece of design is how intuitively the new feature can be learnt. One way to go about it would have been to add to user manual a section on ‘a new and easy way to open your camera app’, but instead, developers simply added that little bounce effect, providing the user with simple but efficient feedback as for how they might modify their behaviour to work the device.

For a few minutes, I marvelled at how ingenious this functionality was (yes, I’m easily impressed). But what’s more, I kept thinking of how such simple an efficient design could be used in my teaching, to help students learn new stuff effortlessly. Not that all learning should be effortless, but there’s nothing wrong with making people’s life easier once in a while.

So now the question is: how can better design help my students learn better? Any thoughts, please share!