The slides from the presentation I gave with Joe Ferrari on May 9, 2012 at nycoders.org.
We did a case study of an Adobe AIR app we built for iPad and discussed the troubles we encountered (many!) and our solutions.
10. The Research Phase
Presentation builder
Asset Repository
Asset types: PDF, video, HTML5
Tracking (Flurry analytics)
Email sharing of assets
AIR workflow
11. Misconception #1
Adobe makes AIR, Adobe owns PDF
standard PDF, certainly PDFs will be
super easy!
(I vaguely remember that Adobe AIR has native support for PDFs...)
Is StageWebView the answer?
14. Misconception #2
PDFs are hard, but videos will be easy!
Flash has always been good for video,
right?
15. Video playback on iOS
FLV playback
Using StageWebView with Video file
Using StageWebView with Video
embedded in HTML
Using StageVideo: why we didn’t use this
16. Video playback on iOS
You can have video auto play (SWV
video)
Or you can track video events (SWV
HTML w/video)
BUT YOU CAN’T HAVE BOTH!
17. Video playback on iOS
You can have video auto play (SWV
video)
Or you can track video events (SWV
HTML w/video)
BUT YOU CAN’T HAVE BOTH!
or can you? Stage Video is one option...
And what about Full screen?
19. Our super-duper full
screen workaround
Same trick, just with a delay
HTML-StageWebView Communications
Auto play AND video status and full
screen!
Show Code
26. Correct Conceptions
Simple and quick architecture (show)
Easy to build UI
Able to adapt to schedule change (oops,
only 5 weeks after all)
Project ready on time as promised
28. Summary
Qualified success
Video and PDFs much harder than
expected
Full screen scaling/pinching vector art
problematic
Worth considering, especially with
cross-platform