Presentation about standards and requirements for mobile development and mobile portals for higher educational institutes

1. Study Case American University in Cairo By Student Service Online Mobile Technologies in Higher Education

2. Stakeholders (Students, Admins, faculty … etc) Mobile Design Layers & Standards Existing Services & Products Technologies & Infrastructure Service Oriented Architecture Agenda

3. Students Calendar, Class Schedule, Bus Schedules, Announcements… Faculty E-Learning, Student2Faculty Communication … Administrators Remote Administration, Security … Stakeholders

4. Understanding users Fits in your pocket More personal than the PC Consistency across modes Localization is intensified Integrated devices, modes, products Mobile Six Layers Design & StandardsAccording to Google …

5. "Repetitive now“ User is someone checking for the same piece of information over and over again, like checking the same stock quotes or weather. [Using RSS Feed] "Bored now“ Users who have time on their hands. People on trains or waiting in airports or sitting in cafes. For Entertaining and Surfing "Urgent now” Users who needs to find something specific fast 1 or 2 clicks tops, like the location of a Class or directions to the certain building. [ Location-Aware ] [prospective students] Mobile User Types

6. Fit on a small screen and no complicated text input. Layout has to be clean, simple, but maintain the basic usability of the parent desktop application. The "density of information" changes on a mobile phone, requiring designers to identify only the most essential parts of any given application. Fits in your pocket

7. Different functionalities, Different layouts and needs If mobile applications are to be universal, it have to maintain patterns and designs across all screens. Consistency

8. The need to optimize for different devices, browsers, languages, countries and cultures. Localization is intensified

9. Few links and Less choice, more structure, but drill down further. OR As many links as possible but be shallower so users get to their destination faster? Finding that right balance sometimes means dropping as much functionality as possible. Once you have identified who will be using your site Depth vs Breadth

10. NCSU Libraries Mobile http://www.lib.ncsu.edu/m/about.html http://m.ncsu.edu/ UoMobile: University of Ottawa http://m.uottawa.ca http://www.fairchoicesystems.com/uomobile.php Existing Services & Products

11. Helping Booth or a Kiosk for information provding Student2Faculty Virtual Office hours ( virtual meeting ) Mobile Health Care Services, keeping track of students and faculty health and dietary. A lot More  Other Services

12. Java, JSP, .NET Languages SharePoint Should Provide MobileView ( not good Idea though) UoMobile, 3rd Party Services and Softwares No Significant changes to infrastructure, Good Architecture and bunch of hardware. Technologies & InfraStructure

13. But All this is not feasible with out a solid and reliable Architecture. Service Oriented Architecture

14. Students & Faculty can contribute to the digital campus. Forget Ordinary Database Applications. Think Intelligent, Decision Making & Multi-Agent Systems and Applications. All we need is layout the platform (SandBox ) and let people play This … What I Came to See Made By AUC ... For AUC

15. http://www.informationweek.com/blog/main/archives/2007/04/google_lays_out.html;jsessionid=NFBUVPZOERHX1QE1GHPSKHWATMY32JVN References