Even if you think you know it all - I guarantee you'll get a few new ideas by the time you finish reading this infographic!
How are you planning on using this?
Thanks to Tony Vincent at learninginhand for the excellent round up!
Interested in the future of mobile learning and the technology that drives it? I am geoff stead. This is a vintage blog of mine I'm reviving for m-learning thoughts that stray beyond the day job. You can find my work with enterprise mobile learning at WorkLearnMobile.org, and in english language learning over at beta.cambridgeenglish.org
A year ago, Google released App Inventor – a fascinatingly visual, albeit rather buggy tool for developing android apps. Although not robust enough for our commercial development, we loved the fresh ideas about interface, and app building. Perfect tools for learning about coding. Today I found an email in my inbox announcing that Google are dropping support for it.
Google are open-sourcing the code base. Often a sign of a project’s demise. Sounds like bad news for education … or is it?
(by Andrew Merryweather - @merryux - our UX guru)
The iPad, loaded up with a few off-the-shelf apps, is revolutionising the way archaeological digs are run.
As an ex-archaeologist I keep an eye on digital trends in the digging world, and came across a great post on Apple.com about an old friend and colleague Dr Steven Ellis of the University of Cincinatti and his digitally-enhanced fieldwork at Pompeii. He is using iPads, with simple off-the-shelf apps to collect data in a simpler, and more shareable manner than ever before.
Computers and archaeology have a long history, but excavators have been waiting for mobile tech to hit the right balance of portability, usability and power to really have a big impact on the way they conduct fieldwork. The latest generation of mobile devices, and especially the iPad, has hit the sweetspot.
Ellis credits the introduction of six iPad devices at Pompeii with helping his team solve one of the most difficult problems of archaeological fieldwork: how to efficiently and accurately record the complex information they encounter in the trenches.
This kind of digital data collection could be a learning opportunity in the making. There's a chain ready to be created which takes live data from field projects (in any scientific discipline, not just archaeology), being captured by fieldworkers on iPads, iPhones, and other devices, and feeding it up to a web site, from where it could be pulled directly into a classroom.
It's not hard to imagine a collection of classrooms 'partnering' a dig, and getting data piped straight from the trench to a few iPads of their own. Activities could be built around looking at the latest photos and maps each day, discussing the latest finds, following the life of the project from start to finish.
M-learning with a twist?
If you like the sound of this, please also check out Nick Short’s work at the Royal Veterinary College. He is using Android devices, and off-the-shelf Google tools to support Vets in Africa collect and share some extremely valuable data
…we are relaxing all restrictions on the development tools used to create iOS apps, as long as the resulting apps do not download any code. This should give developers the flexibility they want, while preserving the security we need.As one of a small (but enthusiastic) set of app developers striving to make cross-platform apps, this is a HUGE deal.
Living in the middle of “mobile learning”, it feels totally obvious that mobile is important, and that it fundamentally changes the way we look at information … but I can’t help noticing that not everybody else shares my view!
(shocking, I know!)
That’s why I really like Bryan’s presentation – with (quite a lot of) simple, non-technical images and statements he manages to capture the excitement, the challenges, and the diversity of the mobile landscape
I especially like the simplicity he uses to get the message across – if I wasn’t already enthused, I would be now! Thanks, Bryan
There are a few m-learning conversations that pop up again and again when talking to clients about mobile courses. It often starts with a seemingly simple question:
“I want richly interactive content for any phone”
“Will it do Blackberry? And iPhone? And Nokia?”
“all my students need to have the same access to learning”
These are good questions, and the obvious response to any is “yes, of course”, because we would all like equality between mobile users. But there is a painful reality that (right now, in 2010) makes this an impossible dream:
The painful reality about making m-learning content is that there is no single solution to push richly interactive mobile content onto every possible phone. Rather, there is a spectrum of possible solutions: On one side, going for the richest possible interactivities (but narrowing down to single platforms) and on the other side going for the widest possible phone coverage (but limiting interactivities to the very lowest common denominator)
Examples on either side of this spectrum would be some of the delightfully interactive apps you can get for the iPhone (which exclude all other devices) vs several SMS / text messaging solutions (which work on just about any phone)
This spectrum is just the reality. There is no getting away from it. if somebody tells you otherwise they are not seeing the whole picture.
M-learning developers have been trying many creative approaches to cover as wide a range on this spectrum as possible, but it is technically impossible to cover it all. Examples are:
- making a different app for each device, playing whichever bits of the same central content that device supports
- delivering media-only courses (video or audio) that make up for lack of interactivity with wide device coverage
- using 3rd party players (like Flash, or eBook readers) to render a common course format to different devices
- putting content online, in the browser, and allowing the web-server to decide which versions suit your device
In all of these scenarios, there is a functionality sacrifice (because you are not exploiting device specific features, like GPS), but the benefit of create-once but used-by-many.
So, if you are thinking of making your own mobile content, my best advice is to be pragmatic about this spectrum of solutions. Instead of starting with the big dream (“for every single device”) rather start a little more pragmatically by narrowing the range of technologies you are looking at, and them work backwards to see which type of authoring tool or technical approach works best.
A popular example of a narrower range is "smartphones", though depending on who you are trying to reach out to it might also be "phones with decent browsers".
Another good subset (if data rates are not an issue) are phones with decent browsers, since the latest smartphones and high end featurephones all have a pretty good web browser, which is a lot more standardised than their operating systems.
Currently, my team in Cambridge cover the spectrum via a hybrid approach. We build for iPhone and Blackberry by hand. We have a java (j2me) engine we use for old-skool phones. We use a hand-made authoring tool for WindowsMobile / Android / UMPC / Linux / Windows / Mac (also sold commercially as MyLearning Author). We use another handmade tool for SMS activities (SMS Quiz / SMS Survey).
A lot of our current research work is looking at a hybrid between our MyLearning app (building installable learning apps) and browser-based content (wider cross-device support), so that we can get the best of both – with content that can be installed like an app, runs both on- and off-line, and uses the browser to play back courses wherever possible.
There has been a flurry of news over the past few days including the words “US Military” and “mobile Apps”
part one:
DARPA, home of the pentagon’s technology research gurus, has announced it wants to buy an “AppStore” to use for distributing mobile apps to soldiers.
This is newsworthy on several fronts:
1: DoD (department of defence) are thinking of using normal, everyday-type connectivity (3G), on normal, every-day type devices! (Android)
2: They plan on taking their own 3G coverage with them, to save relying on the possibly unfriendly locals when in far away lands
3: they have dropped both WindowsMobile and iPhone in favour of Android
4: they plan on asking the open market to bid for funding to make apps
Read those again. Bog standard kit. Mainstream networks. Open standards. Open market for apps. Wow.
part two:
A couple of days later, DoD announces the A4A (Apps for the Army) initiative to encourage software-savvy soldiers to propose and make apps (mobile and other).
There is only enough funding for 100 lucky soldiers, but this is clearly just the beginning because …
part three:
DARPA are expected to announce that they are looking to buy apps. If you have a good idea for an app, and the technology skills to make it, they might well be in the market to buy it.
“Flurry of news” is definitely the phrase, here. Until a few weeks ago I had seen hardly any publicity from the US military around mobile learning. Here in the UK, there has been a bit more, with people like Major Roy Evans who has been doing some innovative trials in Iraq and Afghanistan.
You can here him talking about it here (though you will need to ffw the first few minutes, which have no sound!)
Publicity. Nice projects. But quite small trials.
Now, all of a sudden the US has significantly upped the game and leapt for a very mainstream, and imminently achievable solution. Wow!
Bring on those Android Apps, and as Google says, “don’t be evil” :-)
All this week, Dutch iPhone users have been seeing this message on their beloved devices
your iPhone has been hacked because it’s really insecure! Please visit xxxx/iHacked and secure your iPhone right now
Together with a request for $4.95 for help securing their phone.
What’s going on?
It turns out that an enterprising Dutch teenager (PureInfinity92) managed to hack a large number of Jailbroken iPhones, flagging up a couple of well known security breaches. He used a combination of port scanning and OS fingerprinting to find iPhones in T-Mobile's 3G IP range and exploit a known security risk in those that were jailbroken (OpenSSH is installed with the same root access and password on all devices!)
Unfortunately for his entrepreneurship, he was quickly outed, and his paypal account blocked. He has apologised to all, offered refunds to those who paid up, and made his security advice available for free
In fairness to the guy, his original message did say:
If you don't pay, it's fine by me. But remember, the way I got access to your iPhone can be used by thousands of others. And they can send text messages from your number (like I did..), use it to call (or record your calls), and actually whatever they want, even use it for their hacking activities! I can assure you, I have no intention of harming you or whatever, but, some hackers do! It's just my advise to secure your phone (: Have a nice day!"
Find out more from the original Dutch posting (translated by Google)
So – why use Jailbreak at all?
One of the biggest problems with using iPhones, and iPod Touches as learning tools is the “closed shop”, when it comes to sharing, and distributing Apps. Teachers cannot easily share content they have made.
Developers need to pay, and be approved by Apple. All applications need to go via Apple(iTunes), and be approved by Apple. Added to that, many countries (like most of Africa!) are not even allowed to download apps from iTunes. This is a MAJOR restriction on educators looking to make and share applications.
Jailbreak is the widely used, though not-quite-legal technique of unlocking your iPhone so that applications can be directly uploaded without going via iTunes and the AppStore. Unfortunately though, it is (by definition) not as secure as the Apple’s proprietary approach, which is why PureInfinity92 managed to hack as many phones as he did.
Our m-learning.org team do certainly not recommend jailbreaking your iphone, though we are very against the current restrictions on regular teachers making and sharing Apps and look forward to the time that Apple opens access to their Apps up a little more (like all the other mobile App stores!)
… and, for some bizarre reason, the two have been bickering all along, and never quite making friends.
The latest move in the ongoing showdown is this slightly aggressive message iPhone and iPod Touch users get if they visit a website requiring flash:
Apple restricts use of technologies required by product like Flash Player. Until Apple eliminates these restrictions, Adobe cannot provide Flash Player for the iPhone or iPod Touch
This is Adobe’s second move in the past few months to push the blame back onto Apple. They also announced that the next version of Flash Professional will allow developers to build iPhone apps from their Flash projects.
This is great news, as it will open up App development to the vast army of skilled Flash developers and coders out there. And the announcement was made via this hilarious “myth buster” movie
But – the bickering is hardly over, and iPhones will still not be “running Flash”. There remains no support for websites containing Flash. If you want that, you had better stick with your:
etc etc etc devices!
BLOOM-ing marvellous! We are in the closing stages of a great project called BLOOM, which is all about using m-learning in the workplace (in this case, for the transport sector).
Have a look at this great little video of our mobile learning solution being used by Taxi drivers while waiting on the rank (errm … no … not while driving!)
A great example of how mobile learning can help you reach the parts other types of learning can’t
Hope you like it – and please leave us comments with your thoughts. We are thinking of releasing a couple of other, similar case study videos if there is demand for them
The Android Developer Challenge: Google has offered $10 million to developers for the coolest, most interesting, creative applications that will run on their new mobile operating system.Android does not differentiate between the phone's core applications and third-party applications. They can all be built to have equal access to phone's capabilities
Android is built on the open Linux Kernel
With Android, a developer could build an application that enables users to view the location of their friends and be alerted when they are in the vicinity giving them a chance to connect.
There will be a publicly accessible repository, similar to how the Linux kernel is managed.


