1 / 1

Challenges in Developing JKO Mobile Content Randy Smith

Challenges in Developing JKO Mobile Content Randy Smith. DAU course mixed text, images, video, embedded PDFs, mandatory and optional paths, and an interactive test (Level 2). Videos converted from flash, mov , … to mp4 using Handbrake . Converted to HTML5 manually.

ina
Download Presentation

Challenges in Developing JKO Mobile Content Randy Smith

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Challenges in Developing JKO Mobile ContentRandy Smith • DAU course mixed text, images, video, embedded PDFs, mandatory and optional paths, and an interactive test (Level 2). Videos converted from flash, mov, … to mp4 using Handbrake. Converted to HTML5 manually. • TGPS PDF documents converted to HTML5 using Calibre and Sigil tools. Resulting HTML adjusted for mobile. • Some TGPS users inputs saved and emailed to user to print or share. • Do you publish PDF, convert to eBook, or convert to HTML5? • Best practice encourages breaking larger content into smaller parts for better mobile results. • Should errors in original content be corrected or noted back to owner for update of original? • SME or ISD participation helps balance mobile design best practice with source content and structure. • Tools only do very basic HTML conversion. Remaining conversion is manual and labor intensive. • Simple line breaks, bullets, and tables have to be re-done to fit mobile displays. • Header and footer styles and transitions are different than source documents. • All images have to be re-sized, re-done for mobile . Is the image needed for mobile? • For readability, text runs need to be shorter on mobile. • Do you embed, link, or convert PDF content? • Code tested on workstation using Firefox may not execute the same on mobile - case sensitivity on Apple, JKO Mobile API does not callback, code errors on mobile device provide little or no opportunity to debug. • Found different behavior across mobile platforms – links to external web sites, links to embedded PDF documents. • Some TGPS users inputs saved and emailed to user to print or share. SME needs to decide where this is needed.

More Related