Showing posts with label Android. Show all posts
Showing posts with label Android. Show all posts

Tuesday, 16 October 2012

Too Many Apples For The Teacher


There is a scene near the end of The Prisoner in which Number 6 starts to speak. "I.." he begins. "I...I...I..." echo all the faceless ones in his audience. He tries to continue. "I..." only to be interrupted by yet louder and more forceful "I... I.... I..." and so it goes on... This seems quite appropriate to what seems to be happening now in many teaching advice articles, even to the extent of how to impress OFSTED (whose representatives surely would have made brilliant Number 2s had they been around at the time).

With all the free promotion from mostly intelligent and ostensibly fair-minded people like teachers and e-learning experts, Apple must be laughing all the way to the bank and can probably now afford to sack all but a few in their Marketing Department.

Everywhere I turn these days there's some eminent authority on education technology telling us, or a grant being offered by supposedly commercially independent quangos for institutions to report on, how wonderful iPads and iPhones can be and how to utilise Apple apps in teaching-and-learning.

I'm not saying that these are not good products. I'm not saying that they cannot contribute immensely to what we're all trying to do in education. What is so wrong is that these guys only talk about or write about or demonstrate Apple products.

There are alternatives. There are good alternatives. Some might argue that there are better alternatives. (I'll try and avoid that part of the argument!) But one thing's for sure - there are cheaper alternatives.

It's a bit like the days when colleagues would give presentations and tell everyone in the room to use PowerPoint or Word to do something that could just as easily be done in software that didn't need a Microsoft Office installation. I lost count of the number of references to Microsoft Office products I had to re-word in piles of course materials designed to assess teachers' and trainers' Information and Learning Technology skills in the earlier part of this Century proposed for publication by erudite bodies running on government money. Whilst they frowned on any logo or brand mark being featured in dissemination reports to the point where I was unable to get a payment authorised for something otherwise excellent with a picture of Homer Simpson somewhere in it, references to specific Microsoft or adobe products were conveniently ignored,

I have no objection to guidance notes and examples of how to do something featuring software or hardware that you need to pay for but when I read the more general recommendations or suggestions that teachers or institutions should adopt I really do think it is time for some balance.


There are loads of really good smartphones around now and soon there will be a real choice between Android and Windows 8 as well as the Apple operating system.



There are less numerous, but still excellent, Android and, coming soon, Windows 8, tablets or pads as well as the iPad. 

Generally Apple's products seem to be much more expensive than their Android competitors and the apps that I see recommended are often ones that have to be bought by staff or students on Apple systems where the Android alternatives are free. I have yet to read a set of suggestions where it would not have been easy to have written them with reference to the alternative products or by using generic terminology instead of specific tools which make the whole article deserving of a brown padded envelope floating through the writer's letterbox containing some suitable sign of appreciation from Apple. Something beginning with i, perhaps?

So can we please stop this ubiquitous use of Apple's very, very cleverly designed brand names. Let's talk about phones, not iPhones (or, worse, iphones!). Let's talk about pads or tablets or anything except iPads. Save those Apple Marketing people's jobs! They've worked hard to get you all on their side - it doesn't seem fair that you should be doing their work for them now does it?



Saturday, 29 October 2011

Here comes the $35 tablet!



Aakash Tablet from Venturebeat on Vimeo.

Well, if you're at school in India, that is. Even allowing for a Government subsidy of about $20 this is one cheap solution that works and will enable millions more children to see what we see and take for granted on our notebooks, pcs and tablets that cost ten times as much.

Yes, our kit may look cooler, work a bit faster, even have the seemingly essential letter i at the start of the model name but...

... the information we all access remains the same.

Thanks to Robert Rendl, a thinker at Easytouch.com, Vienna, for sharing this initially.

Wednesday, 12 October 2011

Goggles at the Zoo

Holding a Staff Conference in a zoo was, of course, bound to lead to a few jokes but what a great place! Whilst networking between sessions has its value, we did, actually have plenty of time to chat over lunch and on a mild autumn day it didn't seem to have as much value as wandering around and finding muntjacks crossing the path or ring tailed lemurs on the other side of a hedge. Add an ape or two, owls and some other exotic birds and some good exercise and you had a good reason to leave the discussions for a while.

Still remembering the Google Goggles presentation from a few days ago at the E-learning Forum this was also a great opportunity to put it to the test. I mean, I had no idea what the muntjack were but Google Goggles told me. This was the first time I'd used the software which had gradually downloaded itself the day before when I was in an area with a rather better connection than I have at home. It really is dead simple to get for Android users, taking care of its own download and installation with little more than the occasional tap on OK - and it's free. I had no idea how to work it but needn't have worried. You just tap the icon and it fires up instantly, presenting you with a camera like view and, assuming the camera's pointing in the right direction, another tap on an icon takes a snap and sets off the scanner. The scanner is a blue faded line that whooshes across the screen (and up and down sometimes too for reasons best known to itself). That takes a while and, once it's done you get told either that it doesn't recognise what you and it have seen or it does and then provides a bundle of similar images and some data which can be clicked to provide whatever else you want to know.

I clearly need more practice at aiming as most of my efforts, especially the ones where others were watching and I was hoping to show off , produced the unrecognised response. So more about that when I get a bit more success and maybe stop shaking when I press the buttons!

Unless I had something else running that I wasn't aware of it does seem to eat into my battery life, though and, from a full charge in the morning the bleep that tells me it's shutting down through lack of power (and, frustratingly, doesn't give me any time to grab a charger and do the decent thing to revive it) comes at about 7pm. That's not too good. Just as well I didn't make any calls or use the phone to make notes or do any research during the day or I'd have been lucky to make it home.

Something else I discovered after almost a year with this phone was that I could zoom in on things with the normal camera. I feel such a fool and must have missed, or not bothered taking, loads of potentially good snaps before! I had an ape in view and accidentally pressed what would normally be the volume control. And I'm now staring the fellow in the eye as if I'm a few inches away! Remarkable.

Some interesting developments with FE on the horizon and, for the first time for a while, I have some real hope that I may have a chance to express some views and constructive suggestions and actually have them considered. More on that another time. For now I have to deal with the problems that Staff Conference days do bring: 34 new e-mails to do something with (and that's after archiving those that are just for reading some day), figuring out what a new HNC course is all about and gathering enough information to ensure that I appear reasonably informed for a new group starting tomorrow and assorted personal matters like advising on increasingly difficult children's homework (I have already abandoned hope of being any use at all on my 15 year old daughter's Biology and Chemistry is virtually at the edge of my comprehension too). I seem to recall that the Khan Academy had some courses - looks like I'll be going back to school there again soon! Then there's the matter of liaising with the nice Edufire people who want me to do a Helping Students Succeed course soon, following up on a bundle of interested enquiries about my Staff ICT Skills Audit and then there's the E-learning Consortium to set up. Twitter and Google+ will ahve to wait another day by the seems of it. Hope I'm not missing too much. They have become my Daily News. Oh, and I nearly forgot ... dinner.



Monday, 19 July 2010

App Inventor for Android

This is quite remarkable. The very idea that 'normal' people can make applications, sorry, they're called apps now, for their mobile is just so hard to grasp. Yet it seems to be true and could be one of those massive leaps that happen from time to time in technology and what we do with it.

The GoogleLabs App Inventor for Android ..

"You can build just about any app you can imagine with App Inventor. Often people begin by building games like MoleMash or games that let you draw funny pictures on your friend's faces. You can even make use of the phone's sensors to move a ball through a maze based on tilting the phone.
But app building is not limited to simple games. You can also build apps that inform and educate. You can create a quiz app to help you and your classmates study for a test. With Android's text-to-speech capabilities, you can even have the phone ask the questions aloud.
To use App Inventor, you do not need to be a developer. App Inventor requires NO programming knowledge. This is because instead of writing code, you visually design the way the app looks and use blocks to specify the app's behavior."

Apart from spelling behavior differently there'd be no point in me trying to put this any better. I carry on, with acknowledgements to the GoogleLabs writers..

"App Inventor is simple to use, but also very powerful. Apps you build can even store data created by users in a database, so you can create a make-a-quiz app in which the teachers can save questions in a quiz for their students to answer.
Because App Inventor provides access to a GPS-location sensor, you can build apps that know where you are. You can build an app to help you remember where you parked your car, an app that shows the location of your friends or colleagues at a concert or conference, or your own custom tour app of your school, workplace, or a museum.
You can write apps that use the phone features of an Android phone. You can write an app that periodically texts "missing you" to your loved ones, or an app "No Text While Driving" that responds to all texts automatically with "sorry, I'm driving and will contact you later". You can even have the app read the incoming texts aloud to you (though this might lure you into responding).




App Inventor provides a way for you to communicate with the web. If you know how to write web apps, you can use App Inventor to write Android apps that talk to your favorite web sites, such as Amazon and Twitter."




This all sounds great and I can imagine students will really love this too. Now, I wonder just how 'easy' it really is? I'll let you know in a while.