Title: 2 ND Open uMobile call
Date: Thursday 7 November, 2013 at 11 am EST
Agenda Summary:
1.
Improvements needed for uMobile:
This seemed like a very open ended question and did not get any response from the attendees. It was decided to move to the next agenda item
2.
Consideration of PhoneGap as a native client:
Dave @ Oakland University: Developing on PhoneGap uMobile version. They have open sourced that and has logou button, list view v/s grid view. Oakland has added modules that are not part of
Portal. One issue they have found is that scrolling is slower compared to their native android app.
They are planning iOs7 release by end of November or latest by end of year. They have found a couple of bugs related to the following: i.
CAS authentication ii.
Freezing
Q1) Are we saying that as a community we would like to adapt PhoneGap as the native client?
Code for PhoneGap is out and includes documentation. This code works for both iOs and Andriod. For more details, please refer to PhoneGap documentation
Q2) Why did some universities select PhoneGap?
Don’t like to do all things only for iOS clients. Don’t have people that know objective C
Resource constraints
Q3) Did you find any features that were in Titanium version to be missing in PhoneGap version?
No major issues so far on PhoneGAp
Before moving to another employer, Jen at Unicon converted the titanium cdoe to PhoneGap. Other were tasked to look at the code and fleshing out all details before the 2013 Apereo conference.
Anything that was used in Titanium is now available in Phone Gap
One difference is Titanium made the code look like Native code whereas PhoneGAp makes it look like
HTML
Oakland has same functionality with their PhoneGap as was their Titanium version
3.
Client as a web service
KiThai – need more information on this?
General consensus was:
If you are trying to create a modern interface for some service on campus based on restful web service where does the logic and the code to display it reside?

The answer is neither in uPortal code nor in PhoneGap but to develop a portlet to do that and deploy it to your uPortal
4.
Responsive design
Unicon is working on the Respondr theme. They are focusing on the twitter bootstrap that ties with various devices. This is not yet wrapped with uMobile.
This is open for business and working on uPortal 4.1 release to include this.
Majority of things currently work and are short a few features.
Discussed about responsive design and native client:
Native client would still serve a very valuable purpose – especially for those features that require native apps to tap in the features of the device. Examples are launching turn by turn direction
Some schools have a mandate to have visibility in the app store
It was discussed that students do not like mobile browsers and prefer mobile app instead.
Q) Should responsive design be considered a part of uMobile?
Some Universities see value in the uPortal code to be responsive to fit their Portal deployment that may not be easy to integrate in the Mobile App
Action Items:
# Who
1. Dave @ Oakland
University
2. Oakland
Due Date What
Send Oakland’s PhoneGap documentation to wiki
Demo of their PhoneGap deployment on iOS and
Android?
Decisions:
# What
1. Titanium version has been deprecated in favor of PhoneGap client (date?)
2
Parking Lot