iPad and Mobile Computing

3. Mobile Device Implementation

5. Growth of Mobile Devices
• 46% of US adults owned a Smartphone in
February 2012, an increase of 11 percentage
points over the 35% who owned a
smartphone in May 2011, according to a new
survey by the Pew Research Center’s Internet
& American Life Project.
• The age demographic of Smartphone owners
is 18 to 44.

7. Time-To-Adoption

9. If you are designing classroom
instruction expecting this…

10. How does mobile computing
effect Classroom Instruction?
How Does Classroom Instructional
Delivery Change With Mobile Devices

11. Teaching Changes
• Forces a Student Centered –
Inquiry Based, Project Based
approach
– ELP Extended Learning Projects
– Challenge Based Learning
• Develops Collaborative
Professional Learning Networks or
Communities among teachers

12. Challenges to Mobile Education
• Technical Challenges
– Flash (iPad platform and many Android Devices) may count out a lot of
rich content
• Access Challenges
– Mobile broadband access can be limited in Montana
– Digital divide is likely a larger issue in the mobile space as compared to
the desktop/laptop computer space
• Student Challenges
– Students need to be trained on the devices – especially in how to use
them as a learning device
• Local Site Challenges
– Restrictive Policies that prevent usage in some locations
– Little support for students facing technical issues on mobile devices

17. Mobile.DiscoveryEducation.com

19. Web Resources Currently Converting
to iOS Compatible

20. Resources We Use That Work
Except for Flash Video Clips
These resources work but may not play Flash Video segments at this time.

21. Resources In Doubt At This Time
To be replaced by a new resource.

22. Resources That Work With
Specific Apps

24. The Problem Is Using Flash on Mobile
Devices
• HTML5 and Flash
• Finally, I want to touch on some of my thoughts on Flash and HTML5.
• From its beginning, Flash’s primary role has been to enable things on the web that were not otherwise possible. Over its history, this has included
things such as animation, vector graphics, sound, video, webcam and microphone support, and more. Because of its ubiquity and fast rate of
adoption, it was uniquely suited to quickly introduce new features to the web.
• Overtime, many of these Flash features were added to the browser. Time and time again, as the browsers matured things which were once done
exclusively in Flash, were eventually done in the browser. The Flash Player would then add new features and the cycle would continue. This has
happened over the entire history of Flash, and I expect, will continue to happen. This was something that was good for users (who got richer content
earlier), Adobe (who got to sell tools and technologies), and browser vendors (who could focus their efforts on features which the Flash Player had
proven to be popular and viable).
• The key point is this. If a Flash feature is successful, it will eventually be integrated into the browser, and developers and users will access it more and
more via the browser and not Flash.
• With the renewed competition in the browser market and the subsequent acceleration of new HTML5 features being added to browsers, the
number of things possible in the browser has dramatically increased. This includes a lot of overlap with features that were once exclusive to the Flash
Player. While it will still be a while before HTML5 / CSS3 features have the same ubiquity as the Flash Player currently has, the trend is very clear. A
lot of the things that you have done via Flash in the past, will increasingly be done via HTML5 and CSS3 directly in the browser.
• I think that is important enough that I should repeat it.
• A lot of the things that you have done via Flash in the past, will increasingly be done via HTML5 and CSS3 directly in the browser.
• I know that this is a bit scary for a lot of people who have made their career working with Flash. I completely get that. However, I think it is a HUGE
opportunity for the Flash community. As browser support for richer content and motion graphics improves, so will demand for designers and
developers who have experience working with motion graphics on the web. The Flash community has been doing this type of work on the web for
over a decade and is uniquely qualified to fill demand for similar work in the browser. I don’t think it is a coincidence that some of the most cutting
edge motion graphics work being done in HTML5 today is being done by developers and agencies with extensive experience in Flash (such as Grant
Skinner, Branden Hall, Big Spaceship, etc…).
• I am not suggesting that all Flash content should or will be done in HTML5. You have to look at each project on a case by case basis and make a
decision based on development costs, target platforms and user experience. Regardless, your customers are going to ask about HTML5, and you
should put yourself in a position to best meet their needs, regardless of technology or platform.
• This has ended up much longer than I had expected, but I wanted to share a lot of stuff that has been going through my head over the past couple of
days. Again, I understand the frustration about how all of this was originally communicated, and I want to apologize for that. I think it is pretty clear
that we did not communicate the news and our views around Flash as clearly as we should have.
• Please post and questions / comments below. Please keep all comments constructive and on topic (or else they may be moderated).

25. • http://innovativescholar.com/2011/03/26/im
plementing-a-11-ipad-scheme/